mine is back working again today, i did notice yesterday that phoscon.de was down, why the hell is this stick relying on that website to work?!?!? it should be locale not relying on a webserver
I also lost all access to the HA deCONZ add-on yesterday/last night and was up trying to figure out why till late.
I agree that you can disconnect your internet connection and usually, everything continues to work as expected. However, it seems too much of a coincidence that the Phoscon website was down the entire time I couldn’t start my deCONZ add-on & since it’s back, everything started fine…
I think this is the first time (or possibly 2nd time, as I don’t trust my memory) that this has happened over the period of 7 years. There are no aspects except for this discovery service used during installation that is related to noon local communication. Perfect storm is probably a good description of the issue
Hi everyone, i have a bug since some time that the state of an Blub is not correctly updated in the HA dashboard. So i change the color in HA, the blub changes in real live, but the Icon in HA of the blub still hast the old color. Iam using the Deconz addon.
I saw your other more detailed report Deconz Color change not reflected in HA UI
What bulb is it? Without knowing all details it sounds as if signaling is broken for that device in some way
Hi, thanks for the reply. Its multiple devices but most of them are HUE Bulbs.
So you have the issue with multiple bulbs? Or all bulbs?
And its only when changing color, or with any state change?
How are you hosting and running deconz?
My integration has stopped working again, with the same crashing on startup issue as before.
Phoscon.de is also down, funnily enough. Anyone else having the issue again?
Yes, I’m having the same issue. This is no coincidence. I’m moving away from Conbee ASAP now, I can’t have my lights and heating relying on the availability of a website.
Strange, all working fine for me. This was also the case when this was last mentioned. Feels like there must be something else going on here.
Is the error on deconz or integration? Can you share logs?
It’s the deConz add-on that is crashing. This is what I get in the logs. The integration actually runs for a couple of minutes when it first starts up, but then it dies. It seems to fail when it starts the VNC server, but there doesn’t seem to be any way of disabling that,
[10:57:40] INFO: Starting VNC server (local/yes)...
[09:57:40] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
In exit
2023/04/07 10:57:40 [notice] 124#124: signal 15 (SIGTERM) received from 115, exiting
Closing socket listening at 127.0.0.1:5901
2023/04/07 10:57:40 [notice] 1698#1698: exiting
2023/04/07 10:57:40 [notice] 1698#1698: exit
2023/04/07 10:57:40 [notice] 124#124: signal 17 (SIGCHLD) received from 1698
2023/04/07 10:57:40 [notice] 124#124: worker process 1698 exited with code 0
2023/04/07 10:57:40 [notice] 124#124: exit
[09:57:40] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Thanks I’ve reported it to Deconz devs
2 Likes
System is up again. Everyone affected by the service being down are you running the deConz addon?
I still don’t understand how this can happen, reviewed the code in deCONZ many times. As a workaround the query to the discovery server can be disabled in the Phoscon App > Menu > Gateway Settings page.
One thing I wonder, are there reports of this for setups which don’t use the HA add-on?
Yep, working again now coinciding with phoscon.de being back. Had to start the addon manually.
Definitely weird behaviour. It not only refuses to start when phoscon.de is down, but it must be shutting down in the middle of normal operation when the site goes down. My log is identical to the one posted by grebble.
To try and gain some clarity I blocked my home assistant server from accessing the internet at all via my router, and deconz started up normally. Here’s the relevant bit of the log during this entirely local startup:
[18:17:24] INFO: Websockify waiting for VNC to start
[18:17:24] INFO: Running the deCONZ OTA updater...
[18:17:24] INFO: Running the IKEA OTA updater...
[18:17:24] INFO: Running the OSRAM LEdvance OTA updater...
[18:17:24] INFO: Can't fetch data from osram!
[18:17:25] INFO: Starting VNC server (local/yes)...
[18:17:25] INFO: Starting websockify...
WebSocket server settings:
- Listen on 127.0.0.1:5901
- Flash security policy server
- Web server. Web root: /usr/share/novnc
- No SSL/TLS support (no cert file)
- proxying from 127.0.0.1:5901 to 127.0.0.1:5900
[18:17:28] INFO: deCONZ waiting for VNC to start
[18:17:28] INFO: Starting the deCONZ gateway...
So the problem must be ocurring after the “Starting VNC server (local/yes)” entry, because when phoscon.de is down this line is immediately followed by “WARNING: Halt add-on”.
Am i the only one who has problems with the latest update? (6.19.0)
Since the update my switches (aqara) take more time to react (light didnt turn on immediately)!
I reverted to 6.18.0 and have no problems. Strange…
No issues here so far. Hue, innr, Aquara and tint devices
1 Like
No problems here - however from Aqara I only have a couple of temperature sensors, rest is from other brands.
1 Like
It’s happened again…phoscon.de is down once more and down went my devices. I’ve now blocked phoscon.de from my router, restarted the add-on and it’s all fine. It’s going to stay that way now.