"unknown" value for sensor.power_l1 about hassio-sma-em HOT 15 OPEN

Hi i tried everything and i have your same issue. All sensors are in "unknown"

from hassio-sma-em.

Do you see anything in your HA Core logs? Have you tried add DEBUG: 1 to your add-on configuration?

The Home Assistant integration https://www.home-assistant.io/integrations/sma/ - using the pysma library shows "unknown" during the evening

The only reason I can think of that you see "unknown" with the Energy Meter HASS.IO Add-On is if it stopped working completely/never worked

from hassio-sma-em.

Do you see anything in your HA Core logs? Have you tried add DEBUG: 1 to your add-on configuration?

The Home Assistant integration https://www.home-assistant.io/integrations/sma/ - using the pysma library shows "unknown" during the evening

The only reason I can think of that you see "unknown" with the Energy Meter HASS.IO Add-On is if it stopped working completely/never worked

Hi Keller,
i tried with the DEBUG:1 and i have this error:

DEBUG:asyncio:Datagram endpoint remote_addr=None created: (<_SelectorDatagramTransport fd=8 read=idle write=<idle, bufsize=0>>, <main.MulticastServerProtocol object at 0x7f34b4853430>)

Do you have some suggestion on how to fix it?
Thanks

from hassio-sma-em.

Hi @macnug ,

• has it ever worked?
• what environment are you using?

Your error seems related to the multicast socket. It is needed to receive the Energy meter's Speedwire packets,

from hassio-sma-em.

ed to receive the Energy meter's Speedwire packets,

Hi. thank you for your reply.
It worked for months but it stopped working, so i started using only sma solar integration and i deactivate the addon. With these last releases the prysma library removed some sensor that were fundamental like total house consumption. Now there are multiple metering sensor that are "unknown" also during day time.
I tried again with SMA energy meter addon but now it doen't work for me.

my config:
-sma sunnyboy 2,5
-sma energy meter in Speedwire connection
-nuc with proxmox and multilple VM, in one there is Hassio os.

In the UI of Sma energy meter i have Speedwire on YES the ip is the ip of the inverter or the ip of the sma energy meter?

from hassio-sma-em.

You do not need the source IP /IP of the SMA-Energy Meter

What is the old version you used? 0.5.4? I created a "Legacy" plugin based off that branch if you want to try that. https://github.com/kellerza/hassio-sma-em/tree/main/sma-em-legacy

Just add the SMA Energy Meter (Legacy) plugin under the same repository in the Supervisor

from hassio-sma-em.

from hassio-sma-em.

The joys of file permissions... you can try 0.5.5

from hassio-sma-em.

from hassio-sma-em.

Can you confirm that you are seeing the multicast packets on the HA instance or inside the container? Are you aware of how to check tis via tcpdump?

from hassio-sma-em.

from hassio-sma-em.

@macnug the error still shows asyncio, are you sure you strarted the legacy addon?

This is not an error you will get for the Legacy addon

DEBUG:asyncio:Datagram endpoint remote_addr=None created:
(<_SelectorDatagramTransport fd=8 read=idle write=<idle, bufsize=0>>,
<__main__.MulticastServerProtocol object at 0x7fd261dd3430>)

from hassio-sma-em.

from hassio-sma-em.

I had the same problem and it was the powerline adapter that does not support multicast.
So to check if everything is fine type this "sudo tcpdump host 239.12.255.254" into Terminal and look if there are packets appearing every second.

from hassio-sma-em.

I am not getting ann values from the addon, the nolrmal version 2021.9.2 gives me te following 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 0x7fa9a173a0>)

The Legacy version does do a bit more and creates sensors but stay unkown. With the following 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.
ic| topic: 'homeassistant/sensor/304XXXXXX/pconsume/config'
    payload: ('{"name": "pconsume", "dev_cla": "power", "stat_t": '
              '"SMA-EM/status/304XXXXXX/pconsume", "unit_of_meas": "W", "uniq_id": '
              '"304XXXXXX_pconsume", "dev": {"ids": ["sma_em_304XXXXXX"], "name": "SMA '
              'Energy Meter", "mdl": "Energy Meter", "mf": "SMA"}}')
ic| topic: 'homeassistant/sensor/304XXXXXX/pconsumecounter/config'
    payload: ('{"name": "pconsumecounter", "dev_cla": "energy", "stat_t": '
              '"SMA-EM/status/304XXXXXX/pconsumecounter", "unit_of_meas": "kWh", "uniq_id": '
              '"304XXXXXX_pconsumecounter", "dev": {"ids": ["sma_em_304XXXXXX"], "name": '
              '"SMA Energy Meter", "mdl": "Energy Meter", "mf": "SMA"}}')
ic| topic: 'homeassistant/sensor/304XXXXXX/u1/config'
    payload: ('{"name": "u1", "dev_cla": "voltage", "stat_t": "SMA-EM/status/304XXXXXX/u1", '
              '"unit_of_meas": "V", "uniq_id": "304XXXXXX_u1", "dev": {"ids": '
              '["sma_em_304XXXXXX"], "name": "SMA Energy Meter", "mdl": "Energy Meter", '
              '"mf": "SMA"}}')
ic| topic: 'homeassistant/sensor/304XXXXXX/psupply/config'
    payload: ('{"name": "psupply", "dev_cla": "power", "stat_t": '
              '"SMA-EM/status/304XXXXXX/psupply", "unit_of_meas": "W", "uniq_id": '
              '"304XXXXXX_psupply", "dev": {"ids": ["sma_em_304XXXXXX"], "name": "SMA '
              'Energy Meter", "mdl": "Energy Meter", "mf": "SMA"}}')

And the dev version gives me the SMA-EM/status/304XXXXXX/available that gives me online. the log also proofs this

[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.
2024-03-15 14:00:23,458 INFO    options: Loading HASS OS configuration
2024-03-15 14:00:23,463 INFO    MQTT: Connecting to mosquitto@core-mosquitto:1883
2024-03-15 14:00:23,479 INFO    MQTT: Connection successful
2024-03-15 14:00:23,981 INFO    Listening for multicast frames. Sensor discovery will be triggered by the first frame.

from hassio-sma-em.