SOLARMAN INTEGRATION BROKEN

[mattomu22]

Very simple. After last HA update the integration stopped working. Sensors unknown. The inverter and the wifi logger are working normally. I can read values with inverter app.
Thank you.

[madness10452]

Same here

[mattomu22]

I tried to remove a reinstall but no change. Any ideas? Thanks

[sir106]

Same here

[toivio]

The same

[PV-Joe]

Just updated to:

… and everything is working fine ✅

[mattomu22]

I tried to load back up but didn't go well. I will wait for possible fix in my case.

[toivio]

How can i do downgrade?

[PV-Joe]

How can i do downgrade?

Restore from backup?
Beta releases can be faulty.

[toivio]

How can i do downgrade?

Restore from backup? Beta releases can be faulty.

I have restore, manual config is ok, but all sensors have an error stare.

[jpameli]

Same here (broken) I am on:
Core 2024.3.3
Supervisor 2024.03.1

[toivio]

Same here I am on: Core 2024.3.3 Supervisor 2024.03.1

Same, that's meen Ok or not Ok.

[jpameli]

Its broken, sorry!
Maybe its a Solarman issue? I can't even see my devices at https://home.solarmanpv.com . They show offline but they are not.

[toivio]

Its broken, sorry! Maybe its a Solarman issue? I can't even see my devices at https://home.solarmanpv.com . They show offline but they are not.

https://home.solarmanpv.com its Ok for me, but solarman is working on lokal IP add.

[jpameli]

You are right, its too late here and they went offline because of low sun.

[mattomu22]

Personally I will not revert because I did a lots of things in the last few days.
Can someone tell me if you are going to fix it? I pay annual subscription to Home Assistant. Thank you.

[maxsiindonesia]

Indonesia is also the same, it doesn't work after updating

[herijaya]

Indonesia is also the same, it doesn't work after updating

same

[liviui]

Fixed: Updated to 12.2: Entity unavailable, changed the Yaml file to anything else and then to deye_hybrid.yaml = Restart.
Start working again. Strange!

[schasan]

I do not think "broken" is the correct wording.
Deye seem to have dropped their previous old style modbus in favour of "AT+..." commands, which this integration does not (yet) support.
Try something like the following to receive a steady stream of data:

import socket
import binascii

def dump(binary, size=2, sep=' '):
hexstr = binascii.hexlify(binary)
hexstr = hexstr.decode('ascii')
return hexstr.upper()

s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
s.connect(("192.168.8.16", 8899))

while True:
buffer = s.recv(80)
print(len(buffer))
print(dump(buffer))
print(buffer)

[mattomu22]

My system is a ZCS Azzurro equivalent to sofar inverter and I was sure I am taking the data directly from the inverter via wifi. May be is on of those things that at the end was my fault and I have addes something that goes in conflict. Boh!%@£#!% I will try to disconnect the wifi dongle and try all again. This is for me.

…

On Tue, 2 Apr 2024, 14:58 schasan, ***@***.***> wrote: I do not think "broken" is the correct wording. Deye seem to have dropped their previous old style modbus in favour of "AT+..." commands, which this integration does not (yet) support. Try something like the following to receive a steady stream of data: import socket import binascii def dump(binary, size=2, sep=' '): hexstr = binascii.hexlify(binary) hexstr = hexstr.decode('ascii') return hexstr.upper() s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) s.connect(("192.168.8.16", 8899)) while True: buffer = s.recv(80) print(len(buffer)) print(dump(buffer)) print(buffer) — Reply to this email directly, view it on GitHub <#548 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXDMP6WPN5MEHQOMMSZFCSDY3KTPVAVCNFSM6AAAAABFOCSWPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZRHE3TMMJQGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Xabrim]

I solved the problem by downgrading to 1.4.3:
-Delete the Integration in HA

• Delete all downloaded Hacs files (hacs-> Solarman-> Top right corner-> Delete). Restart.
• Download 1.4.3. Restart.
• Configure the Integration. Restart again and the values changed from unknown to solid values.

[mattomu22]

Thank you very much!!! If you pass by Padova Italy a drink on you!!!!

…

On Wed, 3 Apr 2024, 14:17 Xabrim, ***@***.***> wrote: I solved the problem by downgrading to 1.4.3. Delete all downloaded Hacs files (hacs-> Solarman-> Top right corner-> Delete). Delete the Integration in HA. Restart. Download 1.4.3. Restart. Configure the Integration. Restart again and the values changed from unknown to solid values. — Reply to this email directly, view it on GitHub <#548 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXDMP6SPTJSUUQBFTNIVXWDY3PXOXAVCNFSM6AAAAABFOCSWPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZUGQZDENZYGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Hassfabi]

I solved the problem by downgrading to 1.4.3. Delete all downloaded Hacs files (hacs-> Solarman-> Top right corner-> Delete). Delete the Integration in HA. Restart. Download 1.4.3. Restart. Configure the Integration. Restart again and the values changed from unknown to solid values.

Worked for me too.
(Two Deye 600 parallel. One with SN 39xxx (FW MW3_16U_5406_1.57), one with with SN 41xxx (FW MW3_16U_5406_2.32-D1) and the SUN-MI-RELAY connected.

[toivio]

Nice, Worked for me too on 1.4.3, thanks

[nedyarrd]

Created pull request #550 to make component work again ;-)

[xwitte]

Same for me after last HA update.

Neither downgrade to 1.4.3. nor solution in pull request #550 worked for me. Still no values for sensor data. On version 1.51 I saw that the graphs sometimes showed single values spread over the whole day. But values could not be gathered regularly.

2024-04-08 11:48:06.202 WARNING (MainThread) [homeassistant.components.sensor] Updating solarman sensor took longer than the scheduled update interval 0:00:30
2024-04-08 11:48:12.365 WARNING (SyncWorker_20) [custom_components.solarman.solarman] Querying registers [3 - 112] failed, aborting.
2024-04-08 11:49:16.205 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.pv1_stand_pv1_power is taking over 10 seconds
2024-04-08 11:49:36.206 WARNING (MainThread) [homeassistant.components.sensor] Updating solarman sensor took longer than the scheduled update interval 0:00:30
2024-04-08 11:49:42.263 WARNING (SyncWorker_47) [custom_components.solarman.solarman] Querying registers [3 - 112] failed, aborting.

My specs:
Inverter: Deye SUN800G3-EU-230
Firmware version: MW3_16U_5406_1.57

Home Assistant

Core: 2024.4.1
Supervisor: 2024.03.1
Operating System: 12.1
Frontend: 20240404.1
RaspberryPi 3B+, RaspBee II, LAN+Wifi (onboard)

[Xabrim]

Check your Version again. Sometimes it auto updates/loads the wrong version. I had this problem with a different system. Delete Hacs file and the integration and try a full HA reboot before installing Version 1.4.3. Tell me if it works for you.

[xwitte]

Check your Version again. Sometimes it auto updates/loads the wrong version. I had this problem with a different system. Delete Hacs file and the integration and try a full HA reboot before installing Version 1.4.3. Tell me if it works for you.

You are right. I repeated the procedure and fully reloaded Home Assistant and then 1.4.3 was working as expected and shows collected sensor values.

Thx @Xabrim

See also #467 (comment)

[erxbout]

Hi I also had this problem!

I noticed that after I updated HASS OS
Seems that it does not work anymore with HASS OS 12.2 but with 12.1 its good!

downgrade with this command

ha os update --version 12.1

My working installation is now with versions:
core 2024.4.2
Supervisor 2024.04.0
OS 12.1
Frontend 20240404.1

[sbkbg]

Hi I also had this problem!

I noticed that after I updated HASS OS Seems that it does not work anymore with HASS OS 12.2 but with 12.1 its good!

downgrade with this command

ha os update --version 12.1

My working installation is now with versions: core 2024.4.2 Supervisor 2024.04.0 OS 12.1 Frontend 20240404.1

I CAN CONFIRM AFTER THE COMMAND SOLARMAN WORKS AGAIN :)

ha os update --version 12.1

[jmccrohan]

This is an issue that has been introduced in HA OS 12.2 with the upgrade to Docker 25. It has impacted a number of containers (add-ons), including HA core itself.

The proper fix is to remain on HA OS 12.2 and to rebuild the core container:

ha core rebuild

No changes to the Solarman integration required.

[erxbout]

Have tried that and can confirm that also works!

[deebeo-blip]

Is this something that can be expected to be adressed in HA OS in the future or will every future HA OS Update lead to the Solarman integration not working anymore? Is there anybody who can update the Solarman integration to work with Docker 25/HA OS >=12.2 ? I would happily buy them a few coffees...