Replies: 7 comments
-
I don't think I can implement |
Beta Was this translation helpful? Give feedback.
-
Not timer entities, per se, but calendar/date/time/datetime ones. Inching, for example, would be a time or number entity, similar to the existing countdown timers. Schedules would be input as time/datetime entities, and perhaps exposed as calendar entities |
Beta Was this translation helpful? Give feedback.
-
You mean replacing the existed timer number entities with time or datetime entities platforms? or set 2 entities number / time. |
Beta Was this translation helpful? Give feedback.
-
For reference, here's a reference for a smart socket similar to one I have. The countdown timer (DPID 9) is implemented with a number entity, but the more complex cycle/random timers (DPID 41/42) are unimplemented. How they're implemented would be up to you :D just suggesting that time/calendar entities would be a decent way to do so :D I can also contribute code and testing, if I get time and guidance. |
Beta Was this translation helpful? Give feedback.
-
cycle/random aren't existed in every device, these two DPID reports an encrypted string e.g. |
Beta Was this translation helpful? Give feedback.
-
I'd imagine that string could be parsed with the definition provided in the reference, which was my original hope for implementation of those DPIDs. I understand though if it's not really worth it :D However, having countdowns be |
Beta Was this translation helpful? Give feedback.
-
Making other entities to have any control of other entities isn't really ideal, well the best way I would is by changing the countdown platforms from number to more suitable entity which "timer" is perfect for that but since this can't be done I may give time entity a shot if it didn't works then there is nothing I can do ^^ |
Beta Was this translation helpful? Give feedback.
-
Currently, timers such as schedules, inching, etc are not supported, and there's no option to configure a calendar/text/time/etc entity to match (understandable, as those fields are binary data).
While these functions can be emulated in HA through automations, it would still be cool to have the built-in timers supported, to allow easier integration for users with existing timers in Smart Life
Beta Was this translation helpful? Give feedback.
All reactions