Core: 0.98.3 Envisalink will not initialize

[prndlrm]

Home Assistant release with the issue:
0.98.3

Last working Home Assistant release (if known):
0.97.2 (did not try any versions of 0.98.x below 0.98.3)

Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io

Component/platform:
envisalink

Description of problem:
Envisalink component will not start up with this release. Get the following in the log for every restart. No envisalink config changes have been made.

2019-09-04 18:08:30 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink
2019-09-04 18:08:30 ERROR (MainThread) [homeassistant.setup] Setup failed for envisalink: Integration failed to initialize.
2019-09-04 18:08:30 ERROR (MainThread) [pyenvisalink.envisalink_base_client] The server closed the connection. Reconnecting...

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

envisalink:
  host: [ip]
  panel_type: DSC
  user_name: [user]
  password: [password]
  code: '[code]'
  port: '[port]'
  evl_version: 3
  keepalive_interval: 60
  zonedump_interval: 86400
  panic_type: Police
  zones:
    1:
      name: 'Driveway Gate'
      type: 'opening'
    2:
      name: 'Doorbell Button'
      type: 'none'
    3:
      name: 'Arming Button'
      type: 'none'
    4:
      name: 'Driveway Beam'
      type: 'motion'
    5:
      name: 'Laundry Water Sensor'
      type: 'moisture'
    6:
      name: 'Furnace Water Sensor'
      type: 'moisture'
    10:
      name: 'Back Door'
      type: 'opening'
    11:
      name: 'Front Door'
      type: 'opening'
    28:
      name: 'Glass Break'
      type: 'none'
  partitions:
    1:
      name: 'Home Alarm'

Traceback (if applicable):

Additional information:

[rhatguy]

I'm running 0.98.3 with HA connected to an envisalink proxy (dscserver) and a DSC alarm panel and do not have this issue. Everything is working as expected.

[prndlrm]

Rolled back to 0.97.2 and envisalink working fine. Updated to 0.98.4 and it won't initialize. Here are some debug logs, it shows that the system eventually connects to the EVL3 and gets information. By this time it is "Entity not available" and get no info in the front end.

2019-09-06 14:02:45 INFO (MainThread) [homeassistant.components.envisalink] Start envisalink.
2019-09-06 14:03:04 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink
2019-09-06 14:03:04 ERROR (MainThread) [homeassistant.setup] Setup failed for envisalink: Integration failed to initialize.
2019-09-06 14:03:05 ERROR (MainThread) [pyenvisalink.envisalink_base_client] The server closed the connection. Reconnecting...
2019-09-06 14:03:39 INFO (MainThread) [homeassistant.components.envisalink] Established a connection with the Envisalink
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:40 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] Envisalink sent a zone update event. Updating zones...
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:41 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:42 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:42 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:42 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:42 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:42 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:42 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2019-09-06 14:03:42 DEBUG (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event

[enelson493]

I'm experiencing the same as @prndlrm. Upgraded to 0.98.4 and envisalink stopped working. I've not touched envisalink config in months and I use the HA / envisalink integration daily, so I know worked fine prior to upgrade to 0.98.4.

Home Assistant release with the issue:
0.98.4

Last working Home Assistant release (if known):
0.97.X (sorry, don't know exactly which 0.97 version it was, but 0.97 for sure.)

Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io, running on RPI 3

Component/platform:
envisalink / I'm connecting to Ademco Vista 20P

Description of problem:
Envisalink component will not start up with this release. Get the following in the log for every restart. No envisalink config changes have been made.

2019-09-08 18:50:45 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-09-08 18:50:46 WARNING (MainThread) [homeassistant.components.http] Configuring api_password via the http integration has been deprecated. Use the legacy api password auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#legacy-api-password
2019-09-08 18:50:46 WARNING (MainThread) [homeassistant.components.http.auth] legacy_api_password support has been enabled.
2019-09-08 18:51:04 WARNING (MainThread) [homeassistant.setup] Setup of alexa_media is taking over 10 seconds.
2019-09-08 18:51:15 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink
2019-09-08 18:51:15 WARNING (MainThread) [homeassistant.setup] Setup of group is taking over 10 seconds.
2019-09-08 18:51:18 ERROR (MainThread) [homeassistant.setup] Setup failed for envisalink: Integration failed to initialize.
2019-09-08 18:51:18 WARNING (MainThread) [homeassistant.setup] Setup of tuya is taking over 10 seconds.
2019-09-08 18:51:19 ERROR (MainThread) [pyenvisalink.envisalink_base_client] The server closed the connection. Reconnecting...
2019-09-08 18:51:53 WARNING (MainThread) [homeassistant.components.media_player] Updating alexa_media media_player took longer than the scheduled update interval 0:00:10
2019-09-08 19:00:35 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.0707814884f3eb610724 is taking over 10 seconds

[ironslow]

I'm also experiencing the same issue here. The weird thing is that this is a brand new hassio system that I build last week. So I was already at 0.98.x from the start. The Envisalink integration was working fine until tonight. After a restart I got the same error :

2019-09-17 20:37:31 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink
2019-09-17 20:37:33 ERROR (MainThread) [homeassistant.setup] Setup failed for envisalink: Integration failed to initialize.

[Count0Int]

Same issue, maybe. Just trying to find an associated log entry, but after updating to 99.2 envisalink won't start.

Log entries:

2019-09-20 08:52:42 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink
2019-09-20 08:52:42 WARNING (MainThread) [homeassistant.components.weather] Setup of platform darksky is taking over 10 seconds.
2019-09-20 08:52:47 ERROR (MainThread) [homeassistant.setup] Setup failed for envisalink: Integration failed to initialize.
2019-09-20 08:52:47 ERROR (MainThread) [homeassistant.setup] Setup failed for plex: Integration failed to initialize.
2019-09-20 08:52:47 ERROR (MainThread) [pyenvisalink.envisalink_base_client] The server closed the connection. Reconnecting...

[satssehgal]

im having the same issue. The new Hassio doesnt load envisalink. Is there a fix in the works for this?

[ngardiner]

I also have this issue. It seems intermittent for me - always triggered by a homeassistant restart, goes away after a subsequent restart (but not immediately - in a future restart).

[smish66]

I am having the same issue. It started in 0.97.2, went back to 0.97.1 and worked fine. Just tried going to 0.99.3 and same issue. No changes to the envisalink config have been done ever since initial install.

Log entry:
2019-09-27 18:22:34 ERROR (Thread-3) [homeassistant.components.mqtt] Unable to connect to the MQTT broker: Connection Refused: not authorised.
2019-09-27 18:22:34 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink
2019-09-27 18:22:40 ERROR (MainThread) [homeassistant.setup] Setup failed for envisalink: Integration failed to initialize.
2019-09-27 18:22:41 ERROR (MainThread) [pyenvisalink.envisalink_base_client] The server closed the connection. Reconnecting...

[Cinntax]

Hey everyone, the envisalink component does support a timeout parameter, measured in seconds.
The default is 10 seconds. Looking at logs here, it does seem like a lot of your initialization is taking quite some time, and it's feasible we're hitting this.
What happens if you add timeout: 100 to your envisalink config?

[smish66]

I have not tried 100 but mine has been set to 30 since inception and now having this issue.

[Count0Int]

I just added the timeout setting to 100 and it works now. Any issue leaving it this high, or should I try some testing to see how low I can get that number and keep the connection reliable?

Thank you VERY much for the suggestion/fix!

[satssehgal]

Setting it to 100 did not work for me
On Sep 28, 2019, 11:20 PM -0400, Count0Int [e-mail], wrote:

I just added the timeout setting to 100 and it works now. Any issue leaving it this high, or should I try some testing to see how low I can get that number and keep the connection reliable?
Thank you VERY much for the suggestion/fix!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[prndlrm]

100 did not work for me either

[Cinntax]

I have a pull request coming up very shortly here- just running testing now. While I can't promise there will never be any connection failures, I am going to make it such that the component initialization will keep trying until a successful connection is made. I'm already reconnecting/recovering if we lose a connection after initialization... so once this is in i'm hoping we'll be able to recover from all connection scenarios.

[Cinntax]

@Count0Int - you can leave it that high and it won't hurt anything- but hopefully you shouldn't need it after this PR goes through.

[satssehgal]

Thank you for your hard work
On Sep 29, 2019, 7:11 PM -0400, Dan Cinnamon [e-mail], wrote:

@Count0Int - you can leave it that high and it won't hurt anything- but hopefully you shouldn't need it after this PR goes through.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[smish66]

Hi, just an update. I tried again going to 0.99.3, setting the timeout to 100 and rebooting the EVL during Hassio reboot, still having the connection failure. Also I get a Notification on the front-end saying there is a configuration error with integration envisalink. Just to note this notification error was also showing up before I changed the timeout value. Not sure if others are getting the same notification along with the connection failures .

[quackpack]

+1 on the same issue as @smish66 above with 0.99.3

[Count0Int]

Was this bugfix rolled into 0.100.1, or will it be in a future one? Just updated to .100.1 and still have issue. Cheers!

[smish66]

To confirm with Count0Int I also just did an update to 0.100.1 and have the connection failure issue still as well. It does not appear to be resolved.

[jcalderon71]

Same error with hassio 1.100.2 on ubuntu

2019-10-14 18:10:26 WARNING (MainThread) [homeassistant.setup] Setup of input_datetime is taking over 10 seconds.
2019-10-14 18:10:27 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink
2019-10-14 18:10:30 ERROR (MainThread) [homeassistant.setup] Setup failed for envisalink: Integration failed to initialize.
2019-10-14 18:10:31 ERROR (MainThread) [pyenvisalink.envisalink_base_client] The server closed the connection. Reconnecting...

[masimmons]

+1 - just installed homeassistant on Linux Mint 1.100.2 getting the same errors as jcalderon71 above

[Cinntax]

Right- i just checked the codebase- it doesn't look to me like my change made it to production. It's supposed to continue on with the initialization, even though the initial connection fails. It will continue to retry and when it does acquire a connection, it'll work.

[Cinntax]

@balloob - it looks like perhaps this is being released with .101- is that right?

[jcalderon71]

ok @Cinntax I will check later if its fixed, thanks

[ngardiner]

It's listed as included in 0.101 released a few hours ago

• Envisalink startup reconnect (@Cinntax - #27063) (envisalink docs)

[satssehgal]

When exactly is this getting released?

Sent from my iPad

On Oct 30, 2019, at 9:26 PM, Nathan Gardiner [e-mail] wrote:


It's listed as included in 0.101 released a few hours ago

Envisalink startup reconnect (@Cinntax - #27063) (envisalink docs)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ngardiner]

It was released earlier today, I am already running it for my environment and so far everything is stable, but my previous envisalink connectivity issues were purely intermittent and not deterministic, so I can't say it is fixed until I've run it for some time without failure.

[Cinntax]

Glad to hear things appear positive. I did want to call out that this fix won’t stop the connection failures- but it will, in all circumstances, retry and will maintain the connection.

[ngardiner]

That should be all that is required in my experience, @Cinntax. Thanks for the update. The behaviour I was seeing previously was that the envisalink would allow only 1 client at a time, so sometimes a restart of HASS would result in that connection failing. In the early days, that would hang HASS completely but recently it would just fail and continue without the component initializing. This seems to be the last piece of the puzzle (to trigger a reconnect event afterwards).

[satssehgal]

Was there something up with the update?

Get this

19-10-31 09:55:47 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.101.0
19-10-31 09:55:47 INFO (SyncWorker_14) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.100.3 to homeassistant/raspberrypi3-homeassistant:0.101.0
19-10-31 09:55:47 INFO (SyncWorker_14) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.101.0.
19-10-31 09:57:33 ERROR (SyncWorker_14) [hassio.docker.interface] Can't install homeassistant/raspberrypi3-homeassistant:0.101.0 -> 404 Client Error: Not Found ("no such image: homeassistant/raspberrypi3-homeassistant:0.101.0: No such image: homeassistant/raspberrypi3-homeassistant:0.101.0").
19-10-31 09:57:33 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
19-10-31 09:57:33 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: .wrap_api() done, defined at /usr/src/hassio/hassio/utils/__init__.py:20> exception=HomeAssistantUpdateError()>
Traceback (most recent call last):
File "/usr/src/hassio/hassio/utils/__init__.py", line 29, in wrap_api
return await method(api, args, *kwargs)
File "/usr/src/hassio/hassio/homeassistant.py", line 337, in update
raise HomeAssistantUpdateError()
hassio.exceptions.HomeAssistantUpdateError

Sent from my iPad

On Oct 31, 2019, at 4:39 AM, Nathan Gardiner [e-mail] wrote:


I have noticed after restarting HASS during testing, I am now getting the following constantly in the logs:
2019-10-31 19:27:34 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink- retrying...
2019-10-31 19:28:04 INFO (MainThread) [pyenvisalink.envisalink_base_client] Started to connect to Envisalink... at 192.168.28.19:4025
2019-10-31 19:28:07 ERROR (MainThread) [pyenvisalink.envisalink_base_client] Unable to connect to envisalink. Reconnecting...
2019-10-31 19:28:07 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink- retrying...
2019-10-31 19:28:37 INFO (MainThread) [pyenvisalink.envisalink_base_client] Started to connect to Envisalink... at 192.168.28.19:4025
2019-10-31 19:28:40 ERROR (MainThread) [pyenvisalink.envisalink_base_client] Unable to connect to envisalink. Reconnecting...
2019-10-31 19:28:40 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink- retrying...
2019-10-31 19:29:10 INFO (MainThread) [pyenvisalink.envisalink_base_client] Started to connect to Envisalink... at 192.168.28.19:4025
2019-10-31 19:29:13 ERROR (MainThread) [pyenvisalink.envisalink_base_client] Unable to connect to envisalink. Reconnecting...
2019-10-31 19:29:13 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink- retrying...
2019-10-31 19:29:43 INFO (MainThread) [pyenvisalink.envisalink_base_client] Started to connect to Envisalink... at 192.168.28.19:4025
2019-10-31 19:29:46 ERROR (MainThread) [pyenvisalink.envisalink_base_client] Unable to connect to envisalink. Reconnecting...
2019-10-31 19:29:46 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink- retrying...
2019-10-31 19:30:16 INFO (MainThread) [pyenvisalink.envisalink_base_client] Started to connect to Envisalink... at 192.168.28.19:4025
2019-10-31 19:30:19 ERROR (MainThread) [pyenvisalink.envisalink_base_client] Unable to connect to envisalink. Reconnecting...
2019-10-31 19:30:19 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink- retrying...
2019-10-31 19:30:49 INFO (MainThread) [pyenvisalink.envisalink_base_client] Started to connect to Envisalink... at 192.168.28.19:4025
2019-10-31 19:30:52 ERROR (MainThread) [pyenvisalink.envisalink_base_client] Unable to connect to envisalink. Reconnecting...
2019-10-31 19:30:52 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink- retrying...

I can see by running a netstat that no connection is established. I have performed a tcpdump:

root@hass1:~# tcpdump -ni any port 4025
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
There is nothing to indicate any connection attempts.

The UI appears as though the component is working, the alarm component is shown, but the connection loop does not appear to work.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ngardiner]

You can ignore my previous comment - my envisalink had (strangely) lost its DHCP address while I was doing some testing, making me think that it was the 0.101 release.

Not sure why your update is failing @satssehgal, there is some discussion here on people's experiences with the release:

https://www.home-assistant.io/blog/2019/10/30/release-101/#read-more

[ur7x]

Did this ever get resolved?

I am getting a password error to my Envisalink. I'm using my Evnvisalink id and password.

Here is my config:
envisalink:
host: 192.168.1.118
panel_type: DSC
user_name: Eyezon.com id
password: Eyezon.com Pass
code: '0000'
port: 4025
evl_version: 4
keepalive_interval: 60
zonedump_interval: 30
timeout: 10
zones:
01:
name: 'Front and Garage Door'
type: 'opening'
02:
name: 'Front Motion'
type: 'motion'
03:
name: 'Family Motion'
type: 'motion'
04:
name: 'Smoke'
type: 'smoke'

partitions:
1:
name: 'Grand'

My error log is this

2020-09-30 11:18:08 INFO (MainThread) [pyenvisalink.envisalink_base_client] Started to connect to Envisalink... at 192.168.1.118:4025
2020-09-30 11:18:09 ERROR (MainThread) [pyenvisalink.envisalink_base_client] Password is incorrect. Server is closing socket connection.
2020-09-30 11:18:09 INFO (MainThread) [pyenvisalink.envisalink_base_client] An event loop was given to us- we will shutdown when that event loop shuts down.
2020-09-30 11:18:09 ERROR (MainThread) [homeassistant.components.envisalink] The Envisalink rejected your credentials
2020-09-30 11:18:09 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.updater
2020-09-30 11:18:09 INFO (MainThread) [homeassistant.setup] Setup of domain envisalink took 0.9 seconds
2020-09-30 11:18:09 ERROR (MainThread) [homeassistant.setup] Setup failed for envisalink: Integration failed to initialize.

[ur7x]

Figured it out.. the id and pass word id the Envisalink module id and password NOT the one that you use to log into the Eyezon website.