Upgrade to Latest Version

[deliverer33]

I have 2 SPAN panels. I'm trying to upgrade to the latest 2.x code and both my panels fail upon the upgrade. I have attempted to delete both and add again, with the same result. I validated I'm on firmware Firmware: spanos2/r202603/05. Below are my logs from Home Assistant. It looks like something with DNS, but not sure. I tried adding the SPAN panel by both ip and fqdn, neither option works. This worked perfectly prior to upgrading and the other day I attempted to upgrade and didnt want to deal with it, so I rolled back. Now that I have deleted my Span devices in HA, I'm committed to getting this working with some help hopefully.

Logger: homeassistant.config_entries
Source: config_entries.py:762
First occurred: 5:17:23 PM (2 occurrences)
Last logged: 5:18:54 PM

Error setting up entry Span Panel for span_panel
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/homeassistant/config_entries.py", line 762, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/span_panel/init.py", line 303, in async_setup_entry
await client.connect()
File "/usr/local/lib/python3.13/site-packages/span_panel_api/mqtt/client.py", line 124, in connect
await self._bridge.connect()
File "/usr/local/lib/python3.13/site-packages/span_panel_api/mqtt/connection.py", line 176, in connect
await self._loop.run_in_executor(None, _blocking_tls_and_connect)
File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.13/site-packages/span_panel_api/mqtt/connection.py", line 166, in _blocking_tls_and_connect
self._client.connect(
~~~~~~~~~~~~~~~~~~~~^
host=self._host,
^^^^^^^^^^^^^^^^
port=self._port,
^^^^^^^^^^^^^^^^
keepalive=MQTT_KEEPALIVE_S,
^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/paho/mqtt/client.py", line 1435, in connect
return self.reconnect()
~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/paho/mqtt/client.py", line 1598, in reconnect
self._sock = self._create_socket()
~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/paho/mqtt/client.py", line 4609, in _create_socket
sock = self._create_socket_connection()
File "/usr/local/lib/python3.13/site-packages/paho/mqtt/client.py", line 4640, in _create_socket_connection
return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/socket.py", line 840, in create_connection
for res in getaddrinfo(host, port, 0, SOCK_STREAM):
~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/socket.py", line 977, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno -2] Name does not resolve

[cayossarian]

I'm curious if your HA and panel are on different network segments? MQTT is broadcasting .local which is link-local so that would not resolve across segments.

[cayossarian]

On second thought the Reconfigure would have the same problem.

I think the issue is the mDNS resolution of .local link-local

Please try v2.0.4b3 which is a pre-release but it is near ready, I removed the simulation which would not affect you but I need to release the simulator add-on first. Your upgrade to v2.0.4 will be smooth if the beta works for you. You need to pick another release when downloading in HACs and find that release. Let me know the outcome.

[cayossarian]

Now v2.0.4b3

[deliverer33]

The latest beta resolved the problem. For the record I did try a reconfigure without any success. Could the issue be I have both span panels hard wired and on WiFi?

[cayossarian]

Perhaps, but what I can say is that having WiFi and Ethernet connected is against best practices according to SPAN. Seems like a firmware problem IMHO.

I would open a ticket with SPAN and have them address it by disabling the WiFi. I block the WiFi MAC but many folks don't have that sort of control on their network.

[deliverer33]

Perhaps, but what I can say is that having WiFi and Ethernet connected is against best practices according to SPAN. Seems like a firmware problem IMHO.

I would open a ticket with SPAN and have them address it by disabling the WiFi. I block the WiFi MAC but many folks don't have that sort of control on their network.

what exactly should I report? Something not resolving correctly with DNS?

[cayossarian]

I would report that you have LAN/Ethernet connected and WiFi is also connected which is against the best practices, they've heard this before. They just need to disconnect the WiFi since you can't and don't connect it again once they do that.