Lights do not change name in deconz

[w.vuyk]

Wim,

Perhaps this error is in deCONZ itself. I have now seen that a new update has been released for deCONZ (2.13.2-beta) and one of the changes is:

• Fix naming of smart plugs in deCONZ GUI #5380

I'm not going to test it because I'm going to stick with the stable 2.12.6 version for now

Nuno,

I agree you not going to this beta yet. I am in the middle of this beta and have quite a lot of issues going with this beta. Needing all sanity checks to find where the issue comes from. I have been waiting for this new beta and will test it here. For one I hope this will resolve the double IKEA motion sensors on the same device I am having now. And hope my alarm system will work again

I will keep you posted here ok?

Wim

[nunoary]

Ok. Thanks Wim.

[legato]

Hi Wim,

The combination of JowiHue 4.0.5.6 and deCONZ 2.13.2-beta works fine now for the renaming of Zigbee devices, but still a manual rename had to be done after adding a new on/off plug. (which is by design, as indicated in one of the earlier posts in this thread)

Tonight I added a new Blitzwolf SHP-15 plug by using the 'Scan for devices' in de Bridge Maintenance part of the JowiHue plugin.

The device was correctly found as Light device On/Off plug-in unit 14, an On/Off feature for plug-in unit 14 was found and two unknown sensors were found.
I restarted the JowiHue plug-in in HomeSeer, and then the HomeSeer log showed: Adding feature For Power 26 (ZHAPower), Adding feature For Consumption 25 (ZHAConsumption), Power feature Volt for Power 26 created, Power feature current for Power 26 created

The name in deCONZ was automatically changed to Consumption 25, but the name in the JowiHue Bridge Maintenance, Settings -> Light Info was still On/Off plug-in unit 14.
Also in Phoscon the name was still On/Off plug-in unit 14 and the HomeSeer device was also still On/Off plug-in unit 14.

I changed the devicename in HomeSeer, which automatically changed the name in deCONZ. The name in the JowiHue Bridge Maintenance, Settings -> Light Info and the name in Phoscon was still On/Off plug-in unit 14.
Then I changed the name in Phoscon, which automatically changed the name in the JowiHue Bridge Maintenance, Settings -> Light Info.
The feature name On/Off plug-in unit 14 (312) had to be renamed manually within HomeSeer.

Everything is working fine now, with the correct names, all the power features and no errors in the HomeSeer logging.
It took me a while to reproduce the above procedure, but it seems to do the trick.

Soon I will unpack another new Blitzwolf SHP-15 plug, and check if the procedure as written above, can be done again to be absolutely sure the procedure is correct.

[w.vuyk]

As a workaround this can be a good procedure. I will still try to get it right while using only the plugin I am sure it will happen! But the largest part of the pain is when a device has multiple plug devices. I need to get this part correct.

[legato]

Wim,

After restarting deCONZ, one of the renamed devices suddenly changed its name back in deCONZ.
It seems that deCONZ itself still has some renaming issues.

My workaround was to correct the names directly in the zll.db database file with the tool DB Browser for SQLite.
After that everything was as it should, without having to remove devices and without having to rescan for new devices.

It looks like the deCONZ naming issue still hasn't been completely solved in deCONZ 2.13.2-beta; See issue #4255

[w.vuyk]

The current beta version of deCONZ is having a lot of serious issues and I really do not advise anyone to use this version as it is just not stable, Here I have to change my HS events witrh every start of deCONZ because of double devices on motion sensors. So sorry, I cannot support this beta version at this point. Also, editing the database is very much at your own risk

Wim

[legato]

Hi Wim,

For now it's working and my HomeSeer system works as expected.
Indeed I'm going to wait for a new stable deCONZ, before changing anything else.
The JowiHue plugin works fine and I understand that changes in the deCONZ database are completely at own risk.
I'm not very fond of this either, and rather have it done the nice way, when deCONZ works correct again. (but still it was nice to do some research how deCONZ works with the zll.db database)

[w.vuyk]

I think (hope) the next update of the plugin wil solve it. I am testing it, and there seems to be one hurdle to solve it. It does not take away the current beta confusion of deCONZ, bt it shod be a ot n=more clear how renaming works once all is stable again.