I have been using Envisalink with HA and I have noticed that it loses connectivity to the sensors every week or so. The DSC panel still responds to key press commands send from HA but doesn’t show change of sensor when doors are tripped or when panel changes state from Ready. I usually restart HA which often the Envisalink connection is refused and disconnected. I usually have to log into the Envisalink webpage and reboot Envisalink and then restart HA.
I am thinking of creating a watchdog automation in HA to monitor this and try to restart HA / Envisalink when it happen. Before I do this, I was wondering if anyone else experience this or have a solution?
I am using Envisalink 4 with DSC 1616 panel since about year. I have not seen such issue. Most of the time I keep update HA to latest version.
FYI: I have static IP assigned to Envisalink
Although I have noticed two things:
Envisalink doesn’t allow more than one client connected at the same time. So if I use raspberry pi to test few things it will not allow to connect raspberry pi HA while my production version of HA on Ubuntu is already connected.
My production version of HA keeps logging status change events for doors so much and fills up the database. I think someone already logged the issue for this. Below is the link to that issue: https://github.com/home-assistant/home-assistant/issues/7098
Thanks for your help, I don’t think my issue is related to 1 or 2 although I experience both. I read somewhere that they are going to change the database so same state or no state change entries will not be entered to reduce database size.
I do this right now to reduce database size although it doesn’t reduce same state entries.
DELETE FROM events WHERE event_type = ‘service_executed’;
DELETE FROM events WHERE event_type = ‘call_service’;
DELETE FROM events WHERE event_type = ‘component_loaded’;
I just experienced the loss of the envisalink component again, it last happened about a week ago. I set my log to info and got this, you can see when it stopped.
2017-06-12 17:07:47 INFO (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2017-06-12 17:07:58 INFO (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2017-06-12 17:08:13 INFO (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2017-06-12 17:08:20 INFO (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2017-06-12 17:08:28 INFO (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2017-06-12 17:08:38 INFO (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2017-06-12 17:08:39 INFO (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2017-06-12 17:08:44 INFO (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2017-06-12 19:31:37 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-06-12 19:32:40 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
and when I restart, i get this. I will have reboot envisalink from webpage to establish a connection again.
2017-06-12 19:37:13 INFO (MainThread) [homeassistant.components.envisalink] Start envisalink.
2017-06-12 19:37:13 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/tasks.py", line 241, in _step
result = coro.throw(exc)
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/base_events.py", line 695, in create_connection
raise exceptions[0]
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/base_events.py", line 682, in create_connection
yield from self.sock_connect(sock, address)
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/futures.py", line 361, in __iter__
yield self # This tells Task to wait for completion.
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/tasks.py", line 296, in _wakeup
future.result()
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/futures.py", line 274, in result
raise self._exception
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/selector_events.py", line 439, in _sock_connect_cb
raise OSError(err, 'Connect call failed %s' % (address,))
ConnectionResetError: [Errno 54] Connect call failed ('192.168.2.19', 4025)
Hey all. I believe I’m running into this same bug. New install of HA 0.46.1 on RP3/Hassbian (just got started with HA about two weeks ago). I noticed today after about 5-6 days of run time, HA seemed to crash. What clued me in was my Envisalink SMS alert let me know that the TPI session closed, then I noticed the web UI wasn’t live and my SSH session to the RPI had timed out.
From /var/log/syslog
Jun 22 16:03:46 hassbian hass[717]: Traceback (most recent call last):
Jun 22 16:03:46 hassbian hass[717]: File “/usr/lib/python3.4/asyncio/tasks.py”, line 233, in _step
Jun 22 16:03:46 hassbian hass[717]: result = coro.throw(exc)
Jun 22 16:03:46 hassbian hass[717]: File “/usr/lib/python3.4/asyncio/base_events.py”, line 570, in create_connection
Jun 22 16:03:46 hassbian hass[717]: raise exceptions[0]
Jun 22 16:03:46 hassbian hass[717]: File “/usr/lib/python3.4/asyncio/base_events.py”, line 557, in create_connection
Jun 22 16:03:46 hassbian hass[717]: yield from self.sock_connect(sock, address)
Jun 22 16:03:46 hassbian hass[717]: File “/usr/lib/python3.4/asyncio/futures.py”, line 388, in iter
Jun 22 16:03:46 hassbian hass[717]: yield self # This tells Task to wait for completion.
Jun 22 16:03:46 hassbian hass[717]: File “/usr/lib/python3.4/asyncio/tasks.py”, line 286, in _wakeup
Jun 22 16:03:46 hassbian hass[717]: value = future.result()
Jun 22 16:03:46 hassbian hass[717]: File “/usr/lib/python3.4/asyncio/futures.py”, line 277, in result
Jun 22 16:03:46 hassbian hass[717]: raise self._exception
Jun 22 16:03:46 hassbian hass[717]: File “/usr/lib/python3.4/asyncio/selector_events.py”, line 382, in _sock_connect_cb
Jun 22 16:03:46 hassbian hass[717]: raise OSError(err, ‘Connect call failed %s’ % (address,))
Jun 22 16:03:46 hassbian hass[717]: ConnectionResetError: [Errno 104] Connect call failed (‘10.1.1.251’, 4025)#033[0m
I think that might be a different issue, in mine, the TCI connection is not lost, just HA doesn’t update any DSC zone when tripped. It is when I restart HA that I get the error above which cause me to have to reset envisalink from the webpage.
Certainly a possibility. I may be having hardware or cabling issues, I’ve noticed network drops and port errors in my switch for the port the RPi is connected to, so I’ve also been troubleshooting that. I’d rather not move to wifi. Long term I think we need a way to automate service health in general, restarting/rebooting when certain conditions exist, like HA not being available, etc