Just wanted to add that the GE26933 motion dimmer Does not seem to report correctly even after adding the command class
I went back and deleted the ozw cache and rebuillt it and it still made no difference.
This is a known bug in OZW, was fixed in 0.6 but that version had other issues and was pulled back a while ago. Probably with the next update it`s fixed again.
Just wanted to note that this works for me also. Thanks!
Did you ever find a resolution to this? Just upgraded to OZW 1.6 and I’m having the same issue with the GE 26933.
I did get it to work, but honestly not sure if the fix is now part of OZW or not. Basically I made some changes to the xml for th GE dimmer motion control. I cannot remember exactly what changes I made, but I just checked and it looks like there have been updates. The file I think I updated was
26933-motion-dimmer.xml in the ozw under ge.
Just got it to work. I added the VerifyChanged flag to the xml file as suggested above. Didn’t work at first, but after I power cycled the switch it started behaving as expected.
1 Like
What would be the fix for us using the new Z-Wave JS?
You don’t need to do anything in zwavejs, they just work. If you have the old versions of the dimmers, you need to poll them. You can enable polling if you’re using zwavejs2mqtt
I just moved everything from Smartthings over, they are older dimmers, a couple of examples are:
ZW3003 by GE/Jasco
WD500Z-1 by Control
So you’re saying, there is not a way to get the incorporated HA suggested zwaveJS to do polling and that I need to install zwavejs2mqtt, correct?
I don’t want to convolute my z-wave integration (not sure how the 2 play with each other).
What is the best method of installing ZwaveJS-2-mqtt and making the changes that need to be done? Can I or should I uninstall ZwaveJS-2-mqtt when done?
Thanks again!
Nathan
I have 2 qubino mini dimmers ZMNHHD . One on firmware 20 and the other on 20.2. Linked via zwavejs2mqtt. The old one works fine. The new one does not update it’s entity status when enabled via the button in the room.
Why would this be?
How does one make those modifications on the newer homeassistant running the rebuilt zwave config?
I have about 12 of those type zwave dimmers. I paired one fan controller and one switch to test and right away saw that it always reported on after being turned off.
WIth the new zwave build I don’t seem to have a yaml to edit and if I create it no good.
Thanks
Ping the device with an automation. That’s what has replaced the polling setting in yaml. You can use a time_pattern to ping the devices every x minutes/seconds, whatever your heart desires.
Thanks for the quick reply though this seems like a short term answer, the ping says:
NOTE: This service has been deprecated and replaced with a new button entity.
I’m very very new to homeassistant despite having over 100 zwave/zigbee devices and lots of experience with smart devices.
Just trying to get caught up here.
I should add I also am not entirely sure where to put those lines of code
Ah yes, you want to use the button.press service and provide it the button.ping entity that is created in the device.
You make an automation. You can do it through the UI. Choose call a service and select button.press and find the ping entity for the node in question.
Let me hunt for all that. I got this stood up over a month ago, even signed up for a year of Nabu casa so I can move from smartthings.
I saw this somewhere back then but moved on to a huge 3D print project (yes got octoprint integrated here). I remember best when I find things on my own so I will hunt it down.
Sorry I’m at work and about to leave so I gave this a little more thought.
What is the trigger for the automation I am to make? I assume it needs one to activate the “button press” event to then force the ping?
Thanks
Here’s where petro stated what to use 
Ok so I have this so far, the task runs on a 30 second schedule (for now) to test. Its triggering. The pic is what I have set up but no change to on/off status. … So what am I doing wrong? TIA
A ping doesn’t refresh the on/off status, it makes sure the node’s alive, you’ll need to issue a zwave refresh_value to update the status.
