StephanJoubert / home_assistant_solarman

Home Assistant component for Solarman collectors used with a variety of inverters.
Apache License 2.0
508 stars 190 forks source link

error: Querying [512 - 597] failed with exception [OSError: [Errno 30] Read-only file system] #499

Open murraythegoz opened 5 months ago

murraythegoz commented 5 months ago

Everything worked till last week. then it suddenly stopped working.

running against a ZCS azzurro ZM1ES060 with firmware V290, with the sofar_hyd3k-6k-es.yaml template.

now when trying I get the following errors: Querying [512 - 597] failed with exception [OSError: [Errno 30] Read-only file system] Querying [512 - 597] failed with exception [NoSocketAvailableError: No socket available]

any suggestion?

alain57 commented 5 months ago

same issue, i was thinking that all this was my unstable wifi, and then saw he logs and this message :/ If someone has any clue on how to fix that i would highly appreciate it

murraythegoz commented 5 months ago

opened a ticket to the vendor.

they are evaluating a firmware update to check if it could fix the issue.

just for the records, the not working configuration releases: Inverter: V290 logger: ME_08_2701_2.06 connected via ethernet

ferrarisimo commented 5 months ago

Hi, I have a ZCS HYD 5000 HP and I'm facing the same issue too In my log files I see the same Read-only logs and in addiction I also see: Querying registers [1028 - 1056] failed, aborting. The wifi connection is ok, it seems a "server" change in a registry read list ... The official Azzuro App works fine. Hope this could be useful

murraythegoz commented 5 months ago

updated inverter to V360, and logger to ME_0D_2701_5.09 (activities performed by Zucchetti following up a request from me).

hard reboot the whole inverter, but still not working.

murraythegoz commented 5 months ago

I was redirected to the standard documentation:

https://pysolarmanv5.readthedocs.io/en/stable/solarmanv5_protocol.html#frame-diagrams

Sutek commented 5 months ago

I had the same problem with this integration, but I managed to find a solution. I have Home Assistant Supervisor installed. It turned out that Docker version 25.0.1, which was supposed to be HA compatible, caused problems with Solarman integration. Downgrading Docker to version 24.0.7 solved the problem.

sudo apt install docker-ce=5:24.0.7-1~debian.12~bookworm docker-ce-cli=5:24.0.7-1~debian.12~bookworm docker-buildx-plugin=0.11.2-1~debian.12~bookworm docker-compose-plugin=2.21.0-1~debian.12~bookworm docker-ce-rootless-extras=5:24.0.7-1~debian.12~bookworm
sudo apt-mark hold docker-ce docker-ce-cli docker-buildx-plugin docker-compose-plugin docker-ce-rootless-extras
sudo reboot
ferrarisimo commented 5 months ago

I had the same problem with this integration, but I managed to find a solution. I have Home Assistant Supervisor installed. It turned out that Docker version 25.0.1, which was supposed to be HA compatible, caused problems with Solarman integration. Downgrading Docker to version 24.0.7 solved the problem.

sudo apt install docker-ce=5:24.0.7-1~debian.12~bookworm docker-ce-cli=5:24.0.7-1~debian.12~bookworm docker-buildx-plugin=0.11.2-1~debian.12~bookworm docker-compose-plugin=2.21.0-1~debian.12~bookworm docker-ce-rootless-extras=5:24.0.7-1~debian.12~bookworm
sudo apt-mark hold docker-ce docker-ce-cli docker-buildx-plugin docker-compose-plugin docker-ce-rootless-extras
sudo reboot

Thanks Sutek it works for me. I forgot that yesterday I upgraded my Debian and the only updated packages were docker 25

murraythegoz commented 5 months ago

still not working, but good point, thank you.

Querying registers [512 - 597] failed, aborting. 09:43:01 – (WARNING) Solarman (custom integration) - message first occurred at 09:36:33 and shows up 14 times Querying [512 - 597] failed, [1] retry attempts left 09:43:01 – (WARNING) Solarman (custom integration) - message first occurred at 09:36:31 and shows up 28 times Querying [512 - 597] failed with exception [V5FrameError: V5 frame contains invalid start or end values] 09:43:01 – (WARNING) Solarman (custom integration) - message first occurred at 09:36:30 and shows up 28 times

alain57 commented 5 months ago

I confirm that @Sutek found a working way i have again my deye working correctly in HA thanks a lot ... I just hope that it will be fixed in HA or docker so that the package is up to date :)

Joshua2372 commented 4 months ago

I had the same problem with this integration, but I managed to find a solution. I have Home Assistant Supervisor installed. It turned out that Docker version 25.0.1, which was supposed to be HA compatible, caused problems with Solarman integration. Downgrading Docker to version 24.0.7 solved the problem.

sudo apt install docker-ce=5:24.0.7-1~debian.12~bookworm docker-ce-cli=5:24.0.7-1~debian.12~bookworm docker-buildx-plugin=0.11.2-1~debian.12~bookworm docker-compose-plugin=2.21.0-1~debian.12~bookworm docker-ce-rootless-extras=5:24.0.7-1~debian.12~bookworm
sudo apt-mark hold docker-ce docker-ce-cli docker-buildx-plugin docker-compose-plugin docker-ce-rootless-extras
sudo reboot

Good practice! problem solved! now let's hope they solve Docker with a new upgrade. ThankU a lot.

81ondo commented 4 months ago

What about not supervised HA installation? Any advices to fix this?

doreks commented 3 months ago

finding the same problem here but i cannot fixed with the WA, any idea :

Reading package lists... Done Building dependency tree... Done Reading state information... Done Package docker-ce is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: docker-ce-cli

Package docker-buildx-plugin is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source

Package docker-ce-cli is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: docker-buildx-plugin

Package docker-compose-plugin is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source

Package docker-ce-rootless-extras is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Version '5:24.0.7-1~debian.12~bookworm' for 'docker-ce' was not found
E: Version '5:24.0.7-1~debian.12~bookworm' for 'docker-ce-cli' was not found
E: Version '0.11.2-1~debian.12~bookworm' for 'docker-buildx-plugin' was not found
E: Version '2.21.0-1~debian.12~bookworm' for 'docker-compose-plugin' was not found
E: Version '5:24.0.7-1~debian.12~bookworm' for 'docker-ce-rootless-extras' was not found
kefrens commented 2 months ago

I just upgraded to HAOS 12.2 and have the same issue. Looking at the release notte they have upgrade to docker 25 which obsivouly is not working anymore.

Does anyone have a fix for it? I can't run the sudo command and I am using HAOS through a virtualbox image.... I dont even think that the backup will revert to HAOS 12.1...

Update: turns out you can downgrade on HAOS. Simply run the following command on terminal: ha os update 12.1 and it will downgrade to 12.1 It works now... Hopefully dev will make it work with docker 25...

kefrens commented 2 months ago

What about not supervised HA installation? Any advices to fix this?

See above , in termnal: ha os update 12.1

fhrbek commented 2 months ago

Same here, solarman stopped working after upgrading to 12.2. The downgrade to 12.1 helped but the upgrade hint is back. I hope this will be solved so that I can upgrade again.

kefrens commented 2 months ago

Same here, solarman stopped working after upgrading to 12.2. The downgrade to 12.1 helped but the upgrade hint is back. I hope this will be solved so that I can upgrade again.

Turns out you just need to do following command on 12.2 after upgradeha core rebuild

It works for me now on 12.2

doreks commented 2 months ago

Same here, solarman stopped working after upgrading to 12.2. The downgrade to 12.1 helped but the upgrade hint is back. I hope this will be solved so that I can upgrade again.

Turns out you just need to do following command on 12.2 after upgradeha core rebuild

It works for me now on 12.2

applied this WA in container hassio_cli and now works!

fhrbek commented 2 months ago

Same here, solarman stopped working after upgrading to 12.2. The downgrade to 12.1 helped but the upgrade hint is back. I hope this will be solved so that I can upgrade again.

Turns out you just need to do following command on 12.2 after upgradeha core rebuild

It works for me now on 12.2

Yes, it helped and works with 2024.4.3 core as well.

Note: For some reason, I also had to reboot my Pylontech battery which is monitored by Solarman. Until then, Solarman was failing with [NoSocketAvailableError: No socket available] and the battery IP was unreachable. Interestingly, it all had worked until I updated HA OS to 12.2.

murraythegoz commented 2 months ago

Just upgraded to core 2024.4.3 and upgraded solarman to 1.5.1 (my probe has serial 21xxxxx).

Still no luck :-(

AndyNew2 commented 2 months ago

If anyone interested you can go back to HA OS 12.1 with this in the shell: ha os update --version 12.1