Error: known as ip address for a bridge, but is no longer recognised as bridge

[bobsilver1]

Getting the error "known as ip address for a bridge, but is no longer recognised as bridge" from JowiHue. Had been using the HS3 version and just upgraded to the HS4. Ive deleted the bridge and rescanned it and all my lights. Keep getting this error. I did suffer a power and internet outage. Since the restoration I cant seem to get rid of this error.

Any suggestions?

Log file attached

[bobsilver1]

More current log file with additional errors.

bobsilver

[w.vuyk]

You say you upgraded to the new version of the plugin. If you are running on Windows, did you allow the HS4 version of the plugin through the firewall? There probably has been a popup with that question during the first start of the plugin. Easiest way ot check on that is temporarly disabling the Windows Firewall.

Wim

*edit* To allow the plugin on the firewall you need to add "HSPI_JowiHue.exe" in the firewall rules and allow all network actions

[bobsilver1]

My problem started on the HS3 version of JowiHue. In an attempt to solve it I upgraded to the HS4 version. No change. I looked at the Windows firewall settings. The HS3 Jowihue shows up but there is no HSPI_JowiHue.exe listed at all. There are 4 instances of the HS3 Jowihue listed though. I have tried toggling the firewall on and off. Still has the issues. Attached is the debug log and screenshot of settings for you.

[w.vuyk]

The page you are showing is coming from the HS4 plugin. Which is active then.

I see a line in the log you posted earlier (your last post has no log:

0/26/2021 1:39:45 AM JowiHue Error Error: (GetJsonCommand):Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.

Which suggests that the Philips Hue bridge is either denying access from the HS machine or something else is wrong with the Philips Hue bridge at this point.
Can you do the following two tests for me?

Open a browser on the HS machine itself and fill in the address http://<your hue bridge IP address>/description.xml
If it finds information here, copy it and show me?

in the same browser on the HS machine go to https://discovery.meethue.com/ Does the reply in the browser show you the (expected) address of the Philips Hue bridge or is it empty.

If both are empty or giving unexpected results, could you try and restart the Philips Hue bridge and after the bridge is back, the Homeseer machine?

If you do the tests again after that, does this correct the issues?

Wim

*edit* corrected the description.html to description.xml

[w.vuyk]

bobsilver1 Did the issue get resolved?

[bobsilver1]

Thanks for checking in. Well I did a restore of my server to try and get back to a known working situation. That did not solve the issue. In addition to this plugin I was also having issues with Bond and one other. So after many frustrated hours I went in a whole new direction. I built a Homebridge server with Apple Homekit. Turns out that one of my great displeasure with HS4 was a lack of a good mobile client. I hadnt used Homekit before this and found with the Homebridge setup it is now a fantastic mobile experience. I have tied it together with all my hubs, cloud accounts and now even Homeseer.

So let me bring it back to my Hue issues. Since turn off many of the HS4 plugins I still have Jowihue active. My errors have gone away but one of the remaining issues is the Warning on slow hue hub response. I am no longer using HS to control my Hue lights except for events where I use an IR command to trigger a Hue scene. This is working fine. I no longer have errors just the slow hub warnings. I changed the polling to 120 sec since I dont need the status info for my scene triggers. I dont know what is causing the hub slow down. Too many devices polling it? I had been using Alexa, HS and the Hue app.

Lastly Ill say this. Ive been an HS user for 15 or more years going back to V1. The lack of a suitable mobile client was very disappointing. The Homebridge Homekit solution (while a pain to configure due to inadequate configuration instructions (its all hacker driven and free so I cant complain) is now flawless. It is super fast and beautifully configured. The last piece was to connect it to HS. Since the 2 remaining pieces I needed were Zwave integration and the ability to use infrared triggers. So HS remains an active component of my automation but has been significantly depreciated to the function of a bridge for Zwave and IR.

Again thanks for the help and concern. If anyone wants to learn more about Homebridge and Homekit PM me.

Bob