Closed mrtnkhl closed 5 years ago
Open Z-Wave config for this device can be found here: https://github.com/OpenZWave/open-zwave/blob/master/config/ge/26933-motion-dimmer.xml
Issue still exists in 0.86.3.
I'm seeing this in 0.86.4 and have been seeing it since I added these switches. I think this is also causing my issues with my burglar always saying at value 254 (sleep) and them not updating properly as there are multiple entities.
Issue still exists in 0.87.0
I just wanted to +1 this...I have had this issue with GE Z-Wave motion switches and dimmers since the beginning (1.5 years ago or so). This happened on my previous install that included MQTT, and on a new install that does not have MQTT.
+1 Just commenting to say that I am experiencing this issue as well. Would be great if there was a workaround for duplicate switches.
+1 I have the same issue. I would love to have a solution for the duplicate switches/sensors as well as the lack of updates on the switch status. When you use the buttons to turn on/off in HA, the light will turn off but the switches stay on usually at a partial dim setting.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
So.....this was closed, and I assume nobody ever figured anything out? I am also having issues with these devices showing up as multiples of the same node in HA. Would really love to resolve the issue.
still happens in 0.97.2
If I recall correctly, this was expected behavior. The second instance of the switch represents z-wave switch changes, and the primary instance is any changes. You can use this to determine if a change to the switch state was initiated by a person or by an automation. I have not investigated if this works properly.
On Mon, Aug 26, 2019 at 11:17 PM Andrew Lambeth notifications@github.com wrote:
still happens in 0.97.2
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/20495?email_source=notifications&email_token=ABELXA6YQ5CM5IXMNKJLOBTQGSTDXA5CNFSM4GSSCNBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5GNPZI#issuecomment-525129701, or mute the thread https://github.com/notifications/unsubscribe-auth/ABELXAZFL6MKBX2PLEXQ2X3QGSTDXANCNFSM4GSSCNBA .
That seems...unlikely? I mean....I've got a whole lot of zwave switches, and these are the only ones that do that. All of them are able to tell if they were controlled locally or via RF....why would these particular switches require an entirely different entity for that?
I don't know GE/JASCO's motivations. I have about 15 of these, and about an equal number of Leviton switches. I agree these work differently than Leviton switches. Looking at the history for several of these duplicate switch instances, I can 100% confirm that the histories are NOT identical between the two instances of the same switch (meaning these are not just a shadow of some kind). Beyond that, I can confirm that value_instance 2 appears to correlate with automations, and value_instance 1 appears to correlate with the actual relay state. If there is another explanation of the purpose or meaning of these that correlates with observed data, I would definitely be interested.
On Wed, Aug 28, 2019 at 12:53 PM Rocketman69 notifications@github.com wrote:
That seems...unlikely? I mean....I've got a whole lot of zwave switches, and these are the only ones that do that. All of them are able to tell if they were controlled locally or via RF....why would these particular switches require an entirely different entity for that?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/20495?email_source=notifications&email_token=ABELXA3UXJ36WFWZCCMQAJLQG23TLA5CNFSM4GSSCNBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5L6DRI#issuecomment-525853125, or mute the thread https://github.com/notifications/unsubscribe-auth/ABELXAZGEUVI6DRYF6LQ5CLQG23TLANCNFSM4GSSCNBA .
This is still an issue with HA 106
I'm even seeing issues where the zwave entity is created but no child entities for GE switches :. I'm unable to remove or repair them either.
Still a issue for me 4/27
This is not an issue. This is what is reported from the device.
Check this: https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/740
So what happened is when OpenZWave sees endpoint 0, it creates SWITCH_MULTILEVEL instance 1 and NOTIFICATION instance 1. When it sees endpoint 1, it creates SWITCH_MULTILEVEL instance 2 and when it sees endpoint 2, it creates NOTIFICATION instance 2. That's where the duplicates are from.
Now, they should behave the same as the document says. However by openzwave default, only instance 1 is in the association group 1 (Members ["1.0"], if your controller node id is 1). So that's why you only see updates from the first instance but not the second. (If, by any chance, your instance 2 is in the association group 1 ("1.1"), you see the opposite). (Here I'm also not very clear why 1.1 is instance 2 but not endpoint 1 or 2, but that's the basic idea). If you want them both updated, just add "1.0" and "1.1" both to the association group.
So, for me, my solution for the duplication is to simply disable the entities from the second instance (and make sure only "1.0" is in the association group 1)
Home Assistant release with the issue:
0.85.0
Last working Home Assistant release (if known): unknown
Operating environment (Hass.io/Docker/Windows/etc.):
Docker on Ubuntu 18.04 LTS with Aeotec Z-Stick Gen5, fresh install a week ago
Component/platform:
https://www.home-assistant.io/docs/z-wave/
Description of problem: https://community.home-assistant.io/t/ge-jasco-26933-issues/22738 When adding a GE / Jasco 26933 Motion Dimmer device via Z-Wave "Add Node", the Z-Wave component adds one (1) new NodeID for the device but Home Assistant creates multiple duplicates:
On the Home Assistant side, the light component of the device, as well as the motion and other sensor components, appear 2-3 times as duplicates. This makes the devices practically unusable, as it is unclear which light of the two to switch or which sensor to query or respond to. The duplicate lights also appear to not share the same state.
This seems to be a known issue since 2017, that some people in the forum attribute to the different operating modes of the motion dimmer (Occupancy, Vacancy, and Manual mode). No real workaround has been found for this attractive and useful device.
The folks around SmartThings seem to have found a solution to this problem in the form of a custom DTH: http://thingsthataresmart.wiki/index.php?title=GE_Z-Wave_Motion_Sensor_Dimmer_Switch Their code can be found here: https://raw.githubusercontent.com/MichaelStruck/SmartThingsPublic/master/devicetypes/michaelstruck/ge-motion-dimmer-switch-26933.src/ge-motion-dimmer-switch-26933.groovy
Ideally, HA would only create one entry for the light and sensor components.
Problem-relevant
zwavecfg.xml
entries:Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: All components are new, Z-Wave stick and dimmer switches bought in January 2019, sourced both from Amazon and Lowe's.