Vera: errors after adding (too many?) devices

For a while I’ve been using home assistant together with my Vera edge z-wave controller and the vera component. It work like a treat, but now that I added a lot of devices last weekend (light switches and motion sensors), triggers from the vera are often not picked up.

In the hass log files, I see a lot of errors like these:

2018-01-08 20:01:56 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.bedlamp_schakela_9 fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connection.py", line 141, in _new_conn
    (self.host, self.port), self.timeout, **extra_kw)
  File "/usr/local/lib/python3.4/dist-packages/urllib3/util/connection.py", line 83, in create_connection
    raise err
  File "/usr/local/lib/python3.4/dist-packages/urllib3/util/connection.py", line 73, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 601, in urlopen
    chunked=chunked)
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 357, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/lib/python3.4/http/client.py", line 1090, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python3.4/http/client.py", line 1128, in _send_request
    self.endheaders(body)
  File "/usr/lib/python3.4/http/client.py", line 1086, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python3.4/http/client.py", line 924, in _send_output
    self.send(msg)
  File "/usr/lib/python3.4/http/client.py", line 859, in send
    self.connect()
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connection.py", line 166, in connect
    conn = self._new_conn()
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connection.py", line 150, in _new_conn
    self, "Failed to establish a new connection: %s" % e)
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x6ac00f90>: Failed to establish a new connection: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/requests/adapters.py", line 440, in send
    timeout=timeout
  File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 639, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/usr/local/lib/python3.4/dist-packages/urllib3/util/retry.py", line 388, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.2.5', port=3480): Max retries exceeded with url: /data_request?output_format=json&id=variableget&Variable=LastSceneID&serviceId=urn%3Amicasaverde-com%3AserviceId%3ASceneController1&DeviceNum=9 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x6ac00f90>: Failed to establish a new connection: [Errno 111] Connection refused',))

It seems like the vera thinks hass is polling it too often and is refusing connections. Is there anything I could do about this?

It certainly does look like thats the case. I’m not sure right off hand what could be done but I can look at the code and see what could be done. How many devices did you have before, and how many do you have now?

I actually think there’s something wrong with my Vera unit, after removing several devices (more than I added before the problem) I still get a lot of these errors. I’m now in the process of moving to a aeon labs stick instead of the vera which seems to be a better solution after all.