kellerza / hassio-sma-em Goto Github PK

sensor.s1consume has unit VA which is unsupported for device_class energy ---> must have device_class: apparent_power
sensor.s3consume has unit VA which is unsupported for device_class energy
sensor.s2consume has unit VA which is unsupported for device_class energy
sensor.s2consumecounter has unit kVAh which is unsupported for device_class energy
sensor.s3consumecounter has unit kVAh which is unsupported for device_class energy

Any idea how to resolve or what a root cause could be?

2021-09-11 20:16:18 ERROR (MainThread) [homeassistant.util.logging] Exception in async_discover when dispatching 'mqtt_discovery_new_sensor_mqtt': ({'name': 'u1', 'device_class': 'voltage', 'state_topic': 'SMA-EM/status/1900*****/u1', 'unit_of_measurement': 'V', 'unique_id': '190*****_u1', 'state_class': 'measurement', 'last_reset': '2021-07-30T00:00:00+00:00', 'device': {'identifiers': ['sma_em_190*****'], 'name': 'SMA Energy Meter', 'model': 'Energy Meter', 'manufacturer': 'SMA'}, 'platform': 'mqtt'},)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 180, in async_discover
    config = schema(discovery_payload)
  File "/usr/local/lib/python3.9/site-packages/voluptuous/validators.py", line 218, in __call__
    return self._exec((Schema(val) for val in self.validators), v)
  File "/usr/local/lib/python3.9/site-packages/voluptuous/validators.py", line 341, in _exec
    raise e if self.msg is None else AllInvalid(self.msg, path=path)
  File "/usr/local/lib/python3.9/site-packages/voluptuous/validators.py", line 337, in _exec
    v = func(v)
  File "/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py", line 817, in validate_callable
    return schema(data)
  File "/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py", line 432, in validate_mapping
    raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: extra keys not allowed @ data['last_reset']

Would it be possible to modify the addon to work with the statistics changes made in 2021.8 that we can use the Energy Dashboard? That would be awesome, so we would be able to get rid off the awful sunnyportal stuff.

Got that running now.
But it only "polls" pcconsume, pconsumecounter:max and u1.
If i try to ad other sensors as like psupply the entry just dissapears.
Am I doing something wrong?

When I first installed this, thank you by the way, it "found" my HM2 without a hitch.

Then, for some unknown reason, not anymore. Deinstalling or installing the other two flavors changed nothing. I have no idea what SMA 42xxxxx295 is supposed to be. I have a SUNNY BOY and a HM2, that is it. Neither has a serial that starts with 42!

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO:sensors:Unknown sensor: pconsume
INFO:sensors:Unknown sensor: pconsumecounter
INFO:sensors:Unknown sensor: u1
INFO:sensors:Discover 0/3 sensors on SMA 42xxxxx295

The strange part is, my inverter (SUNNY BOY 5.0) has NEVER found HM nor HM2. All SMA Software works though. PORTAL, PLACES and the ANDROID App all deliver reliable data.

I successfully built a GLOW, but that cannot read the power to grid. GRID_POWER is always positiv, even when supplying to the grid.

Why could this be happening? I am assuming all cables are ok, as the SMA software works ok. Is it possible, that there is a problem with cables if SMA can read all data?

Thanks for your troubles,

Regards from Mannheim, Germany

Hi

I ve updatet sma em in core-2021.6.6 to version 0.7,
The green light shows that 0.7 is running.

But the MQTT entity dosnt work

My config:

MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_USERNAME: XXXXXXX
MQTT_PASSWORD: XXXXXXX
SMA_SERIALS: []
FIELDS:
  - pconsume
  - pconsumecounter:max
  - u1
  - psupply
  - sconsume
  - ssupply
  - cosphi
  - frequency
  - pconsumecounter
  - psupplycounter
THRESHOLD: 10
RECONNECT_INTERVAL: 86400
DEBUG: 0

The Mqtt shows offline

Good evening community,

I am not receiving any sensors in the MQTT. What am I doing wrong? Attached is the log.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
DEBUG:asyncio:Datagram endpoint remote_addr=None created: (<_SelectorDatagramTransport fd=8 read=idle write=<idle, bufsize=0>>, <main.MulticastServerProtocol object at 0x7fad84d3a0>)
INFO:sensors:Unknown sensor: pconsume
INFO:sensors:Unknown sensor: pconsumecounter
INFO:sensors:Unknown sensor: u1
INFO:sensors:Unknown sensor: frequency
INFO:sensors:Unknown sensor: p2consume
INFO:sensors:Unknown sensor: p2supply
INFO:sensors:Unknown sensor: p3consume
INFO:sensors:Unknown sensor: p3supply
INFO:sensors:Unknown sensor: q3consume
INFO:sensors:Unknown sensor: speedwire-version
INFO:sensors:Unknown sensor: pconsumecounter
ic| res: []
INFO:sensors:Discover 0/11 sensors on SMA 4294967295
WARNING:asyncio:Executing <Task pending name='Task-2' coro=<process_emparts() running at /usr/src/app/sensors.py:85> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7fad6bc070>()] created at /usr/local/lib/python3.9/asyncio/base_events.py:424> created at /usr/src/app/./run.py:29> took 0.299 seconds
INFO:sensors:Unknown sensor: pconsume
INFO:sensors:Unknown sensor: pconsumecounter
INFO:sensors:Unknown sensor: u1
INFO:sensors:Unknown sensor: frequency
INFO:sensors:Unknown sensor: p2consume
INFO:sensors:Unknown sensor: p2supply
INFO:sensors:Unknown sensor: p3consume
INFO:sensors:Unknown sensor: p3supply
INFO:sensors:Unknown sensor: q3consume
INFO:sensors:Unknown sensor: speedwire-version
INFO:sensors:Unknown sensor: pconsumecounter
ic| res: []
INFO:sensors:Discover 0/11 sensors on SMA 4294967295

Greetz
Benedikt

It would be great if a docker image could be provided for installation of home home assistant which don't use the add-on store or supervisor.

Now I know what the magic cure is!! Found it on a german website and they had the tip from a german solar-forum.

With all the software deinstalling and generally mucking around, I completely forgot one very important thing.

It was suggested to put all SMA on ONE switch, with NOTHING else. I had a bunch of stuff besides the SMA parts on my switch. This "SMA-Switch" is then plugged into the switch of your choice, and that is it. Worked like a charm and got all the SMA gremlins sorted. As soon as I put everything back on a single switch, my inverter can't find the HM2 anymore.

Best part, I had a cheapo switch lying around and it worked out just perfect. Was exactly the one recommended to fix this!!! Go figure...

So to all of you out there that have some sort of gremlins in your SMA setup, try this very cheap fix. Worked perfectly for me, "Gerätestatus" is still green. Changes back to red, if everything goes on one switch!!!

I don't quite see where this lower limit is coming from. An average SMA EM does not seem to produce more than one message a second, which in my opinion is a good rate and makes it well usable for purposes like EVCC which probably benefit from a short interval. The :N average functions already allow the user to apply a rate limit, and the plugin would send only one message every N seconds for those "channels" onto the MQTT bus. This could be used just fine within Home Assistant then. And given that the events are time discrete anyway, there is, at least in my opinion, no reason to implement a different rate limit than a time-based one.

Hi
Have anyone seen this before.

Logger: homeassistant.util.logging
Source: util/logging.py:105
First occurred: August 12, 2021, 8:44:09 AM (2 occurrences)
Last logged: August 12, 2021, 8:44:09 AM

Exception in async_discover when dispatching 'mqtt_discovery_new_sensor_mqtt': ({'name': 'pconsume_5', 'device_class': 'power', 'state_topic': 'SMA-EM/status/1900248759/pconsume_5', 'unit_of_measurement': 'W', 'unique_id': '1900248759_pconsume_5', 'device': {'identifiers': ['sma_em_1900248759'], 'name': 'SMA Energy Meter', 'model': 'Energy Meter', 'manufacturer': 'SMA'}, 'state_class': 'energy', 'platform': 'mqtt'},) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 180, in async_discover config = schema(discovery_payload) File "/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py", line 272, in __call__ return self._compiled([], data) File "/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict return base_validate(path, iteritems(data), out) File "/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py", line 432, in validate_mapping raise er.MultipleInvalid(errors) voluptuous.error.MultipleInvalid: value must be one of ['measurement'] for dictionary value @ data['state_class']

Exception in async_discover when dispatching 'mqtt_discovery_new_sensor_mqtt': ({'name': 'psupply_5', 'device_class': 'power', 'state_topic': 'SMA-EM/status/1900248759/psupply_5', 'unit_of_measurement': 'W', 'unique_id': '1900248759_psupply_5', 'device': {'identifiers': ['sma_em_1900248759'], 'name': 'SMA Energy Meter', 'model': 'Energy Meter', 'manufacturer': 'SMA'}, 'state_class': 'energy', 'platform': 'mqtt'},) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 180, in async_discover config = schema(discovery_payload) File "/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py", line 272, in __call__ return self._compiled([], data) File "/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict return base_validate(path, iteritems(data), out) File "/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py", line 432, in validate_mapping raise er.MultipleInvalid(errors) voluptuous.error.MultipleInvalid: value must be one of ['measurement'] for dictionary value @ data['state_class']

Hi firends! When there's not solar production the sensor.power_l1 does not appear with a 0 value, appears as a "unknown".
And also, all the other sensors appears as a "currently unavailible" when I reboot the HA and there is not solar production.

Can it be solved? Thank you for your integration, I love your work, makes our lives easier!

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
DEBUG:asyncio:Datagram endpoint remote_addr=None created: (<_SelectorDatagramTransport fd=8 read=idle write=<idle, bufsize=0>>, <main.MulticastServerProtocol object at 0x7f5ff90423a0>)

Hola,

is it possible to get the value for how much energy i feed into the grid?

Hi Kellerza
The Add-on works great thank you.
I just couldn't see the filtered values after adding the info to the configuration.yaml file
I used the friendlly (sensor.sma_grid_total_5s) names like you show in the docs.md but just shows unavailable.
So I had to use the original entity name (sensor.pconsumecounter) in the filter platform part.
Not sure why but I thought you would like the feed back.
Thanks Again
Nicko1

Is it possible to increase the resolution of the "counter" variables?
Currently only two decimal places are passed to HA. It would be nice if all 4 decimal places are passed to HA.

Hello, my SMA Energy Meter (192.168.178.X) is in a different subnet than Home Assistant (192.168.100.X). How can I still integrate the connection via this add-on?

Maybe this is related to #7 but in my setup i am getting zero information out of your addon.

Setup: KVM Host with HASSOS/Supervisor thing on a bridged network. I can confirm mosquitto broker, user and pass are correct and working with some python paho script.

Inside the homeassistant terminal as well as inside your container i am seeing the multicast traffic:

➜  ~ docker exec -ti addon_6a2c1c7a_sma-em /bin/sh

/usr/src/app # tcpdump -s0 -vvvvv host 239.12.255.254
tcpdump: listening on enp0s3, link-type EN10MB (Ethernet), snapshot length 262144 bytes
15:38:43.195123 IP (tos 0x0, ttl 1, id 50230, offset 0, flags [DF], proto UDP (17), length 636) SMA300xxxxxxx.46883 > 239.12.255.254.9522: [udp sum ok] UDP, length 608
15:38:43.394567 IP (tos 0x0, ttl 1, id 50239, offset 0, flags [DF], proto UDP (17), length 636) SMA300xxxxxxx.46883 > 239.12.255.254.9522: [udp sum ok] UDP, length 608
15:38:43.594985 IP (tos 0x0, ttl 1, id 50250, offset 0, flags [DF], proto UDP (17), length 636) SMA300xxxxxxx.46883 > 239.12.255.254.9522: [udp sum ok] UDP, length 608
15:38:43.794439 IP (tos 0x0, ttl 1, id 50257, offset 0, flags [DF], proto UDP (17), length 636) SMA300xxxxxxx.46883 > 239.12.255.254.9522: [udp sum ok] UDP, length 608
15:38:43.994454 IP (tos 0x0, ttl 1, id 50277, offset 0, flags [DF], proto UDP (17), length 636) SMA300xxxxxxx.46883 > 239.12.255.254.9522: [udp sum ok] UDP, length 608

Addon Config:

MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_USERNAME: mqtt-user
MQTT_PASSWORD: xxxxx
SMA_SERIALS: []
FIELDS:
  - pconsume
  - pconsumecounter:max
  - u1
  - psupply
  - sconsume
  - ssupply
  - cosphi
  - frequency
  - pconsumecounter
  - psupplycounter
THRESHOLD: 80
RECONNECT_INTERVAL: 86400
DEBUG: 1
AUTODISCOVER_CONFIG:
  - key: state_class
    value: measurement
  - key: last_reset
    value: '2021-07-30T00:00:00+00:00'

DNS lookup inside container is working:

/usr/src/app # nslookup core-mosquitto
Server:		172.30.32.3
Address:	172.30.32.3#53

Name:	core-mosquitto.local.hass.io
Address: 172.30.33.0

Addon Log

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
DEBUG:asyncio:Datagram endpoint remote_addr=None created: (<_SelectorDatagramTransport fd=8 read=idle write=<idle, bufsize=0>>, <__main__.MulticastServerProtocol object at 0x7f7b68e96490>)

Any idea? Would really love to see this fly :D

Hello,

i have the problem that this addon generates a very high CPU load after a few hours. One of the two assigned cores for HA then runs at 100% continuously and the addon then often says 45-50% CPU load. As soon as I stop the addon, the CPU load of the core goes down to 0.1-1% insantly. When I restart the addon everything is ok for the beginning, after a few hours the load increases again to 45-50% (1 core=100% of the host system).

My host system has 2 cores (2 and 3) allocated for HA (Docker).

after 2-3 hours (Host)

Addon:

after Restart of this Addon:

I hope we can isolate the problem within the addon. Thank you and have a nice Christmas

Hi,

two days ago it worked perfectly, suddenly I only get this readings:
INFO:sensors:Unknown sensor: pconsume
INFO:sensors:Unknown sensor: psupply
INFO:sensors:Unknown sensor: u1
INFO:sensors:Unknown sensor: u2
INFO:sensors:Unknown sensor: u3
INFO:sensors:Unknown sensor: pconsumecounter
INFO:sensors:Unknown sensor: psupplycounter
INFO:sensors:Discover 0/7 sensors on SMA 4294967295

Even with the serial of my SHM configured.

The SHM works, because I have a OpenWB wallbox running which reads the data correctly.

Hey,

thanks for writing this great addon. I do have a usability question: After exposing all relevant fields I always get 0 for psoncume. Is that as it should be? How would I get the correct current grid usage?

Cheers,
Matthias

Hi my data manager is showing negative current (meaning using from the grid)

but in Home assistant is showing 0A

how can I fix that?
I have tried setting the minimum lower but that doesn't work.

I get the following warning message in Homeassistant for the fields i1, i2 and i3:

Logger: homeassistant.components.sensor
Source: components/sensor/__init__.py:738
Integration: Sensor (documentation, issues)
First occurred: 10:17:07 (3 occurrences)
Last logged: 10:17:07

Entity sensor.sma_energy_meter_i1 (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'A' which is not a valid unit for the device class ('energy') it is using; expected one of ['MJ', 'Wh', 'GJ', 'MWh', 'kWh']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
Entity sensor.sma_energy_meter_i2 (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'A' which is not a valid unit for the device class ('energy') it is using; expected one of ['MJ', 'Wh', 'GJ', 'MWh', 'kWh']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
Entity sensor.sma_energy_meter_i3 (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'A' which is not a valid unit for the device class ('energy') it is using; expected one of ['MJ', 'Wh', 'GJ', 'MWh', 'kWh']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22

I guess this entities needs state_class: measurement and device_class: current instead of total_increase and energy.

Config:

MQTT_HOST: IP
MQTT_PORT: 1883
MQTT_USERNAME: USER
MQTT_PASSWORD: PW
SMA_SERIALS: []
FIELDS:
  - pconsume
  - pconsumecounter
  - psupply
  - psupplycounter
  - frequency
  - p1consume
  - p1consumecounter
  - p1supply
  - p1supplycounter
  - p1consume
  - i1
  - u1
  - p2consume
  - p2consumecounter
  - p2supply
  - p2supplycounter
  - i2
  - u2
  - p3consume
  - p3consumecounter
  - p3supply
  - p3supplycounter
  - i3
  - u3
THRESHOLD: 80
RECONNECT_INTERVAL: 86400
DEBUG: false
AUTODISCOVER_CONFIG: []

English version:
HA reports an error on the wrong device class for currents.

Following the device class list here: https://www.home-assistant.io/integrations/sensor/
the device class "current" with unit "A" or "mA" should be used for currents.
The below error messages says the device class "energy" is used with the unit "A".
Can you fix the device class for currents and change it from "energy" to "current"?

German version:
HA meldet einen Fehler wegen einer falschen Device Class für Ströme.

Entsprechend der device class liste hier: https://www.home-assistant.io/integrations/sensor/
sollte die device class "current" mit der Einheit "A" oder "mA" für Ströme verwendet werden.
In der unten stehenden Fehlermeldung steht, dass die device class "energy" mit der Einheit "A" verwendet wird.
Könnten Sie die device class für Ströme von "energy" auf "current" umstellen?

Here the error message from the home assistant log:

Logger: homeassistant.components.sensor
Source: components/sensor/init.py:663
Integration: Sensor (documentation, issues)
First occurred: 13:12:42 (3 occurrences)
Last logged: 13:12:42

Entity sensor.sma_energy_meter_i1 (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'A' which is not a valid unit for the device class ('energy') it is using; expected one of ['MJ', 'GJ', 'Wh', 'kWh', 'MWh']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
Entity sensor.sma_energy_meter_i2 (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'A' which is not a valid unit for the device class ('energy') it is using; expected one of ['MJ', 'GJ', 'Wh', 'kWh', 'MWh']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
Entity sensor.sma_energy_meter_i3 (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'A' which is not a valid unit for the device class ('energy') it is using; expected one of ['MJ', 'GJ', 'Wh', 'kWh', 'MWh']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22

The documentation hint towards the requirement for an MQTT server, which is needed to ingest the sensor data into Home Assistant (and also enable auto-discovery). Given that this is an "add-on" to Home Assistant, I could imagine that the data could be passed to Home Assistant directly.

Is it possible to remove this dependency? I do have Mosquitto running anyway, so I'm not affected by this, but then again, it doesn't make a lot of sense to me. However, I don't know very much about Home Assistant's add-on/plugin system, and this could be an entirely normal thing to do.

Please note that I do appreciate the MQTT integration which I could potentially use with other software, e.g., EVCC. If there is an alternative way to pass the messages, this should be retained as an optional feature. As far as I can see, the SMA-EM scripts support that anyway and you seem to be using that, too.

Edit: I forgot to include this: thank you for providing this plugin in the first place. Users of SMA energy meters can enjoy live energy comsumption/supply data along with long-term statistics and use those to optimize their power use. It's much easier to setup than, e.g., the original SMA-EM project with MQTT.

Is it possible to install this addon with HACS?

Hi,

first of all: A big thank you for getting your handy dirty with SMA!

I recently got a solar system of a SMA TRIPOWER (which i can acces via the HA SMA integration) and a SMA Sunny Island (for the installed battery, which i cannot acces, because there is only one SMA integration possible, right).

I read your comments of some so not reliable date and tried your SMA HomeManager via MQQT here.
The "only" readouts i can get are almost the same ones i get via the SMA integration.

I was hoping for a way to access the battery (via the HomeManager EM), but more than this for a way to monitor the consumtion of my whole house as i can see it in the SunnyPortal webpage. I thought, in the end ALL data is running through the HomeManager and could be read there.

Am i wrong with that assumption? None (TRIPOWER and Sunny Island) are givinhg me a saensor for that, so i figured, it should be possible via sma-em?

Thank you for any information.

I'm having issues setting up the add-on.

I've installed:
Mosquitto broker
Current version: 6.1.2

I'm new to MQTT, but when using MQTT explorer I can connect to the MQQT :

Those are my settings:

Looking at the ingegrations screen in HA, I didn't see the MQTT, I've added it manually:

I'm missing any entities auto discovered?

I'm running HA:

In the SMA-EM config I've got this:

MQTT_HOST: 192.168.1.50 MQTT_PORT: 1883 MQTT_USERNAME: hassmqqt

In HA config/users:

I'm not sure what I'm missing here, but to me it looks like the data isn't going from the SMA-EM to MQTT?

I am using this extension with a freshly installed HA. I know the setup is correct because I do get (correct) data from my SMA Tripower. Unfortunately, the data flow only runs for around 4-5 minutes and it stops. The HA entities do not get updated anymore until I restart it with the same result .. it runs for another period of 4-5 minutes.

Am I missing a setting or something? The logs do not say anything strange. Any help appreciated

I'm using a Tripower-X Inverter and the SHM 2.0.

I regularly receive errors in the log files that various sensor data are not available.
Under options I already added the Serial number of the SHM 2.0

INFO:sensors:Unknown sensor: q3supply
INFO:sensors:Unknown sensor: q3supplycounter
INFO:sensors:Unknown sensor: qconsume
INFO:sensors:Unknown sensor: qconsumecounter
INFO:sensors:Unknown sensor: qsupply
INFO:sensors:Unknown sensor: qsupplycounter
INFO:sensors:Unknown sensor: s1consume
INFO:sensors:Unknown sensor: s1consumecounter

For a long time I couldn't make sense of it all. In the meantime, I think I know the cause.

The Tripower-X send out Speedwire-Packets every minute or so.

58 bytes received from [192.168.2.XXX]
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 53 4D 41 00 00 04 02 A0 00 00 
00000010: 00 01 00 26 00 10 60 65 09 A0 
00000020: FF FF FF FF FF FF 00 00 74 01 
00000030: 0A 30 B4 B3 00 00 00 00 00 00 
00000040: 9B C7 00 02 00 00 00 00 00 00 
00000050: 00 00 00 00 00 00 00 00 

these packets are much too short with 58 bytes compared to the 608(?) bytes to contain data.

sma-em-measurement even crashes because the serial entry is missing from the dict with the data.
https://github.com/datenschuft/SMA-EM/blob/master/sma-em-measurement.py#L82

I don't know if a filter on a packet size makes sense or if one would have to include a better parsing of the speedwire packets.

Hi there,

Getting the following error when trying to install the add-on, any guidance would be appreciated.

Thanks.

_**Failed to install add-on**

The command '/bin/ash -o pipefail -c pip3 install --no-cache-dir paho-mqtt~=1.5.0 attrs requests~=2.24.0 icecream' returned a non-zero code: 1_