ZWave Dimmer Control #38
Labels
No Label
architecture
bug
ci/cd
cleanup
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
new feature
packaging
question
ui
waiting user input
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: platypush/platypush#38
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've been trying to get a ZWave dimmer switch to work, but need to follow a strange sequence of operations.
zwave.set_value { id_on_network = fc61d6d1.15.26.1.0, data = 130 }
. Reported as 0 in JSON and lamp is OFF.zwave.set_value { id_on_network = fc61d6d1.15.26.1.0, data = 255 }
. Lamp is now ON at 130 (not max brightness) but JSON reports 0.zwave.set_value { id_on_network = fc61d6d1.15.26.1.0, data = 0 }
. Lamp is OFF, but JSON reports level of 76!Looking around in OWZ and python-OZW forums, it looks as though OZW changed how it handled dimmer transitions, and as python-OZW is pretty much unmaintained now, I guess that these changes may not be fully supported in python-OZW??
I then tried running Zwavejs2Mqtt which worked well and seems to be more actively maintained than python-OZW.
What are your thoughts on PP support for zwavejs2mqtt? If you thought this could work in a similar manner to zigbee2mqtt, then I'd be happy to take a look when I had a bit of time.
Thanks,
Chris