Web socket errors to Vivint API about hacs-vivint

[natekspencer]

This should be fixed with 2021.3.1

[mat1583]

I had previously attempted an update from a fresh install with the same result. What finally seemed to work was logging into my API user in the Vivint mobile app, then signing out of all devices. Once I did that, the integration started working again. My best guess according to the log messages is that a web socket connection was left open for that api user and the integration could not establish a new connection.

If this is the case, then I would still consider this an issue. If the web socket create attempt fails, then it should not attempt to update any of the Vivint devices. Each device update took 10 seconds to timeout, and it seems the attempts were in serial. That left HA unresponsive during that period.

Let me know if you need to see any other logs.

[natekspencer]

The logs you posted here all directly point to an issue with the way I was retrieving Z-Wave device details for such devices connected to the panel.

TimeoutError: [Errno 110] Connect call failed ('23.253.164.235', 80)

That's the IP address of the openzwave website I was using for device lookup. If you try to go to that address, or ping it even, you'll see that it is taking a long time or down altogether now.

File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 317, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 385, in _async_add_entity
device_info = entity.device_info
File "/config/custom_components/vivint/init.py", line 167, in device_info
"manufacturer": self.device.manufacturer,
File "/usr/local/lib/python3.8/site-packages/vivintpy/devices/init.py", line 86, in manufacturer
self.get_zwave_details()

Here, again, you'll see it is when trying to save the device_info, which does a lookup for manufacturer, which, if Z-Wave, would try to get the information from openzwave and hang.

I knew it might be a potential problem in the future, and have been thinking of ways to get around it, but haven't done so yet. So for now, Z-wave devices will just show an unknown manufacturer and model until I get that updated.

[mat1583]

Makes sense. Thanks for the explanation. I think there was still some web socket connection issue going on, but those logs have cleared after I signed out of all devices. If the issue pops up again, I'll make sure to enable more verbose logging and update this issue.

[natekspencer]

I'm gonna close this issue. But if you do see some websocket stuff, open up a new one so I can help track it there. Thanks, @mat1583!