Can any Homeseer users post their log of turning on / off / on their LZW31-SN dimmer? Can you also post how you named the parent and child devices created when including the dimmer. I’m sure there is a problem with creation of child devices for this dimmer and not the LZW30-SN switch.
I included it using the Z-Tool+ app on my iphone.
So, however that does its thing is how it got added.
If there is a way for me to tell and you can give me some hints on where to look, I will do so and report back.
I think it is quite weird that I’m getting watts info from the device but not the status of the light.
And, I can talk to the switch from my hub without any problems so I know it is connected and communicating on the Z-wave network.
I think z-tool plus by default attempts to do a secure install. I usually manually select unsecure add when using it, especially for battery operated devices because I think they use less energy in unsecure mode.
Unfortunately I don’t know what is wrong with the dimmers and homeseer. I know the wrong device is being updated. Any events that trigger from status of the switch are broken since the multilevel child device is basically not used for status updates. I think I’ll be going back to homeseer dimmers until this gets resolved, which hopefully is soon.
Thanks for the feedback @devanb. I do have a ticket open with Homeseer, and I have been poking them every few days. The response I have gotten is that they are busy working on the HS4 release and will provide some assistance after that is finished. Unfortunately I’m kind of stuck until they look into it.
As you have noticed the switch is sending a report to the Homeseer hub, but Homeseer isn’t applying it to the correct device. I’ll keep you posted when I find out more.
I’ve seen incorrect status reports in Home Assistant too.
I initially included my LZW31-SN switches with “add node secure”. It was awful. The status reported by HA was almost always different from the real status of the switch. Looking at the ZWave logs, I saw that Open ZWave was rejecting clear text messages sent by the switch. That’s a rule in Open ZWave: if a node was included securely then Open ZWave reject any clear text message from that node.
I excluded the switch and used “add node”. It seems to me I did still get a few incorrect reports afterwards but as we speak I’ve not seen an incorrect report in a very long time. The ZWave network has been restarted in the meantime so it is possible that the initialization process performed when the ZWave network starts has put the switch into the state where the reports are accurate.
They have added my issue with a previous ticket (probably yours).
Since this is happening on homeseer and Home assistant (maybe), why not smartthings?
I came from Vera to Homeseer and never heard of device handlers. I’m not sure what they are and why smartthings needs them. If home assistant and homeseer use a z wave system that does not rely on device handlers or drivers, where is the issue? To be annoying, the inovelli switch works perfectly, not the current dimmer. In fact, my old inovelli dimmer works as well.
Had the same problem and found this thread. Not sure if it’s going to be helpful to anybody, but figured I’d still provide a workaround (or a solution, whatever). The dimmers seem to have 4 association groups:
Group index=“1” label=“Lifeline”
Group index=“2” label=“Basic_Set”
Group index=“3” label=“Switch_MultiLevel_Set”
Group index=“4” label=“Switch_MultiLevel_Start/Stop”
Homeseer only associates itself with the Lifeline group by default. With that group being set homeseer indeed doesn’t report on/off events (when you click the on or off button once), it does however report dim events (when you hold the on or off button), which is weird.
I tried adding homeseer to the other groups and the group 3 seemed to be the one making difference for the on/off events. It now reports all the events immediately and reliably:
Groups 2 and 4 don’t seem to make any difference. Perhaps, someone from Inovelli could explain why it’s happening and whether the other two groups should be associated with the controller as well.
@achurak
Nice work!
Adding Group 3 appears to fix the problem for me.
(FWIW, I didn’t need to associate Group 1.)
Once I added Group 3, turning on/off the light at the switch is quickly and accurately reflected in HomeSeer for the light switch element.
