My ZigBee devices connected to deConz are becoming constantly unavailable without any apparent reason. I have multiple brands including Phillips and Aqara. They're all bettery-run so none are acting as repeaters.
docker_version | 19.03.8
host_os | HassOS 4.10
os_version | 4.19.126-v8
python_version | 3.7.7
supervisor | 228
version | 0.112.0
frontend | 20200603.3 - latest
deconz | 5.3.6
Nothing shows up in the logs when this happens.
Duplicate of https://github.com/home-assistant/hassio-addons/issues/1438, wasn't quite sure which repo to post it on (sorry)
Most likely not related to the integration
They worked fine a few days ago... I'll continue investigating, thanks!
I upgraded to latest Deconz just now and have the exact same issue. Restarted Deconz an HA multiple times, all Zigbee devices just disconnect after a while (looks as if it crashes). Gonna restore to a snapshow as we speak...
I do remember Deconz having this exact same issue a few versions ago. It happened multiple times a day. An update fixed that then.
If it works please let me know, it's driving me crazy 🤣
deconz documentation
deconz source
(message by IssueLinks)
I have exactly the same problem since the latest Deconz update...
FWIW, I was having this problem since the latest update, but upon closer inspection of the logs, I saw that a firmware update was available for my Conbee II. All my devices are stable once again with the new firmware.
For me the problem still exists sadly, I already have the latest firmware for my Conbee (not II)
I’ve tried updating the firmware and rebooting but each time I go back in to deconz it tells me the same firmware update is available. I can confirm that this issue happened prior to the HA core update but I’ve also now updated to the latest core in the hope that it was an incompatibility issue, I can sadly confirm that it wasn’t.
I've just updated the firmware from the Windows 10 application. If the issue is fixed I'll let you guys know
Well, that did not seem to help
For the time being I've migrated to ZHA, once this is sorted I'll probably move back
If it works please let me know, it's driving me crazy 🤣
I restored my snapshot (and that way downgraded Deconz) I did have some issues with losing connections after that still. Then rebooted the hardware (OS, so not just restart HA server). After that seems stable again like before (no lost connections for 48 hours).
By account of previous comments this is related to latest deconz release. Closing this issue since it is not related to the integration per se.
Where should this issue be posted then?
I dont get where else this should be posted then either.. The issue in the hassio-addons was closed too?
Deconz github if it's related to an upgrade of deconz.
They told me it's related to HA, running it standalone has no issues
It is definitely related to HA in some way. I downgraded Deconz to 5.3.2 by restoring HA. I noticed a lot of issues still after that, after that I rebooted the OS entirely (not just HA Server) and also upgraded to 112. Zigbee is more stable now than with Deconz update, BUT all my devices still become unavailable for 15 seconds after a certain amount of time (sometimes after an hour, sometimes after 12 hours, very random). Unfortunately sometimes this happens right when I want to trigger something (which is rare, but still unreliable).
I had this exact issues a few HA versions ago. To say it's entirely Deconz is not correct, since I reverted the update.
Ok then. Share logs showcasing the issue
That's the thing, the logs don't really give that much info:
HA Log:
2020-07-02 23:25:30 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"lastannounced":null,"lastseen":"2020-07-02T21:25:30Z","manufacturername":"dresden elektronik","modelid":"RaspBee","name":"Configuration tool 1","swversion":"0x264a0700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:05:d7:cf-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:05:d7:cf-01"}
2020-07-02 23:25:50 INFO (MainThread) [volvooncall.volvooncall] Updating
2020-07-02 23:25:54 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-07-02 23:25:54 DEBUG (MainThread) [pydeconz.websocket] Reconnecting to deCONZ in 15.
2020-07-02 23:26:09 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-07-02 23:26:09 DEBUG (MainThread) [pydeconz.websocket] Websocket running
2020-07-02 23:26:09 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"lastannounced":null,"lastseen":"2020-07-02T21:26:09Z","manufacturername":"dresden elektronik","modelid":"RaspBee","name":"Configuration tool 1","swversion":"0x264a0700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:05:d7:cf-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:05:d7:cf-01"}
Deconz log:
15:16:38:909 APS-DATA.indication request id: 188 -> finished
15:16:38:909 APS-DATA.request id: 188 erase from queue
15:16:38:909 ZDP status = 0x00 -> SUCCESS
15:16:38:910 ZDP Mgmt_Lqi_rsp zdpSeq: 45 from 0x00212EFFFF05D7CF total: 5, startIndex: 4, listCount: 1
15:16:38:910 * neighbor: 0x00158D00045D44DE (0x0B66), LQI: 255, relation: 0x01 rxOnWHenIdle: 0
=======AT 15:07:02 devices became unreachable=====
15:17:10:432 don't close database yet, keep open for 900 seconds
15:17:10:434 Remove websocket 172.30.32.1:51086 after error Unknown error
172.30.32.2 - - [03/Jul/2020:15:17:10 +0200] "GET /api/2C916F87F2/groups?_=1593778553416 HTTP/1.1" 200 1155 "https://rlc616egup6ikom710nd2uv6k3qg9m56.ui.nabu.casa/api/hassio_ingress/Y6CjyPLqCkHCWJS8gU3lwF1Iw86AR-NMdch8hfC_JaM/pwa/index.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0"
15:17:10:439 APS-DATA.indication srcAddr: 0x27e9, srcEp: 0x02 dstAddrMode: 2, profile: 0x0104, cluster: 0x0001, lqi: 111, rssi: -80
15:17:10:440 no button map for: RWL021 ep: 0x02 cl: 0x0001 cmd: 0x0A pl[0]: 021
15:17:10:440 ZCL attribute report 0x00178801080CDF75 for cluster: 0x0001, ep: 0x02, frame control: 0x18, mfcode: 0x0000
The deconz log is unnecessary, the part from the ha log you shared only show the raspbee device, which isn't relevant more than to show that I should probably ignore it completely. New logs please :)
At the exact time that all Zigbee devices were unavailable, I saw these lines. Perhaps something else causing stuff to hang, which then disconnects HA to Deconz? Configuration files are all ok though... Very strange.
2020-07-08 16:37:38 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.cpu_temperatuur is taking over 10 seconds
2020-07-08 16:37:43 ERROR (SyncWorker_7) [homeassistant.components.command_line.sensor] Timeout for command: cat /sys/class/thermal/thermal_zone0/temp
Disable those and try again
Disable those and try again
Ok, I will keep an eye to the history now that I removed that. I also noticed my iPhone was registered multiple times as a device. At the same time that I got another short disconnect (after removing previous sensor lines), I saw that error in log. Removed those as well.
So once again the devices had a brief moment of unavailable. I see no logs at that exact time. The logs 3 minutes before all devices became unavailable were the following three logs. So I'm not sure this has anything to do with it. Just to clarify, I have deleted home-assistant_v2.db multiple times now (I saw recorder, so figured perhaps corrupt database). The last time I deleted the database was around 24 hours ago.
FIRST ONE
Logger: homeassistant.components.recorder.util
Source: components/recorder/util.py:92
Integration: Recorder (documentation, issues)
First occurred: 19:34:09 (78 occurrences)
Last logged: 20:51:36
Error executing query: (sqlite3.OperationalError) database is locked [SQL: SELECT states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created FROM states WHERE (states.domain IN (?, ?, ?, ?, ?) OR states.last_changed = states.last_updated) AND states.last_updated > ? AND states.entity_id IN (?) AND states.last_updated < ? ORDER BY states.entity_id, states.last_updated] [parameters: ('climate', 'device_tracker', 'humidifier', 'thermostat', 'water_heater', '2020-07-08 18:39:37.044000', 'sensor.load_1m', '2020-07-08 18:40:07.928000')] (Background on this error at: http://sqlalche.me/e/e3q8)
Error executing query: (sqlite3.OperationalError) database is locked [SQL: SELECT states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created FROM states WHERE (states.domain IN (?, ?, ?, ?, ?) OR states.last_changed = states.last_updated) AND states.last_updated > ? AND states.entity_id IN (?) AND states.last_updated < ? ORDER BY states.entity_id, states.last_updated] [parameters: ('climate', 'device_tracker', 'humidifier', 'thermostat', 'water_heater', '2020-07-07 18:51:08.849000', 'light.pc', '2020-07-08 18:51:08.849000')] (Background on this error at: http://sqlalche.me/e/e3q8)
Error executing query: (sqlite3.OperationalError) database is locked [SQL: SELECT states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created FROM states WHERE (states.domain IN (?, ?, ?, ?, ?) OR states.last_changed = states.last_updated) AND states.last_updated > ? AND states.entity_id IN (?) AND states.last_updated < ? ORDER BY states.entity_id, states.last_updated] [parameters: ('climate', 'device_tracker', 'humidifier', 'thermostat', 'water_heater', '2020-07-08 18:51:08.849000', 'light.pc', '2020-07-08 18:51:12.496000')] (Background on this error at: http://sqlalche.me/e/e3q8)
Error executing query: (sqlite3.OperationalError) database is locked [SQL: SELECT states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created FROM states WHERE (states.domain IN (?, ?, ?, ?, ?) OR states.last_changed = states.last_updated) AND states.last_updated > ? AND states.entity_id IN (?) AND states.last_updated < ? ORDER BY states.entity_id, states.last_updated] [parameters: ('climate', 'device_tracker', 'humidifier', 'thermostat', 'water_heater', '2020-07-07 18:51:16.453000', 'light.pc', '2020-07-08 18:51:16.453000')] (Background on this error at: http://sqlalche.me/e/e3q8)
Error executing query: (sqlite3.OperationalError) database is locked [SQL: SELECT states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created FROM states WHERE (states.domain IN (?, ?, ?, ?, ?) OR states.last_changed = states.last_updated) AND states.last_updated > ? AND states.entity_id IN (?) AND states.last_updated < ? ORDER BY states.entity_id, states.last_updated] [parameters: ('climate', 'device_tracker', 'humidifier', 'thermostat', 'water_heater', '2020-07-08 18:50:29.880000', 'media_player.multispeakers_cast', '2020-07-08 18:51:29.890000')] (Background on this error at: http://sqlalche.me/e/e3q8)
SECOND ONE
Logger: homeassistant.components.recorder.util
Source: components/recorder/util.py:32
Integration: Recorder (documentation, issues)
First occurred: 19:34:09 (26 occurrences)
Last logged: 20:51:36
Error executing query: (sqlite3.OperationalError) database is locked [SQL: SELECT states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created FROM states WHERE (states.domain IN (?, ?, ?, ?, ?) OR states.last_changed = states.last_updated) AND states.last_updated > ? AND states.entity_id IN (?) AND states.last_updated < ? ORDER BY states.entity_id, states.last_updated] [parameters: ('climate', 'device_tracker', 'humidifier', 'thermostat', 'water_heater', '2020-07-08 18:39:37.044000', 'sensor.load_1m', '2020-07-08 18:40:07.928000')] (Background on this error at: http://sqlalche.me/e/e3q8)
Error executing query: (sqlite3.OperationalError) database is locked [SQL: SELECT states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created FROM states WHERE (states.domain IN (?, ?, ?, ?, ?) OR states.last_changed = states.last_updated) AND states.last_updated > ? AND states.entity_id IN (?) AND states.last_updated < ? ORDER BY states.entity_id, states.last_updated] [parameters: ('climate', 'device_tracker', 'humidifier', 'thermostat', 'water_heater', '2020-07-07 18:51:08.849000', 'light.pc', '2020-07-08 18:51:08.849000')] (Background on this error at: http://sqlalche.me/e/e3q8)
Error executing query: (sqlite3.OperationalError) database is locked [SQL: SELECT states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created FROM states WHERE (states.domain IN (?, ?, ?, ?, ?) OR states.last_changed = states.last_updated) AND states.last_updated > ? AND states.entity_id IN (?) AND states.last_updated < ? ORDER BY states.entity_id, states.last_updated] [parameters: ('climate', 'device_tracker', 'humidifier', 'thermostat', 'water_heater', '2020-07-08 18:51:08.849000', 'light.pc', '2020-07-08 18:51:12.496000')] (Background on this error at: http://sqlalche.me/e/e3q8)
Error executing query: (sqlite3.OperationalError) database is locked [SQL: SELECT states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created FROM states WHERE (states.domain IN (?, ?, ?, ?, ?) OR states.last_changed = states.last_updated) AND states.last_updated > ? AND states.entity_id IN (?) AND states.last_updated < ? ORDER BY states.entity_id, states.last_updated] [parameters: ('climate', 'device_tracker', 'humidifier', 'thermostat', 'water_heater', '2020-07-07 18:51:16.453000', 'light.pc', '2020-07-08 18:51:16.453000')] (Background on this error at: http://sqlalche.me/e/e3q8)
Error executing query: (sqlite3.OperationalError) database is locked [SQL: SELECT states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created FROM states WHERE (states.domain IN (?, ?, ?, ?, ?) OR states.last_changed = states.last_updated) AND states.last_updated > ? AND states.entity_id IN (?) AND states.last_updated < ? ORDER BY states.entity_id, states.last_updated] [parameters: ('climate', 'device_tracker', 'humidifier', 'thermostat', 'water_heater', '2020-07-08 18:50:29.880000', 'media_player.multispeakers_cast', '2020-07-08 18:51:29.890000')] (Background on this error at: http://sqlalche.me/e/e3q8)
THIRD ONE
Logger: aiohttp.server
Source: components/recorder/util.py:75
First occurred: 19:34:09 (22 occurrences)
Last logged: 20:51:36
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 1284, in _execute_context
cursor, statement, parameters, context
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/default.py", line 590, in do_execute
cursor.execute(statement, parameters)
sqlite3.OperationalError: database is locked
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/real_ip.py", line 39, in real_ip_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 73, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 129, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/history/__init__.py", line 475, in get
minimal_response,
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(self.args, *self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/history/__init__.py", line 502, in _sorted_significant_states_json
minimal_response,
File "/usr/src/homeassistant/homeassistant/components/history/__init__.py", line 138, in _get_significant_states
states = execute(query)
File "/usr/src/homeassistant/homeassistant/components/recorder/util.py", line 75, in execute
result = list(qry)
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/orm/query.py", line 3481, in __iter__
return self._execute_and_instances(context)
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/orm/query.py", line 3506, in _execute_and_instances
result = conn.execute(querycontext.statement, self._params)
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 1020, in execute
return meth(self, multiparams, params)
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection
return connection._execute_clauseelement(self, multiparams, params)
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_clauseelement
distilled_params,
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 1324, in _execute_context
e, statement, parameters, cursor, context
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 1518, in _handle_dbapi_exception
sqlalchemy_exception, with_traceback=exc_info[2], from_=e
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/util/compat.py", line 178, in raise_
raise exception
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 1284, in _execute_context
cursor, statement, parameters, context
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/default.py", line 590, in do_execute
cursor.execute(statement, parameters)
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) database is locked
[SQL: SELECT states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created
FROM states
WHERE (states.domain IN (?, ?, ?, ?, ?) OR states.last_changed = states.last_updated) AND states.last_updated > ? AND states.entity_id IN (?) AND states.last_updated < ? ORDER BY states.entity_id, states.last_updated]
[parameters: ('climate', 'device_tracker', 'humidifier', 'thermostat', 'water_heater', '2020-07-08 17:33:01.245000', 'sensor.load_1m', '2020-07-08 17:34:03.011000')]
(Background on this error at: http://sqlalche.me/e/e3q8)
Can you enable debug for deconz in hass for more detailed logs,
Can you enable debug for deconz in hass for more detailed logs,
Allright, enabling debug in configuration now. Will report back once it happens again with logs
I have a couple of hours of logs as well...not sure which parts would be helpful.
Every period of "unavailable" in the log file has a corresponding entry in the log file which like this...
2020-07-08 17:23:44 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-07-08 17:23:44 DEBUG (MainThread) [pydeconz.websocket] Reconnecting to deCONZ in 15.
2020-07-08 17:23:59 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-07-08 17:24:31 DEBUG (MainThread) [pydeconz.websocket] Websocket running
Many...but not all, have the immediate lines _AFTER_, is a script trigger fired from a zigbee motion sensor
2020-07-08 17:24:32 INFO (MainThread) [homeassistant.components.automation] Executing room-occupancy-trigger
2020-07-08 17:24:32 INFO (MainThread) [homeassistant.components.automation] room-occupancy-trigger: Running script
2020-07-08 17:24:32 INFO (MainThread) [homeassistant.components.automation] room-occupancy-trigger: Executing step call service
2020-07-08 17:24:32 INFO (MainThread) [homeassistant.components.automation] Executing room-occupancy-trigger
2020-07-08 17:24:32 INFO (MainThread) [homeassistant.components.automation] room-occupancy-trigger: Executing step call service
Another clip show more info
2020-07-08 17:26:24 INFO (MainThread) [homeassistant.components.automation] Executing room-unoccupied
2020-07-08 17:26:24 INFO (MainThread) [homeassistant.components.automation] room-unoccupied: Running script
2020-07-08 17:26:24 INFO (MainThread) [homeassistant.components.automation] room-unoccupied: Executing step call service
2020-07-08 17:26:24 INFO (MainThread) [homeassistant.components.automation] Executing Room Unoccupied
2020-07-08 17:26:24 INFO (MainThread) [homeassistant.components.automation] Room Unoccupied: Running script
2020-07-08 17:26:24 INFO (MainThread) [homeassistant.components.automation] Room Unoccupied: Executing step call service
2020-07-08 17:26:24 DEBUG (MainThread) [pydeconz.gateway] Sending "put" "{'on': False}" to "172.30.33.0 /groups/6/action"
2020-07-08 17:26:27 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-07-08 17:26:27 DEBUG (MainThread) [pydeconz.websocket] Reconnecting to deCONZ in 15.
2020-07-08 17:26:33 DEBUG (MainThread) [pydeconz.gateway] HTTP request response: [{'success': {'/groups/6/action/on': False}}]
2020-07-08 17:26:42 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-07-08 17:26:46 DEBUG (MainThread) [pydeconz.websocket] Websocket running
2020-07-08 17:26:46 INFO (MainThread) [homeassistant.components.automation] Executing room-occupancy-trigger
2020-07-08 17:26:46 INFO (MainThread) [homeassistant.components.automation] room-occupancy-trigger: Running script
2020-07-08 17:26:46 INFO (MainThread) [homeassistant.components.automation] room-occupancy-trigger: Executing step call service
2020-07-08 17:26:46 INFO (MainThread) [homeassistant.components.automation] Executing room-occupancy-trigger
2020-07-08 17:26:46 INFO (MainThread) [homeassistant.components.automation] room-occupancy-trigger: Executing step call service
2020-07-08 17:26:46 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"lastannounced":null,"lastseen":"2020-07-08T21:26:46Z","manufacturername":"Philips","modelid":"LLC011","name":"bloom-1","swversion":"5.127.1.26581","type":"Color light","uniqueid":"00:17:88:01:00:1d:24:7a-0b"},"e":"changed","id":"3","r":"lights","t":"event","uniqueid":"00:17:88:01:00:1d:24:7a-0b"}
2020-07-08 17:26:46 INFO (MainThread) [homeassistant.components.automation] room-occupancy-trigger: Executing step call service
2020-07-08 17:26:46 INFO (MainThread) [homeassistant.components.automation] room-occupancy-trigger: Executing step call service
2020-07-08 17:26:46 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"lastannounced":null,"lastseen":"2020-07-08T21:26:46Z","manufacturername":"Philips","modelid":"LCT016","name":"bathrrom-vanity-1","swversion":"1.50.2_r30933","type":"Extended color light","uniqueid":"00:17:88:01:03:ee:53:fc-0b"},"e":"changed","id":"12","r":"lights","t":"event","uniqueid":"00:17:88:01:03:ee:53:fc-0b"}
2020-07-08 17:26:47 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"lastannounced":null,"lastseen":"2020-07-08T21:26:47Z","manufacturername":"Philips","modelid":"LCT016","name":"livingroom-light-table","swversion":"1.50.2_r30933","type":"Extended color light","uniqueid":"00:17:88:01:03:bd:5d:b6-0b"},"e":"changed","id":"4","r":"lights","t":"event","uniqueid":"00:17:88:01:03:bd:5d:b6-0b"}
2020-07-08 17:26:48 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"lastannounced":null,"lastseen":"2020-07-08T21:26:48Z","manufacturername":"Philips","modelid":"LCT012","name":"livingroom-light-candle1","swversion":"1.50.2_r30933","type":"Extended color light","uniqueid":"00:17:88:01:03:ba:15:92-0b"},"e":"changed","id":"5","r":"lights","t":"event","uniqueid":"00:17:88:01:03:ba:15:92-0b"}
...
Let me know if you would like a zip file of the log or anything else that might be helpful
Another odd bit... "connection closed by client."
2020-07-08 17:14:17 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-07-08 17:14:17 DEBUG (MainThread) [pydeconz.websocket] Reconnecting to deCONZ in 15.
2020-07-08 17:14:27 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.2849320784] Connection closed by client
2020-07-08 17:14:32 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-07-08 17:14:32 DEBUG (MainThread) [pydeconz.websocket] Websocket running
2020-07-08 17:14:32 INFO (MainThread) [homeassistant.components.automation] Executing room-occupancy-trigger
That connection closed by client is probably a web client you've closed.
Well there is not much to go on. Indeed the connection to Deconz goes down for some reason.
How are you running deconz? What other integrations are you running in parallell? I don't think it's an issue with the integration but something else in your environment.
Not a lot going on here....
Was working without trouble untill about two weeks ago.
Always available and working from the Phoscon app, when unavailable in HA
I DID have a problem while ago where the Integration app showed TWO identical connections -- both with the same Config Entry Name (long string of numbers.). This was after the OS Update. A reboot, I think, fixed it.
the mqtt server is running on a separate Pi and not in use. I can remove it from HA if helpful.
I would just flush the whole thing and rebuild it ... but I have 47 devices that would need to be reconnected. Not thrilled about that idea.
deconz via an ConBeeII in the usb on the same Pi as HA
Accessing the Phoscon app via the integration panel, and linked in the HA left rail
Phoscon has a password t access... and had to be activated in the Config settings
I can can also VNC into the app on port :5900
automation triggered on a motion detector and dispatched via a service call (currently oversimplified, but functional here.)
- alias: Room Occupancy
trigger:
platform: state
entity_id:
- input_boolean.bathroom_occupancy
- input_boolean.bedroom_occupancy
- input_boolean.kitchen_occupancy
to: 'on'
condition:
action:
- service: scene.turn_on
data_template:
entity_id: scene.{{ trigger.entity_id.split('.')[1].split('_', 1)[0] | lower }}_daytime_scene
That's actually the wrong code... sorry about that. (and most likely not relevant. Of out 27 dropouts today... 21 of them are immediately followed by motion detector trigger. I know, most likely not related. But oddly frequent.
- alias: room-occupancy-trigger
initial_state: true
trigger:
# the sensor list for room occupancy motion sensors
- entity_id:
- binary_sensor.motion_sensor_6
- binary_sensor.motion_sensor_7
- binary_sensor.motion_sensor_8
platform: state
to: 'on'
# Occupied is occupied, it's not conditional
condition: []
action:
- service: timer.start
data_template:
entity_id: "timer.{{ trigger.to_state.attributes.friendly_name.split(' ', 1)[0] | lower }}_motion_timer"
- service: input_boolean.turn_on
data_template:
entity_id: "input_boolean.{{ trigger.to_state.attributes.friendly_name.split(' ', 1)[0] | lower }}_occupancy"
Just got the short disconnect again after 10 hours now. There only one entry in log:
Logger: asyncio
Source: components/hassio/ingress.py:154
First occurred: 9:36:59 (36 occurrences)
Last logged: 9:37:00
socket.send() raised exception
This happened while I was in HA Server and I noticed everything hanged for that moment as well. Perhaps something is locking my system up, which then re-connects to Deconz?
Also in Deconz at that same moment this happened:
09:36:24:849 skip binding for attribute reporting of ep: 0x00 cluster 0x0101 (end-device might sleep)
09:36:58:636 Remove websocket 172.30.32.1:51808 after error Unknown error
09:36:58:804 New websocket 172.30.32.1:35438 (state: 3)
09:37:00:732 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
09:37:02:822 ZCL attribute report 0x90FD9FFFFE137215 for cluster: 0x0000, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:37:05:849 skip binding for attribute reporting of ep: 0x00 cluster 0x0101 (end-device might sleep)
09:37:09:370 Current channel 25
09:37:09:378 Device TTL 897 s flags: 0x7
09:37:10:392 dev /dev/ttyAMA0
09:37:10:395 GW firmware version: 0x264a0700
09:37:10:395 GW firmware version is up to date: 0x264a0700
09:37:10:850 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
09:37:15:849 skip binding for attribute reporting of ep: 0x00 cluster 0x0101 (end-device might sleep)
09:37:17:763 no button map for: lumi.sensor_magnet ep: 0x01 cl: 0x0000 cmd: 0x0A pl[0]: 002
09:37:17:763 ZCL attribute report 0x00158D0004264F65 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x1234
09:37:17:764 0x00158D0004264F65 extract Xiaomi special attribute 0xFF02
09:37:17:764 64 on/off 0
09:37:17:764 01 battery 3035 (0x0BDB)
09:37:17:764 03 unsupported index (data type 0x21)
09:37:17:764 04 unsupported index (data type 0x24)
09:37:17:764 05 unsupported index (data type 0x21)
09:37:17:764 06 unsupported index (data type 0x20)
09:37:20:849 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
09:37:25:849 skip binding for attribute reporting of ep: 0x00 cluster 0x0006 (end-device might sleep)
09:37:30:849 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
09:37:35:110 ZCL attribute report 0x000B57FFFEEB6D74 for cluster: 0x0000, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:37:35:849 skip binding for attribute reporting of ep: 0x00 cluster 0x0006 (end-device might sleep)
09:37:40:849 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
09:37:45:849 skip binding for attribute reporting of ep: 0x00 cluster 0x0006 (end-device might sleep)
09:37:47:506 ZCL attribute report 0x7CB03EAA00B035A2 for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
09:37:47:516 ZCL attribute report 0x7CB03EAA00B035A2 for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
09:37:50:850 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
09:37:54:349 remove outdated neighbor 0xB6E6
09:37:55:850 skip binding for attribute reporting of ep: 0x00 cluster 0x0006 (end-device might sleep)
09:38:00:016 ZCL attribute report 0x90FD9FFFFE6FC60E for cluster: 0x0000, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:38:00:850 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
09:38:05:849 skip binding for attribute reporting of ep: 0x00 cluster 0x0006 (end-device might sleep)
09:38:09:365 Current channel 25
I have the exact same issue so there's something weird going on.
So you mean you notice other stuff get locked up as well?
So you mean you notice other stuff get locked up as well?
Yes, I noticed the entire system was hanging briefly. I couldn't open settings for instance.
Since I've read that SD cards can become corrupt pretty quickly (especially if you write/change a lot with Lovelace/automations) it can go hard. I've already replaced the SD card twice and also noticed those times stability issues at random places. I figured, perhaps the SD card has something to do with it as well. I had a thought that maybe the entire system froze sometimes because the recorder couldn't write it off on time. I also noticed huge CPU spikes lately. So I created a snapshop, used a fresh (never before used, still sealed) sd card with a clean HA install on it. I also re-installed clean HA on the old SD card to test them both. I immediately noticed that the new SD card was flashed WAY faster (or should I say, the old one WAY slower). So I had high hopes the SD card was going bad.
After that I installed Deconz (latest) and did not encounter those weird issues.
Then I restored my snapshot, without selecting Deconz. So I ended up with a clean Deconz that did work, on the latest update and my old snapshot back. I had to re-pair all my Zigbee devices (around 36) and had some issues with Zigbee going down when I activated my Zwave.me stick again. But I changed some settings and right now all devices are working with the latest Deconz (though I can't seem to update the Conbee II, but that's a common Deconz issue). So the first issue (losing all connections after even a few seconds with latest Deconz) is now gone. I'll keep my eye on my sensor states to see if they lose connections briefly.
Perhaps my issue was the sd card going bad, resulting recorder going haywire, causing huge cpu spikes, freezing evertything and maybe that caused the sockets to close/disconnect and re-connect. Also CPU load is way more stable now. You can clearly see that it went haywire, then a few hours flat (because of re-installing HA), then it came back but a lot more stable (then it went back flat because I accidentally removed it from recorder integration).
I'll update my post tomorrow and I hope all is good now. Not saying that everyone has SD card problems here, but it's worth checking out. In the meantime I changed the recorder integration to limit the writings.
If this starts up again. Try disabling the deConz integration to see if that changes anything and if not also remove deconz addon
Same issue for me with 0.112.4. Multiple disconnects (status unavailable) with Deconz. I don't believe I had the issue with 0.111.
RPI4 running both HA and Raspbee.
Same issue for me with 0.112.4. Multiple disconnects (status unavailable) with Deconz. I don't believe I had the issue with 0.111.
RPI4 running both HA and Raspbee.
Have you tried removing the Deconz integration and adding it again? Keep in mind that you have to change entity id’s if you have manually changed those.
Since I reset everything I haven’t had any issues (over 48 hours now). knocks on wood
I’d advise making a backup first, then removing Deconz integration and re-adding it. If it’s solved, then great! (Still have to manually change entity id’s you edited, but finally fixed) Please share so others can try and maybe that’s the fix. If not: restore your snapshot so you don’t have to manually change entity id’s.
Intermittent unavailability (exactly 15 seconds) on a clean test rig.
To attempt to eliminate or recreate the problem took the following steps:
All Philip Hue bulbs and led strips (all types)
All Xiaomi sensors (none configured with the test rig) (motion, multi-sensor, switches)
deconz II usb
zero scripts, automation, etc
HA went from hero to zero with the significant other. (Motion triggered lighting has become the new "normal")
When it comes to light controls 90% is 10% failure -- that's "apple maps bad."
Not sure what to try next.
Or reinstall the hue hub. Oh please no.
(Might try z2m on a separate device)
Intermittent unavailability (exactly 15 seconds) on a clean test rig.
To attempt to eliminate or recreate the problem took the following steps:
- formatted a brand new SDCard (to eliminate the possibility of bad I/O)
- used a different Pi (Pi 4 w/4Gb)
- added an extension cable to the deconz USB stick and moved it 6' away from the pi, power supplies, cables, etc.
- installed the ZHA and ran for 24 hours -- no dropouts. (A lot of other issues with groups and scenes, for me, with ZHA. I really wanted this to work... open-source python, no proprietary UIs...maybe someday, but then again, I'm not helping so shame on me)
- Removed the ZHA integrations
- Added deconz integration, configured and added devices through phoscon
- one dropout already occurred running overnight (way better than the 1 per hour I was seeing)
All Philip Hue bulbs and led strips (all types)
All Xiaomi sensors (none configured with the test rig) (motion, multi-sensor, switches)
deconz II usbzero scripts, automation, etc
HA went from hero to zero with the significant other. (Motion triggered lighting has become the new "normal")
When it comes to light controls 90% is 10% failure -- that's "apple maps bad."Not sure what to try next.
Or reinstall the hue hub. Oh please no.
(Might try z2m on a separate device)
Are you using Conbee II? Did you also update the firmware of the stick? I updated the stick via Windows since Dezons keeps failing the upgrade (it says succesul but then after a while it show update is available, common issue).
@ASNNetworks
Yes...Conbee II
No...I don't have a windows box running anyplace.
Firmware 264A0700
"Update to 26580700" (button showing, but doesn't upgrade)
@ASNNetworks
Yes...Conbee II
No...I don't have a windows box running anyplace.
Firmware 264A0700
"Update to 26580700" (button showing, but doesn't upgrade)
Up until now I haven’t had anymore disconnects (last 60 hours). I did upgrade the firmware though, which is the only difference between you and me (I also removed Deconz, used a new sd etc). I’d advise you to upgrade the Conbee II firmware. You can try manually with other platforms than Windows as well: https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually
I would try that before you do anything else. Chances are the firmware upgrade fixes it.
I do have exactly same issue, I updated formware manually using windows to 26580700 from 264A0700 but problem still remain, disconnection happends in all my zigbee devices very frequntly affecting sensors and lights
I do have exactly same issue, I updated formware manually using windows to 26580700 from 264A0700 but problem still remain, disconnection happends in all my zigbee devices very frequntly affecting sensors and lights
I also still have the same problem and i've also updated my conbeeII via windows
Heeellppp....
Same issue here. Rolling back to 5.3.2 fixed the issue. Everything else is up-to-date. Is 264A0700 the latest??
http://deconz.dresden-elektronik.de/deconz-firmware/?C=M;O=D
I'm having this exact same issue with Home Assistant (hass.io) running on a Pi 4 with DeConz as an addon.
Running multiple devices: Xiaomi Aqara (battery powered), Ikea tradfri bulb + sensor (battery powered)
Around 6/7 times a day, even at night the devices go unavailable for a time and then report back.
It's driving me insane, and i'm glad i'm not the only one.
I've already attached the Conbee 2 stick via USB extension cable + changed the zigbee channel.
The only thing i see in common with everyone reporting this is that they use a PI 3/4 . Is there anyone having this on anything else then a PI?
The only thing i see in common with everyone reporting this is that they use a PI 3/4 . Is there anyone having this on anything else then a PI?
I also had some thoughts in the same direction. I'm having this deconz disconnection problems for some time now running HA on a Pi3. The WiFi connection is not used, only Ethernet. But may be because of WiFi device is not completely deactivated, there are some interference problems?
Is someone running HA on Pi2 (without WiFi device) facing same problems?
There is a major update (6.0) with few fixes after that (6.1.0 latest). Perhaps that will fix issues others are still having. Worth trying.
Today I moved my Home Assistant from SD-card to SSD (not because of this problem, this was planned long time ago). I restored with my latest snapshot and to my surprise the issue seems gone! I don't understand why but maybe that can somehow help people with more knowledge to solve this issue.
Today I moved my Home Assistant from SD-card to SSD (not because of this problem, this was planned long time ago). I restored with my latest snapshot and to my surprise the issue seems gone! I don't understand why but maybe that can somehow help people with more knowledge to solve this issue.
Are you running hass os? What Guide did you follow and hardware are you running?
Yes I'm running HassOs on Raspberry 3B. I followed the official way to enable USB boot https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md
And then just write an image of the latest HassOs to your ssd, enable Samba and restore with snapshot.
Yes I'm running HassOs on Raspberry 3B. I followed the official way to enable USB boot https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md
And then just write an image of the latest HassOs to your ssd, enable Samba and restore with snapshot.
Did it update deconz to 6.1.0?
No, I'm still on 5.3.6.
Yes I'm running HassOs on Raspberry 3B. I followed the official way to enable USB boot https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md
And then just write an image of the latest HassOs to your ssd, enable Samba and restore with snapshot.
Im running a Pi4, would your instruction work?
Not yet, I'm afraid. Usb boot is still in beta for Pi4.
Also running on Pi4, I am updating to 6.1.1 I will let you know once upgrades
I was having about 12 unavailable pero hr average, since I updated 20 minutes ago has not failed, using 6.1.1 will keep checking and upadate results
it took 30 min.... still failing using 6.1.1 , how do you Roll back to 5.3.2? what was the date before it changed to look into my backups?
it took 30 min.... still failing using 6.1.1 , how do you Roll back to 5.3.2? what was the date before it changed to look into my backups?
I had to go to a snap from 21st May to get 5.3.2 back,
Thank you very much danemonkey, I look for my backups and selected one from May 13th that seems to be back to stable. using 5.3.2, no failures for over an hour
Thank you very much danemonkey, I look for my backups and selected one from May 13th that seems to be back to stable. using 5.3.2, no failures for over an hour
How do you downgrade to Deconz addon 5.3.2 ? I starter using Deconz wat after that.
Thank you very much danemonkey, I look for my backups and selected one from May 13th that seems to be back to stable. using 5.3.2, no failures for over an hour
How do you downgrade to Deconz addon 5.3.2 ? I starter using Deconz wat after that.
I restored a previous snapshot not sure how you would do it otherwise
I have been having this issue for quite some time as well.
However, I just migrated to ZHA in hope that this fixes the issue, but it even got worse. So I am unsure, whether this is related to deConz at all.
An update after rolling back to 5.3.2, rate of disconnect decreased from around 12 per hr to one every 5 hrs (I can leave with that)
I have been having this issue for quite some time as well.
However, I just migrated to ZHA in hope that this fixes the issue, but it even got worse. So I am unsure, whether this is related to deConz at all.
I migrated a few weeks ago to ZHA and it solved my issue.
Ok, so here it's my experience and I hope it could be useful. I was having this same issue, every 15 seconds all my devices were unavailable...on the logs i had this:
2020-07-07 10:30:25 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-07-07 10:30:25 DEBUG (MainThread) [pydeconz.websocket] Reconnecting to deCONZ in 15.
2020-07-07 10:30:40 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-07-07 10:31:06 DEBUG (MainThread) [pydeconz.websocket] Websocket running
2020-07-07 10:31:06 DEBUG (MainThread) [pydeconz.websocket] {"e":"changed","id":"2","r":"sensors","state":{"lastupdated":"2020-07-07T14:31:06.761","presence":true},"t":"event","uniqueid":"00:15:8d:00:02:52:aa:f2-01-0406"}
2020-07-07 10:31:08 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"lastannounced":null,"lastseen":"2020-07-07T14:31:08Z","manufacturername":"dresden elektronik","modelid":"RaspBee","name":"Configuration tool 1","swversion":"0x264a0700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:05:ac:17-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:05:ac:17-01"}
2020-07-07 10:31:12 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"lastannounced":null,"lastseen":"2020-07-07T14:31:12Z","manufacturername":"dresden elektronik","modelid":"RaspBee","name":"Configuration tool 1","swversion":"0x264a0700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:05:ac:17-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:05:ac:17-01"}
2020-07-07 10:31:35 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-07-07 10:31:35 DEBUG (MainThread) [pydeconz.websocket] Reconnecting to deCONZ in 15.
and on the deconz addon i was having over and over again this message:
Remove websocket 172.30.32.1:51086 after error Unknown error
New websocket 172.30.32.1:36186 (state: 3)
These lines for me are the main reason why for the intermittence because when the addon was working i never saw this behavior. After restarting a several times the addon stop working at all and i was unable to start it again, having the following errors on the supervisor log:
ERROR (MainThread) [supervisor.api.ingress] Ingress error: None
ERROR (MainThread) [supervisor.api.ingress] Ingress error: None
[supervisor.docker.interface] Can't grep logs from homeassistant/armhf-addon-deconz: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
So, after a few days been unable to solve the problem i decided to re install homeassistant from zero. I downloaded the hassio image and start installing everything again on my raspberry pi 3 and this solve all the problems. My devices were working again flawlessly for weeks. But today, I saw that there was an update for the addon so i installed it and all my problems started again...the intermittence was back and again i'm having some problems to start the addon.
I really don't want to reinstall all over again homeassitant but it seems thats is the only way to have the deconz addon working again so please I need your help to solve this for once.
I really don't want to reinstall all over again homeassitant but it seems thats is the only way to have the deconz addon working again so please I need your help to solve this for once.
As I have said in previous posts I migrated to ZHA and all of my issues were solved, there defienetely seems deconz is somehow broken.
There seems to be an issue with ingress or the addon so better to get frenck and pvizeli to investigate this.
@aguilaair thats not the solution to the issue
That's why it's still not closed 🙃
With version 6.1.2. I still have the same problem but only one disconnection in an hour, to be continued ....
Well guys, im having same problem here:
Runing:
Facing the same problem since several weeks. All Deconz devices go to "unavailable" state randomly in intervals from 5 to 30min.
Home Assistant: 0.113.3
deConz: 2.05.79
RaspBee firmware: 26350500
Supervisor version: 229
OS: HassOS 4.11
deCONZ add-on: 6.2.3
In the log I found a connection to a quite long database operation (>22s) and a removal of the websocket after an unknown error. This happens in coincidence with the change to unavailable state.
15:07:38:338 DB saved in 22087 ms
15:07:38:338 don't close database yet, keep open for 900 seconds
15:07:38:348 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
15:07:38:361 Remove websocket 172.30.32.1:44788 after error Unknown error
Maybe this gives someone an idea..
I switched to ZHA and everything is working perfect for 2 days now. I will keep updated if anything happens
@RenzoBeux That's not a solution to the problem, nor related to this problem.
@RenzoBeux thx for your feedback, wait and see. but i hope this problem is resolve with deconz and HA
i have the problem to i hope its fixed fast its broken for a month now pf :-1:
@frenck is it possible to have it fixed? many thanks on advance
Anyone who can do a network trace between hass and deconz to see what the last few messages are over web socket before it closes?
@mantaalex just reported this to me.
He had a ha database of 260MB. He switched to mariaDB and now it's working properly.
Can you test this @jybi89 ? See if its because of the database size?
If this is the case and does fix it, it might be related to either SD card having to much to do at that disconnects. Or another deeper issue unrelated to the integration.
I moved to MariaDB about an hour ago and in my case the problem persists.
Well there goes my theory
I took the nuclear option...with partial success. Now the other members of the household aren't asking for the entire system to be removed 3 times a day. I haven't had to throw HA out and moved to something else. Yet.
Results:
Reduced the "device unknown" dropouts from:
Google voice commands work about 95% of the time. A few "something went wrong" commands per day. This is the only thing keeping me getting voted out of my own house.
Added several automations back in...
SO... bottom line Is it fixed? No.
Still getting:
Next step - "double nuclear"
(I tried ZHA, with success, but they don't support the xiaomi switches/cubes yet)
Live by the generosity of folks who make open source for the devices I've made
Die by lack of ongoing support/momentum from the choices I've made
Let's keep it relevant
i enabled the mariadb did the config & recorder thing in configuration.yaml file
Did you restarted your Home assistant & deleted old db & log file ?
maybe its just luck but it works for me
posavasos commented 8 hours ago
I moved to MariaDB about an hour ago and in my case the problem persists.
For you who still have this issue ; try disabling custom components and other components, it could be an issue caused from them
@Kane610 I disabled all custom components and restarted the host RPi. Confirmed in logs that no custom components are loaded. This problem still occurs for me around every 5 minutes. All logs are the same as already posted, with a WebSocket disconnect/reconnect lasting ~15 seconds.
I believe the lag in HA when this occurs is the entities switching from available to unavailable to available again, but I don't have conclusive proof of that, I see a lot of activity in the logbook (taking from e.g. 13:35:15 -> 13:36:11 for them to go unavail ableand then all be updated to correct state again).
Current Set up: RPi4/HassOS 4.12/Supervisor 229/deCONZ Add On 6.2.3/Conbee II 2.05.79 (with FW 26580700)/MariaDB
While I appreciate the nature of open source, and thank everyone for their efforts, my house is getting quite tired of "nothing working". As with others, made significant investment in deCONZ configuration so hard to unravel.
Is there some other logging at a network level on why the WebSocket keeps dropping? Or something else can enable beyond debug logs on HA/deCONZ to see what might be happening?
Well now that you've removed everything else you could enable full debug logging for all of hass. That could potentially show something. Another thing to try would be to run the pydeconz library standalone and see if same thing happens to it when running it apart from hass. That could potentially improve possibilities of debugging
I moved to MariaDB about an hour ago and in my case the problem persists.
I moved to MariaDB on an external (raspbian) device to check if it has to do with the SD card together with the recorder component, but unfortunately I have still some disconnects...
Hi guys, I solved this problem on my own.
I solved mine disabling recorder and logbook.
After that, I've replaced my SD to a type A2 and don't have any problems.
(the problem was solved before replacing the SD)
Thanks @Kane610, I tried this, but I am not familiar enough to see any problems occur from the debug logging enabled:
2020-08-08 20:17:41 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
...
2020-08-08 20:17:43 DEBUG (MainThread) [pydeconz.websocket] Websocket running
...
... [ first web socket call ]
...
2020-08-08 20:17:43 DEBUG (MainThread) [pydeconz.websocket] {"e":"changed","id":"51","r":"sensors","state":{"lastupdated":"2020-08-08T19:17:43.659","power":131},"t":"event", <REDACTED>
...
... [ first web socket device ]
...
2020-08-08 20:17:45 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"lastannounced":"2020-07-19T00:08:52Z","lastseen":"2020-08-08T19:17:45Z", <REDACTED>
...
...[ regular pydeconz.websocket device log lines, at 1-3 second intervals ]
...
2020-08-08 20:28:12 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"lastannounced":null,"lastseen":"2020-08-08T19:28:12Z",, <REDACTED>
...
... [ last web socket device log line, 23 seconds later, ... no INFO+ logs between these times ]
...
2020-08-08 20:28:35 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2020-08-08 20:28:35 DEBUG (MainThread) [pydeconz.websocket] Reconnecting to deCONZ in 15.
The 2020-08-08 20:28:35 time is when HA finally realises all the entities are not there and makes them all "unavailable" and starts to get the state of them again. "lastannounced":null
also occurs regularly in log lines where it's working fine, so not sure that is a problem?
I cannot see how to post the full debug logs as I don't believe I will be able to sanitize them reliably.
EDIT 1: Uninstalling and reinstalling deconz add on has not worked for me, and the problem still persists.
EDIT 2: A fresh flash of SD card, then restoring from a back up has this working for me 2 hours so far without interruption (had to reinstall MariaDB, size?)
I'm having the same issue as you guys. Lots of unsuspected disconnections on my RPI4 with deconz. One thing I have noticed is that when I delete my database file "home-assistant_v2.db" of course deleting all the history data, the problem disappears for about 3 days. Next when the database gets enough data problem came back.
I think that there can be a problem with sd card or maybe it is correlated to database changes which they have done in the last release.
Did someone also notice this correlation?
two days ago i deleted my .db file as well. till now now errors.
and btw i can't believe everyone have corrupted sd cards all of a sudden.
the people who have tryed did they tryed all with mariadb on the local raspberry pi ?
i moved mine to an external server (in my case my webserver)
im willing to give someone an account to try out if that works to ? send me a message
https://paste.ubuntu.com/p/5ZFhwFdYjK/ this is how i did the recorder.yaml config
I'm having the same issue as you guys. Lots of unsuspected disconnections on my RPI4 with deconz. One thing I have noticed is that when I delete my database file "home-assistant_v2.db" of course deleting all the history data, the problem disappears for about 3 days. Next when the database gets enough data problem came back.
I think that there can be a problem with sd card or maybe it is correlated to database changes which they have done in the last release.
Did someone also notice this correlation?
Hi you want free of any charge try out on my external Directadmin Centos server?
I Create an account there and an mysql db and you can try it out if it works after a few days :) maybe we are closer to a solution?
just send me a message
I moved to MariaDB about an hour ago and in my case the problem persists.
I moved to MariaDB on an external (raspbian) device to check if it has to do with the SD card together with the recorder component, but unfortunately I have still some disconnects...
Hi you want free of any charge try out on my external Directadmin Centos server?
I Create an account there and an mysql db and you can try it out if it works after a few days :) maybe we are closer to a solution?
just send me a message
@oat1 are you using a high end sd-card on your rpi?
I'm using Samsung Evo plus 64 GB
Further to my description in https://github.com/home-assistant/core/issues/37372#issuecomment-671039397, I am also running on a Samsung Evo card. My MariaDB size was originally 2.5GB when having the issues. After reinstalling everything, the issue went away but my DB grew to 1GB+ in 3 days. I've now been very aggressive about what I am excluding in the recorder
(found had a media player which generated a states
row almost every second of the day). DB growth is now not so large, and no deconz problems in the last 5 days. I should note that I haven't changed my HA configuration in around 6 months before this (other than very minor tweaks like friendly_name, icons etc) other than regularly upgrading HA and deconz.
Some people reported that after the last update (114.), this was resolved. Can anyone confirm?
i'm running 0.114 on a brand new sd card and a new raspberry 3b (the old one smelled kinda burned). let's wait one or two days and see what happens. i really hope this is solved now.
Much much better! But it happened again. 2 times in the last 12 hours.
Both times for exactly 15 seconds.
Same issue here
Less freq, but still happening.
All the deconz connected lights and sensors. (deconz connected zigbee switches don't show as they are event-based.)
i'm having the same issues again (less frequent). so changing the pi and the sd card did not help.
i'm having the same issues again (less frequent). so changing the pi and the sd card did not help.
Did you tryed move the db out of the pi ? like i did
If you want to try out i add an account on my directadmin to testout send me mail alex AT opelmanta DOT BE
To me it sounds like there is something else in your systems that causes a time out or similae
just to test, I upgraded from deCONZ 5.3.2 where I do not see the failure that frecuently to 6.2.3 latest version and I immediatly start seeing the disconnections, so I went back to version 5.3.2 and it is back to stable, I will try using a faster flash A2 and see if that allows to have 6.2.3 with no failures
Is it possible to downgrade to a previous version of deCONZ (like for example 5.3.2) without a having a snapshot with that version? If so, I would love to try.
Is it possible to downgrade to a previous version of deCONZ (like for example 5.3.2) without a having a snapshot with that version? If so, I would love to try.
Same Question to me!
is it possible to create a backup of deCONZ 5.3.2 and use it in another build? if so I can provide the backup for 5.3.2
Hey guys. Did you get this problem resolved?
I was not updating all HA system from start of the summer. Did an update this week. Started having these short period of unavailable for so deconz devices 1-2 times per day for ~30 seconds
Conbee (first) reports firmware update, but after applying it does not increase firmware version and update notification still on.
Ha version 0.114.4
Deconz 6.2.3.
For what I saw that easiest solution is to restore deconz plugin from a June snapshot. That's how all of you got it resolved?
No, this problem still persists any it seems that there is no new approach where to search for a fix :-(
All proposed workarounds (change of sd card, turn off history/logging component, move database to other device, etc.) only mitigate those regular disconnects, the real cause of the problem is always still there.
Of course, downgrading deCONZ helps a lot, but disconnects still happen, although very rarely.
Meanwhile some other threads where started ( #1463 , #1497) all facing the same problem.
I'm wondering why not all users of deconz addon are facing this disconnection problems, otherwise someone would have fixed it yet.
Just a thought, is everyone with the issue using Ikea lights?
On Fri, 18 Sep 2020, 18:09 Markus Hornbach, notifications@github.com
wrote:
No, this problem still persists any it seems that there is no new approach
where to search for a fix :-(All proposed workarounds (change of sd card, turn off history/logging
component, move database to other device, etc.) only mitigate those regular
disconnects, the real cause of the problem is always still there.Of course, downgrading deCONZ helps a lot, but disconnects still happen,
although very rarely.
Meanwhile some other threads where started ( #1463
https://github.com/home-assistant/core/pull/1463 , #1497
https://github.com/home-assistant/core/issues/1497) all facing the same
problem.I'm wondering why not all users of deconz addon are facing this
disconnection problems, otherwise someone would have fixed it yet.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/core/issues/37372#issuecomment-694723894,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKT26GGJECABS247IQKVTXLSGMIR3ANCNFSM4OPEVJEQ
.
I have these deconz entities:
Everything is running on RPI3 (on external SSD) with conbee. Database just recreated, as after update HA didn't start. So renamed old ~1.1GB db home-assistant_v2.broken.db. Current DB is like 8MB
HA version before all those updates was Home Assistant 0.111.4 and it was lastly updated on 2020-06-30
Current deconz fw is 26330500 and cannot update
As mentioned before: when one xiaomi aqara sensor went out on 2020-09-15 I did all HA + HA OS + add-ons updates.
Didn't notice such issues previously.
I would really like to fix this before heating season starts, as I my heating is realated on HA.
So did anybody found any common denominators?
By the way 5 minutes history on that outage looks like so (only deconz entities went out):
Just a thought, is everyone with the issue using Ikea lights?
…
I would not assume that the disconnects are caused by certain devices (even if Ikea lights will be very popular). The trigger of the broken web connection to deconz has definitely to do with high cpu load or high memory/storage traffic on the device where running HA.
So from my point of view there is a timing problem (automatically closing connection after timeout occurs, it takes 15sec to reestablish it), but this will be hard to figure out without deeper knowledge of the addon.
Just a thought, is everyone with the issue using Ikea lights?
…I would not assume that the disconnects are caused by certain devices (even if Ikea lights will be very popular). The trigger of the broken web connection to deconz has definitely to do with high cpu load or high memory/storage traffic on the device where running HA.
So from my point of view there is a timing problem (automatically closing connection after timeout occurs, it takes 15sec to reestablish it), but this will be hard to figure out without deeper knowledge of the addon.
The problem can be with Raspberry 3 and 4. First I thought that it can be correlated with SDs, but Vukisz has SSD so it cannot be a problem with sd cards. Does anyone have this issue on other devices than raspberry ?
I'm so frustrated that this problem has been for a long time and devs don't see or care
@oat1 I really would like to ask you to pay some respect. Please, fix it yourself or be more constructive. @Kane610 has been trying to reproduce it, but he couldn't.
I think from a discussion on the forum (or another GitHub issue) a user commented on a lot of reconnection issues with a specific database that due to it hanging starves out timeouts in different integrations just like deconz where a timer will hit and it will try to reconnect. I'm still fairly certain there is something other than deconz/deconz integration that is the cause of this.
And this is where the responsibility falls on affected users stepping up to try to pin point possible causes
I'm still fairly certain there is something other than deconz/deconz integration that is the cause of this.
@Kane610 : but how would you explain that nearly all of the affected user notice a tremendous difference when downgrading deconz addon e.g. to 5.3.2, compared to all later versions?
It is not gone doing this, but disconnect frequency changes from several times a day to ones in a few days...
Of course some users reported, when they disable all history, logging,etc, staff (everything that has to do with database access) problem seems to be gone, but this cannot be the solution, do you agree?
@MarkusHornbach The only thing i see is that there is more users not having this. I have never experienced it myself for example.
@MarkusHornbach I have no idea, maybe lower system requirements due to different software versions in the add ons? I'm just speculating here.
Just a wild guess here after adding removing deconz integration while refactoring entity ids.
I noticed, that after freshly adding this integration sensor.daylight sensor got's disabled. I have a feeling, that all problems first started when I enabled this sensor in deconz integration. Is this sensor disabled for others?
P.S. Also updated FW to 26370500
Just a wild guess here after adding removing deconz integration while refactoring entity ids.
I noticed, that after freshly adding this integration sensor.daylight sensor got's disabled. I have a feeling, that all problems first started when I enabled this sensor in deconz integration. Is this sensor disabled for others?
P.S. Also updated FW to 26370500
It's good that you're starting to evaluate what could be the root cause but that is not it.
Just had time to swap my SD card from a 128 SAMSUNG EVO Select XC I to a 128GB SamDisk Extreme A2
After I loaded my previus back up, I updated DeConz to 6.2.3 from previus 5.3.2 it is being 40 minutes with no disconnects, I know still too early. I will update later to inform if this continues estable. by the way, also noticed History and logbook being way more faster than using the previus SD card (not related)
In case this is of any help for debugging, I had this issue before upgrading from:
To:
I know there are many parts that differ, but maybe it is of some help.
After 24 hrs. No Disconnections. so the SD card memory speed it is a factor, but as well something changed after DeConz 5.3.2 that make sthe problem more visible. now seems stable
I only see the issue like 2-3 times a day now. I had it around 12pm yesterday and then nothing until it appeared again around 4am.
I have this issue about once in an hour. Running a RbPi4 (4gb), HA core 0.115.1, supervisor 245, HassOS 4.13, Deconz 6.2.3, ConBee II version: 2.05.79, firmware: 26580700. I think it also started after upgrading to latest Deconz add-on version and updating the firmware etc. I vaguely remember having this way back, but not sure what fixed it in the meanwhile. I did recently also move my lights to Deconz light groups as I was having issues having the light groups defined on HA side. Otherwise my setup is quite light so there's not too much CPU or RAM in use normally. I do have a 1 year old SD in, but otherwise I have not noticed any issues with this setup. Of course if somebody can confirm having better hardware would help with this, I could probably consider getting a NUC and SSD etc. Think the performance on the Pi should be enough though so maybe also the USB boot capability will become available soon for HA.
Weirdly enough I am also seeing some of my media_player entities going unavailable in a similar fashion, typically quite close to the same happening for Deconz entities. Might be related or not.
an update, after changing to a faster SDCARD it is being now 48 hrs and not a single disconnection using the latest hassio and DeConz releases
an update, after changing to a faster SDCARD it is being now 48 hrs and not a single disconnection using the latest hassio and DeConz releases
Interesting. Could do that upgrade as I'm still running the original SD card that came with the Pi. Which one did you pick? Probably move to SSD at some point when it gets natively supported with the Pi.
128GB SamDisk Extreme A2
https://www.amazon.com.mx/dp/B07FCMKK5X?ref=ppx_pop_mob_ap_share
Well week was quite good. Maybe one unavailable episode. And now it started: deconz went down and if I start it again it goes down imediatly :-(
HA restart also didn't help. Only removing conbee from rpi3 and inserting again worked :-(
Logs attached
logOnFirstCrash.txt
logOnFCrashAfterStartingDeconzAddon.txt
@vukisz that is not really the same thing, this is about websocket going down and reconnecting
I was running hassOS on a Raspberry Pi 4 with SD card and a conbee 2 stick connected to a USB extension cable and this issue starting popping up a few months ago. Since i had some other weird issues in Home Assistant i did a clean install on a new SD card. Few weeks later the issue was back....
I just switched to a SSD connected to my Pi4 running HassOS and i'm not having this issue anymore *knock on wood
If you are running your instance on a SD card get a SSD and follow the guide below, trust me it will make HA more stable and faster.
How to make your Raspberry Pi4 able to boot from SSD:
https://community.home-assistant.io/t/hassio-on-pi4-with-official-ssd-released-bios-support/205935/31?fbclid=IwAR3BW3OmuKwzUUifE37xhUbAgc42ZnTfp9p1ZJn1mVdxohgrH3o3YgKdXTQ
Known working USB adapters (I've got the startech one)
https://tynick.com/blog/05-22-2020/raspberry-pi-4-boot-from-usb/?fbclid=IwAR3hwXM5vFfiNtWjsXWJZKxZvyt142bDlF4U84MVDXDpJgVXKrXlEIXELrs
How to install raspbian headless and enable SSH:
https://www.youtube.com/watch?v=dhY8m_Eg5iU&t=266s&fbclid=IwAR2djRp6y4nb6D7SNDdrKMkMJsSSJ4Yk7bT6y9tdmOLoTRsTbPra_k1wBK0
Just sharing my experience!
I was running hassOS on a Raspberry Pi 4 with SD card and a conbee 2 stick connected to a USB extension cable and this issue starting popping up a few months ago. Since i had some other weird issues in Home Assistant i did a clean install on a new SD card. Few weeks later the issue was back....
I just switched to a SSD connected to my Pi4 running HassOS and i'm not having this issue anymore *knock on wood
If you are running your instance on a SD card get a SSD and follow the guide below, trust me it will make HA more stable and faster.
How to make your Raspberry Pi4 able to boot from SSD:
https://community.home-assistant.io/t/hassio-on-pi4-with-official-ssd-released-bios-support/205935/31?fbclid=IwAR3BW3OmuKwzUUifE37xhUbAgc42ZnTfp9p1ZJn1mVdxohgrH3o3YgKdXTQKnown working USB adapters (I've got the startech one)
https://tynick.com/blog/05-22-2020/raspberry-pi-4-boot-from-usb/?fbclid=IwAR3hwXM5vFfiNtWjsXWJZKxZvyt142bDlF4U84MVDXDpJgVXKrXlEIXELrsHow to install raspbian headless and enable SSH:
https://www.youtube.com/watch?v=dhY8m_Eg5iU&t=266s&fbclid=IwAR2djRp6y4nb6D7SNDdrKMkMJsSSJ4Yk7bT6y9tdmOLoTRsTbPra_k1wBK0Just sharing my experience!
Great idea. Amazing that it's now possible to get completely rid of the sd card with the pi4. I just went ahead and ordered an SSD and a SATA USB adapter and just in case a small nice SD card to do the process with. Will try to remember to update here if it helps with the original issue.
I was running hassOS on a Raspberry Pi 4 with SD card and a conbee 2 stick connected to a USB extension cable and this issue starting popping up a few months ago. Since i had some other weird issues in Home Assistant i did a clean install on a new SD card. Few weeks later the issue was back....
I just switched to a SSD connected to my Pi4 running HassOS and i'm not having this issue anymore *knock on wood
If you are running your instance on a SD card get a SSD and follow the guide below, trust me it will make HA more stable and faster.
How to make your Raspberry Pi4 able to boot from SSD:
https://community.home-assistant.io/t/hassio-on-pi4-with-official-ssd-released-bios-support/205935/31?fbclid=IwAR3BW3OmuKwzUUifE37xhUbAgc42ZnTfp9p1ZJn1mVdxohgrH3o3YgKdXTQ
Known working USB adapters (I've got the startech one)
https://tynick.com/blog/05-22-2020/raspberry-pi-4-boot-from-usb/?fbclid=IwAR3hwXM5vFfiNtWjsXWJZKxZvyt142bDlF4U84MVDXDpJgVXKrXlEIXELrs
How to install raspbian headless and enable SSH:
https://www.youtube.com/watch?v=dhY8m_Eg5iU&t=266s&fbclid=IwAR2djRp6y4nb6D7SNDdrKMkMJsSSJ4Yk7bT6y9tdmOLoTRsTbPra_k1wBK0
Just sharing my experience!Great idea. Amazing that it's now possible to get completely rid of the sd card with the pi4. I just went ahead and ordered an SSD and a SATA USB adapter and just in case a small nice SD card to do the process with. Will try to remember to update here if it helps with the original issue.
It's been about 24 hours after setting up my Home Assistant instance on an SSD by restoring the backup that I made with the SD card and I haven't yet seen any unavailability issues. Performance seems quite a bit better when it comes to lights always quickly responding to remotes etc. All good so far.
Well I have raspberry pi 3 with SSD via USB.
And I still have issues. Not every day, but a couple times per week. Attaching temperature sensor log of one week period
At least deconz didn't stop for a past week or so. Knocking the wood..
I also switched to SSD. The situation improves a lot, but the problem is not completely solved. I have a disconnection about every 24 hours.
Sadly the same problem here. Not sure when it started to happen, but it's quite annoying.
Could i noticed pattern? Sunday midday always have short unavailable episode
Same here: RPi 4 Hass.IO ... long time it was stable but since one week Deconz is shown as unavailable. In the Deconz App i see all my switches and Sensors :(
I am also experiencing all zigbee devices becoming unavailable 5+ times an hour when HA loses websocket connection to deconz which itself appears to be stable.
My logs follow the same pattern as @aguilaair.
Which additional logs would be helpful to capture?
Pi4 4GB, Samsung Pro Endurance 32GB
8x Ecosmart-ZBT-A19-CCT-Bulb (2.3)
Same problems for me. Really really annoying since allt the automations are disconnected as well when the deconz disconnections occurs. Any news about a fix? (Running HassOs on RPI 3B+ / 0.117.6 and lastest deconz app
All my devices (Xiaomi and Osram) are also unavailable several times per hour.
My system is on the following versions:
Deconz 2.05.84
Conbee 26390500
HassOS 4.15
Core 0.117.1
Supervisor 2020.11.0
Same problems for me. Really really annoying since allt the automations are disconnected as well when the deconz disconnections occurs. Any news about a fix? (Running HassOs on RPI 3B+ / 0.117.6 and lastest deconz app
There is no focus on this issue. This needs someone who has the issue to figure out /narrow down what is causing it
I also had this exact same issue on my RPi4+Raspbee II and the release version of HA.
Usually the devices became unavailable multiple times a day and it was REALLY annoying when it happened the moment you were using a dimmer switch to control lights.
The RPi4 was running on a 64GB SD-card which was very laggy when loading logs/etc.
So I tried installing HA 64bit 5.3 developer version on an SSD using ASM235CM based USB3 SSD-case (by Ugreen). The case has a 0,5m long cable and the case is placed as far from the RPi4 as possible.
Things that I have noticed from this venture:
Cons:
Pros:
@Tiihokatti Interesting. I am running RPI3B+ on an SD card extreme and it should be enough. I started to get some problems with my zigbee sensors/switches when I updated Hassio from 0.116 to 0.117 and with latest Deconz. I will try to reinstall a former version of both and see if the problems disappear...
I know it was mentioned several times in this thread (and in all the other ones handling with this topic), but for everyone who do not want to read all:
SD card "extreme" is not enough in this case, consider buying one with the "A2" classification (better App performance). After I changed my SD card to a A2 (several weeks ago), all disconnects disappeared. Before that change I had several disconnects a day.
@MarkusHornbach Any mode you could recommend? I have read some articles that claims that there is not better performance between A1 and A2...
I talked to the deconz folks in their discord: they simply blamed HA and dismissed the issue.
I then decided to try switching to ZHA, the clouds parted, and everything is working perfectly without the need to manage devices through a separate portal (phoscon).
FWIW: There were no USB devices in use of any type on my setup.
I think the suggestions to use a different SSD/SD card are red herrings and point to some sort of race condition in the HA add-on or integration code.
As has been posted before that is not the solution to this problem @acortelyou, stay on topic.
@acortelyou as far as I am concerned, this issue hasn't been discussed for ages in the discord or I might have missed out big time. Stating we dismissed it is simply not true. We are helping out whenever we can.
@Kane610 is trying to figure out how to get this fixed and the people on deCONZ are helping him whenever we can help him.
Actually I'm not doing anything on this, people affected by it need to identify what is starving out processes in their systems. There is nothing I can do about a dropped websocket, the reconnection works as is shown.
@MarkusHornbach I have uppdated my sd card to A2 and installed the 64bit version of Hassio. 2 days without problem with Deconz becoming unavailable... Thanks for the advice!
Most helpful comment
i have the problem to i hope its fixed fast its broken for a month now pf :-1:
@frenck is it possible to have it fixed? many thanks on advance