search

kellerza / hassio-sma-em

Home Assistant SMA Add-On
MIT License
31 stars 19 forks source link

"unknown" value for sensor.power_l1 #5

Closed MisfitPunisher closed 1 month ago

MisfitPunisher commented 3 years ago

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!

macnug commented 3 years ago

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

kellerza commented 3 years ago

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

macnug commented 3 years ago

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

kellerza commented 3 years ago

Hi @macnug ,

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

macnug commented 3 years ago

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? image

kellerza commented 3 years ago

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

macnug commented 3 years ago

Hi, I tried also the legacy addon. With debug 1 I have this error: ifelse: fatal: unable to exec ./run.py: Permission denied

[cmd] ./run.py exited 126

Can you help me troubleshoot “permission denied”??

I tried all the combination available for mqtt and serial…

Thank you so much

Marco

Il giorno gio 5 ago 2021 alle 14:37 Johann Kellerman < @.***> ha scritto:

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

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kellerza/hassio-sma-em/issues/5#issuecomment-893424359, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO4XKFFW3PAHUZJULGQRWYTT3KAY7ANCNFSM5AQNSO4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

kellerza commented 3 years ago

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

macnug commented 3 years ago

Hi Keller, I tried with the last version 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 0x7fd261dd3430>)

Actually I dunno how to fix multicast error.

Have you ever find this time of issue?

Thank you for everything..

Marco

Il giorno gio 12 ago 2021 alle 09:25 Johann Kellerman < @.***> ha scritto:

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

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kellerza/hassio-sma-em/issues/5#issuecomment-897410921, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO4XKFH7OWWRQIVJ2JRRWYDT4NZPPANCNFSM5AQNSO4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

northalpha commented 3 years ago

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?

macnug commented 3 years ago

Never did that, and no I dunno how to check. May you suggest a guide or some tips on how to do that? Thank you!!!!

Il giorno gio 12 ago 2021 alle 09:59 northalpha @.***> ha scritto:

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?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kellerza/hassio-sma-em/issues/5#issuecomment-897429463, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO4XKFEY562Z67GLBWK6TQDT4N5O7ANCNFSM5AQNSO4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

kellerza commented 3 years ago

@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>)
macnug commented 3 years ago

Hi Johann,

i tried with the legacy addon,

Here you have the log, i still have pconsume in "unknown" state. I dunno how to solve this.. Thank you for any help provided

Marco

[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/1901422886/pconsume/config' payload: ('{"name": "pconsume", "dev_cla": "power", "stat_t": ' '"SMA-EM/status/1901422886/pconsume", "unit_of_meas": "W", "uniq_id": ' '"1901422886_pconsume", "dev": {"ids": ["sma_em_1901422886"], "name": "SMA ' 'Energy Meter", "mdl": "Energy Meter", "mf": "SMA"}}') ic| topic: 'homeassistant/sensor/1901422886/pconsumecounter/config' payload: ('{"name": "pconsumecounter", "dev_cla": "energy", "stat_t": ' '"SMA-EM/status/1901422886/pconsumecounter", "unit_of_meas": "kWh", ' '"uniq_id": "1901422886_pconsumecounter", "dev": {"ids": ' '["sma_em_1901422886"], "name": "SMA Energy Meter", "mdl": "Energy Meter", ' '"mf": "SMA"}}') ic| topic: 'homeassistant/sensor/1901422886/u1/config' payload: ('{"name": "u1", "dev_cla": "voltage", "stat_t": ' '"SMA-EM/status/1901422886/u1", "unit_of_meas": "V", "uniq_id": ' '"1901422886_u1", "dev": {"ids": ["sma_em_1901422886"], "name": "SMA Energy ' 'Meter", "mdl": "Energy Meter", "mf": "SMA"}}')

Il giorno lun 16 ago 2021 alle ore 18:42 Johann Kellerman < @.***> ha scritto:

@macnug https://github.com/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>)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kellerza/hassio-sma-em/issues/5#issuecomment-899656099, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO4XKFDNEX4SPTFG6GUEYWTT5E5XZANCNFSM5AQNSO4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

ghost commented 2 years ago

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.

rick2909 commented 5 months ago

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.