switch_set_on_time not working as expected #1816
Closed
BigProgrammer2000
started this conversation in
Ideas
Replies: 1 comment 11 replies
-
This has never been an assumption |
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The problem
I have noticed that the homematicip_local.switch_set_on_time action/service call does not work as in a program in the CCU.
In the CCU, the ON_TIME parameter can be overwritten after a switch has been switched on. Unfortunately, this does not work with homematicip_local.switch_set_on_time. A reset with the value 0 according to the documentation is also not possible.
Example:
Call homematicip_local.switch_set_on_time with 10s
Call switch.turn_on
wait 5s
Call homematicip_local.switch_set_on_time with 100s
Call switch.turn_on
Result: The switch only stays on for 10s.
Expected result: The switch should stay on for 100s.
Same behavior when using homematicip_local.set_device_value.
Overwriting ON_TIME works when using homematicip_local.put_paramset. However, it is necessary to send “STATE: true” so that the overwriting works.
I also found out the following when testing homematicip_local.put_paramset:
Suggestion:
A checkbox could be added to send STATE: true in the service call. In addition, a distinction must then be made between checkbox active (homematicip_local.put_paramset) and not active (homematicip_local.set_device_value)
Attention:
I could not check if the same applies to homematicip_local.light_set_on_time.
It would be nice if homematicip_local.switch_set_on_time could be adapted so that overwriting ON_TIME really works.
Beta Was this translation helpful? Give feedback.
All reactions