Losing deCONZ connection

[Platopus]

I have been using Jowihue with deCONZ for the past few weeks to control hue lights and different aqara sensors and was very pleased with the performance and stability. For the past two days I have been testing Donmor's plugin to connect lutron Caseta dimmers and when I start creating rules to control Hue lights via the pico remote I lose connection between JowiHue and deCONZ. I can still control all my zigbee devices via Phoscon. The only way I found to make JowiHue work again is to remove and add the bridge. I checked the log and I see this error that coincides with the lost connection for both time I tried it.



Anybody had a similar issue or ideas how to resolve it?

[w.vuyk]

By the looks of the image, you are using HS3 right? Do you know which lights you are trying to control here? Con you try to stop the plugin and remove the device that is throwing the error and then restart the plugin again - do not remove the bridge. I think the light you are trying to control here is damaged in HS3 somehow and a rebuild of the dievce might help you recover it. But you would need to correct the events that control the device to point to the new device again


Wim

[Platopus]

Hi Wim,

I am using HS4 on a Windows 10 PC.

I do not believe the specific hue light is the issue as the problem has manifested itself on different lights and sensor. In any case I have done what you suggested and stopped the plugin and removed the light then restarted the plugin. I have actually deleted the event so there are no trace and JowiHue still looks like it lost its connection to deCONZ as I cannot control any zigbee devices.

What I had failed to notice was that from Phoscon when I try to control a different Hue component (lightstrip) it toggles between on and off about 5 times then shut off. And on a zigbee plug it toggles between on and off non stop until I disconnect it.

I then rebooted the server and now from Phoscon all is fine but JowiHue still does not appear to be connected to deCONZ as I cannot control any devices within Homeseer.



I have also disable the Lutron plugin but the deCONZ connection is still broken.

Your help is really appreciated, any ideas what else I should be looking at?

[Platopus]

Hi Wim,

In the log I noticed that below each error log entry there was a debug line with a ref id which I finally realized that it was referring to the device id. I proceeded by deleting the device (hue light) and then another log for another hue light would pop up. I ended up deleting all the lights and plugs and rescan them and now everything is working again. I turned on the Lutron plugin and created a simple rule and it did not break anything.

I am at a loss as to what happened and hopefully this was a fluke as I am preparing to add 20-30 more hue lights and when I need to delete and rescan lights it takes forever to update all the events.

Thank you for your support.

Richard

[w.vuyk]

I am at loss too. Byt the sound of what you are saying on the Phoscon effects I think deCONZ itself was in error somehow. The plugin will have received the same effect as Phoscon (as those are on a 'equal' level in receiving the updates). I am guessing the plugin has created faulty devices because of that. But that is really only guessing. I am glad to hear it got resolved!