I added it to my zwave network after switching to manual so maybe that has an effect? What does ozwcp say? I did notice that on first load in HA it always maxes at 254 until I move in front of it.
@blerg I see the same thing. I haven’t been able to get the burglar sensors to show anything but 254
Just tried removing and re-adding the switch, making sure it was set to manual mode first. No luck.
Are you using polling or were you also able to get instant status to work with this switch? I can control the switch from within HA but the status doesn’t seem to update reliably.
Again the same thing as @blerg: status updates are unreliable. Often one of the two light level values that show up will show on even after the switch has been turned off
What hub are you relying on? My Wink v1 had issues so I got a Aeon stick for my pi. According to the smartthings forums it looks like a Samsung hub works too.
I’m also using a z-wave stick (Linear/Nortek HUSBZB-1).
Poking through some of the HomeAssistant/Vera threads, it seems a lot of people resolved issues by changing the association mappings or endpoints in, for example, HomeSeer. I’m new to z-wave, but is there a similar kind of thing we can do in HA (hassio specifically)?
Any update on this? I’m hitting it on the latest version of HA with a bunch of 26933’s that I bought recently.
I just ran into this myself. I am gradually switching over from Smartthings and moved two 26933’s over to HA that worked perfectly. The third one was not updating any status or motion, when it had done so in Smartthings previously. What worked for me (I am running hassio) was to remove and re-add the controller node under the lifeline association group. I did this by going to Z-Wave Configuration, and then under Z-Wave Node Management select the problem node. Go to Node group associations, under group select “Lifeline”. Your controller will probably be listed under “Other Nodes in this group:”. Then under Node to Control, select your controller Node. Then select remove from group. I then backed out of the Z-Wave configuration, refreshed and went back in to the Node Group associations for the problem node, selected lifeline again, and made sure that “Other Nodes in this group” was “None”. Then under Node to Control, select your controller Node again. This time, select add to group, and it should show under “Other Nodes in this group”. I don’t know if I got lucky but this worked for me.
2 Likes
I just purchased and installed a GE 26933 Smart Motion Dimmer. It does what I want, but I hate how it reports in Home Assistant! Everything is duplicated. There are 8 new sensors in Home Assistant (2 each of “Alarm Level”, “Alarm Type”, “Burglar”, “SourceNodeId”. One of the two “Burglar” sensors does report motion properly I think (a value of 8 is motion).
The worst aspect is that there are two new “light” entities. One seems a bit more accurate than the other, but it’s basically impossible to understand the status/history of the lights, as it looks like the on/off status shows up on a random light.
I really like the functionality of this product, but I don’t think I’ll install any more due to the difficult reporting situation. 
I recently installed a GE Z-Wave Motion switch and noticed it does expose two of each item to Home Assistant. I’m still trying to figure out why, but I think it’s because it has different modes (manual, occupancy and vacation). I run mine on occupancy mode since it’s installed in the garage so the light automatically turns on when it detects motion and turns off after 5 minutes of no motion. For me, light switch #2 is the one that seems to accurately reflect when the light is turned on and off, and allows me to turn the switch on manually and it will automatically turn off after 5 minutes of no motion. I hid all of the other sensors and light switch #1 since I don’t need them. It’s been working fine in this setup for a couple weeks.
Ran into the same issue here. Only one Z-Wave Node ID per device, but duplicate entries at least 2x for each. Has anybody filed a bug for this? Looks like an HA issue and not a Z-Wave stack issue.
For reference, this is how SmartThings handles the device:
https://raw.githubusercontent.com/MichaelStruck/SmartThingsPublic/master/devicetypes/michaelstruck/ge-motion-dimmer-switch-26933.src/ge-motion-dimmer-switch-26933.groovy
http://thingsthataresmart.wiki/index.php?title=GE_Z-Wave_Motion_Sensor_Dimmer_Switch
Thanks for foiling that. Did anyone else resolve the issue where the burglar always returns 254? It seems so random.
1 Like
This worked for me! Thanks for posting this!
I only saw 254 after a restart of HASS. I just installed my yesterday though., So far, super happy. Set the dimmer to manual, and created a template sensor for the motion sensor and Turn the light off/on using HA. For me I just wanted a powered motion sensor and integrating into a light switch, seemed to be the best way to get both.
You need to follow the instructions above for Node Group associations to resolve the 254 issue. I did the same with a binary sensor template (and setting the device class) checking for the value of 8 
Just for a data point, my burglar sensor works fine, I did not have to do anything with group associations, but I will say that I had set to manual mode before adding to zwave.
Long time user first time poster…
I am surprised these switch/dimmer/motion switches are not more popular. I am having the same problem as everyone else here. Multiple/duplicate instances of switches and sensors show up, they don’t always update especially when turning off they continue to appear on in HA. The burglar sensor does work consistently but I would like to use more of these for automations.
I gotta say, I have two of these now (one dimmer model and one switch model), both added just fine and have worked flawlessly for me. I don’t really care about the multiple entires for the switch/light/motion, etc. I can just ignore them.
Now I will say my setup may not be the same as everyone elses. I wanted these because I wanted a powered motion sensor. I replaced an older zwave switch and dimmer with these and put the old switches somewhere else.
here is my process.
Connect new switch
Configure for manual. (the motion sensor does not turn the light on/off)
After verifying manual is working correctly, add zwave device to HA
Once it’s added, find the device.
Figure out which motion sensor shows 8 when motion is detected. Verify this a few times just to make sure (for me the other motion sensor reports 254 all the time)
Turn the light on and of manually, see which swich reports on/off
switch the light on/off with HA, verify it turns off/on, etc.
Make a binary sensor for the correct motion sensor
- platform: template
sensors:
motion_sensor_front_door_motion:
value_template: "{{ is_state('sensor.motion_sensor_front_door_motion', '8') }}"
friendly_name: "Motion Sensor (Front Door)"
device_class: motion
entity_id: sensor.motion_sensor_front_door_motion
Add the switch/light to whichever lovelace view I want to use.
Create any automations/scripts, etc to turn the light on/off how I want.
For me the motion sensor has worked 100%, and the light turns on/off when I expect it to and reports correctly. I dont know if the duplicate switches/motion are turning on/off because I dont look at them.
Edit: Just wanted to add that I’ve liked these so much , I now have my 3rd (probably last). I have had no issues at all other than the reported extra devices which I just ignore. Everything works perfect as in I’ve never had a single issue with lights or motion.
4 Likes
Don’t think it’s a bug the second light switch tells if it was done physically.