Core: Error setting up entry Configuration.yaml for smappee

[tomvanswam]

The problem

After upgrading to 0.112.0 all my smappee sensors are gone, And i have an error in the log "Error setting up entry Configuration.yaml for smappee"

I removed the old host and oauth login keys from the configuration.yaml, restarted HA and added the smappee integration via UI and logged in on the oauth2.

It seems like the new integration is trying to connect to a local smappee hosted mqtt broker, however none is present on my device, and thus the connection fails. Aborting the creation and usage of all sensors that could come from the API itself. So now I don't have any Smappee sensors.

Environment

• Home Assistant Core release with the issue: 0.112.0
• Last working Home Assistant Core release (if known): 0.111.4
• Operating environment (OS/Container/Supervised/Core): OS
• Integration causing this issue: Smappee
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/smappee/

Problem-relevant configuration.yaml

smappee:
  client_id: !secret smappee_client_id
  client_secret: !secret smappee_client_secret

Traceback/Error logs

Log Details (ERROR)
Logger: homeassistant.config_entries
Source: components/smappee/__init__.py:67
First occurred: 9:19:56 PM (1 occurrences)
Last logged: 9:19:56 PM

Error setting up entry Configuration.yaml for smappee
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 220, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/smappee/__init__.py", line 67, in async_setup_entry
    await hass.async_add_executor_job(smappee.load_service_locations)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/pysmappee/smappee.py", line 40, in load_service_locations
    farm=self._farm)
  File "/usr/local/lib/python3.7/site-packages/pysmappee/servicelocation.py", line 73, in __init__
    self.load_configuration()
  File "/usr/local/lib/python3.7/site-packages/pysmappee/servicelocation.py", line 137, in load_configuration
    self.mqtt_connection_local = self.load_mqtt_connection(kind='local')
  File "/usr/local/lib/python3.7/site-packages/pysmappee/servicelocation.py", line 414, in load_mqtt_connection
    mqtt_connection.start()
  File "/usr/local/lib/python3.7/site-packages/pysmappee/mqtt.py", line 245, in start
    port=config['MQTT']['local']['port'])
  File "/usr/local/lib/python3.7/site-packages/paho/mqtt/client.py", line 937, in connect
    return self.reconnect()
  File "/usr/local/lib/python3.7/site-packages/paho/mqtt/client.py", line 1071, in reconnect
    sock = self._create_socket_connection()
  File "/usr/local/lib/python3.7/site-packages/paho/mqtt/client.py", line 3522, in _create_socket_connection
    return socket.create_connection(addr, source_address=source, timeout=self._keepalive)
  File "/usr/local/lib/python3.7/socket.py", line 728, in create_connection
    raise err
  File "/usr/local/lib/python3.7/socket.py", line 716, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

Additional information

Smappee system information:
Nr of signatures received from acquisition engine | 10390
Last software update |  n.a.
Application software version and build nr | 1.0.0S buildNr # 1081
Acquisition Software version | 3.22
EMeter working config | single phase
EMeter type | SmappeeT
Serial ID | 1005001897
OS build nr | 8

[probot-home-assistant[bot]]

smappee documentation
smappee source
_{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

Hey there @bsmappee, mind taking a look at this issue as its been labeled with an integration (smappee) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[gieljnssns]

I have the same error.

[papacrown]

Also getting the same error.

[bsmappee]

Starting from 0.112.0 we have completely reviewed the Smappee integration with all new monitors and plugs since it was not being updated in the last 4 years. Also, we decided to rather have the development in house, so we can quickly adapt the integration to newer products, features and issues. Of course the integration should still work for older monitors. We're reproducing the error mentioned and working on a fix (Smappee Energy and Smappee Solar devices do not have a local MQTT broker).

[matteos1]

after updating to 0.102, configured the configuration.yaml and integration in settings, smappee in homeassistant no longer provides indications on the sensors and switches. in additions only smappee - Configuration.yaml appears without indicating any identity or device. From Home assistant it is impossible to control the smappee switches now.

2020-07-02 14:34:42 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Configuration.yaml for smappee
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 220, in async_setup
hass, self
File "/usr/src/homeassistant/homeassistant/components/smappee/__init__.py", line 67, in async_setup_entry
await hass.async_add_executor_job(smappee.load_service_locations)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(self.args, *self.kwargs)
File "/usr/local/lib/python3.7/site-packages/pysmappee/smappee.py", line 40, in load_service_locations
farm=self._farm)
File "/usr/local/lib/python3.7/site-packages/pysmappee/servicelocation.py", line 73, in __init__
self.load_configuration()
File "/usr/local/lib/python3.7/site-packages/pysmappee/servicelocation.py", line 137, in load_configuration
self.mqtt_connection_local = self.load_mqtt_connection(kind='local')
File "/usr/local/lib/python3.7/site-packages/pysmappee/servicelocation.py", line 414, in load_mqtt_connection
mqtt_connection.start()
File "/usr/local/lib/python3.7/site-packages/pysmappee/mqtt.py", line 245, in start
port=config['MQTT']['local']['port'])

[bsmappee]

Yes, this is the same stack trace as mentioned initially and which has been resolved in pull request #37331 and merged into dev. You can either use the dev version or revert the HA update to a previous version until this PR got merged into master.