Wrong Z-Wave entity shown in the overview "bubble" from devices with instanceid > 1

[nodomain]

Home Assistant release (hass --version): 0.51.2

Python release (python3 --version): 3.5.3

Component/platform: zwave

Description of problem: According to my thread at https://community.home-assistant.io/t/z-wave-value-instance/25006/5?u=nodomain there seems to be a little UI bug that prints the wrong entity ID if the device has a instance ID >1. This led to some confusion with me trying to hide/regroup the device using customization. In the "developer" view with all entities the device shows up correctly.

I assume something has been mixed up when changing the entity IDs some releases ago.

Expected: Show the correct instance ID, e.g. sensor.dimmer_livingroom_energy_2 instead of sensor.dimmer_livingroom_energy

Problem-relevant configuration.yaml entries and steps to reproduce: n/a

Traceback (if applicable): n/a

Additional info:

[andrey-git]

Could you post an image of both the developer section where the device is showing correctly and the more-info where it shows incorrectly?

[balloobbot]

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 :+1:

[srcLurker]

I am also seeing this issue:

Home assistant 0.60.1 Python 3.5.2

On the stats page (see below), notice the left column has the _2 and _3, but the new_entity_id doesn't. For the pop-up window (also below), notice the value instance, the old_entity_id and the new_entity_id.

Stats page:

Entity	States	Attributes
switch.zooz_unknown_type6100_id6100_switch	off	friendly_name: Zooz Unknown: type=6100, id=6100 Switch new_entity_id: switch.zooz_unknown_type6100_id6100_switch old_entity_id: switch.zooz_unknown_type6100_id6100_switch_30_0 value_instance: 1 value_id: 72057594546044928 value_index: 0 node_id: 30
switch.zooz_unknown_type6100_id6100_switch_2	off	friendly_name: Zooz Unknown: type=6100, id=6100 Switch new_entity_id: switch.zooz_unknown_type6100_id6100_switch old_entity_id: switch.zooz_unknown_type6100_id6100_switch_30_0_2 value_instance: 2 value_id: 144115188583972864 value_index: 0 node_id: 30
switch.zooz_unknown_type6100_id6100_switch_3	off	friendly_name: Zooz Unknown: type=6100, id=6100 Switch new_entity_id: switch.zooz_unknown_type6100_id6100_switch old_entity_id: switch.zooz_unknown_type6100_id6100_switch_30_0_3 value_instance: 3 value_id: 216172782621900800 value_index: 0 node_id: 30

Popup:

Name	Value
new entity id	switch.zooz_unknown_type6100_id6100_switch
old entity id	switch.zooz_unknown_type6100_id6100_switch_30_0_2
value instance	2
value id	144115188583972864
value index	0
node id	30

[csantoni]

I'm having a similar problem with the Inovelli 2-channel switch. Sometimes I get one channel, sometimes the other, but since 0.60.1 I can't get all my switches all the time.

[brillb]

I have the same problem with the Inovelli 2-channel switch as well. Sometimes it shows all the switches, sometimes it just shows one, and it shouldn't be overwriting "old" with "new" that is missing the sub-IDs

friendly_name: Dual Outlets Switch new_entity_id: switch.dual_outlets_switch node_id: 5 old_entity_id: switch.dual_outlets_switch_5_0_6 value_id: 432345564316354208 value_index: 0 value_instance: 6

[halfbaked]

Have the same problem with a fibaro double switch. While the old ids for the 2 switches will be different, the new entity ids are the same. I renamed the zwave node bed3_double_switch and get duplicate: switch.bed3_double_switch_switch

[balloobbot]

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 :+1:

[balloobbot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍