Closed ruimmsimoes closed 7 months ago
simondrake
commented
7 months ago +1 same here. I take some solace in the fact I'm not alone, as I was going mad trying to figure out what was wrong on my end.
@ruimmsimoes - can you share the automation that does the reload, please?
anton4
commented
7 months ago I had to revert back to 2024.02.7b2 and that version is working fine.
simondrake
commented
7 months ago I don't see that in the list of versions, on mobile at least, did you download it manually?
ruimmsimoes
commented
7 months ago Here is the automation I created, it also notifies me every time the integration is restarted:
alias: Reiniciar integração SolaX
description: ""
trigger:
- platform: template
value_template: >-
{{ now() - states.sensor.solax_house_load.last_updated >=
timedelta(minutes=15) }}
condition: []
action:
- service: homeassistant.reload_config_entry
metadata: {}
data:
entry_id: 277a443271216e367913be7bf7e5794b
- service: notify.mobile_app_iphonex_de_rui
metadata: {}
data:
title: Reiniciada integração SolaX
message: >-
Dados SolaX sem actualização à mais de 15 minutos, integração
reinicializada.
mode: singleTo find out the entry_id of your integration, using the file editor, go to file /homeassistant/.storage/core.config_entries and search for 'solax_modbus'.
Unfortunately the automation is executing more than twice every hour.
ruimmsimoes
commented
7 months ago I had to revert back to 2024.02.7b2 and that version is working fine.
I also can't revert back to that version. The earliest it lets me revert to is 2024.03.2. @anton4 How did you manage to revert?
If that version is working then the problem is probably with the changes put in place in version 2024.03.1.
wills106
commented
7 months ago By default HACS only shows the previous 5 https://hacs.xyz/docs/configuration/options
simondrake
commented
7 months ago @ruimmsimoes - thanks.
I changed to using config_entry_id. For anybody else seeing this, if you want to validate it's correct- you can run the following:
cat homeassistant/.storage/core.config_entries | jq -r '.data.entries | .[] | select(.title == '<integration name>' | .entry_id'Thanks @wills106 - I see it now. I've just updated to the newest version, so I'll see if the issue happens again and, if it does, I'll downgrade.
anton4
commented
7 months ago I don't see that in the list of versions, on mobile at least, did you download it manually?
Yes, I did it manually, but @wills106 pointed out you can modify the default HACS (5 previous versions) to show earlier versions also.
PatrikTrestik
commented
7 months ago It also happened to me. Can you confirm that you are using any "remotecontrol" automation?
I had impression that after disabling my remote control it works without issue. I specifically blame "Enabled No Discharge". Checking the code.
ruimmsimoes
commented
7 months ago Downgraded to integration version 2024.02.6 and since downgrading the integration only had to be restarted 4 times in two days. Although not perfect it is much more stable.
Has anyone been able to find out which changes are provoking this behavior?
If you need someone to test any changes I’m available.
@PatrikTrestik I am not using any automations.
lazy-pete
commented
7 months ago Hi - I e also been seeing a lot of failures. I’m using the solax_Modbus integration as comms for fboundy’s PV_opt integration and found over the past few days that the integration is failing overnight - most evident by a huge drift between the clock sync times I see in the pv_opt dashboard, so I’m guessing the inverter time last seen is when it fails.
Logs from last night below I think - I’ll try and put in the reload automation and downgrade as above meantime.
Logger: homeassistant Source: helpers/update_coordinator.py:261 First occurred: 03:26:12 (2 occurrences) Last logged: 03:26:16
Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 417, in _async_refresh self.async_update_listeners() File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 183, in async_update_listeners update_callback() File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 497, in _handle_coordinator_update self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 992, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1113, in _async_write_ha_state state, attr, capabilities, shadowed_attr = self.async_calculate_state() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1050, in async_calculate_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 998, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 548, in state value = self.native_value ^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/devolo_home_network/sensor.py", line 229, in native_value next( StopIteration
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 261, in _handle_refresh_interval await self._async_refresh(log_failures=True, scheduled=True) RuntimeError: coroutine raised StopIteration
This error originated from a custom integration.
Logger: pymodbus.logging Source: custom_components/solax_modbus/init.py:388 integration: SolaX Inverter Modbus (documentation, issues) First occurred: 25 March 2024 at 23:48:14 (61 occurrences) Last logged: 03:27:55
Failed to connect Failed to connect [Errno 113] Connect call failed ('192.168.1.25', 502)
This error originated from a custom integration.
Logger: custom_components.solax_modbus Source: custom_components/solax_modbus/init.py:393 integration: SolaX Inverter Modbus (documentation, issues) First occurred: 25 March 2024 at 23:48:14 (61 occurrences) Last logged: 03:27:55
Unable to connect to Inverter at 192.168.1.25:502
lazy-pete
commented
7 months ago I’m wondering from some of the above whether it’s actually a local networking fail to communicate with the EW11 dongle, although a HA restart seems to fix things which would counter that.
simondrake
commented
7 months ago Downgrading to 2024.03.7b4 didn't fix the issue for me, it would occasionally zero out all the stats and only a HA restart fixes the issue - integration reload didn't.
I've upgraded to 2024.03.7b4 again, but if anyone has a confirmed working version please share it.
The fact a HA restart fixes the problem, I'd hazard a guess it's an issue inside HA.
matomatusov
commented
7 months ago @simondrake I think version 2024.02.5 is stable. I was also reverting to lower versions.
mlj11
commented
7 months ago I have the same problem. The integration stops working and the only soulution is to restart HA. It stops working usually when the remote control is activated and within a few seconds/minutes it stops updating (not always, but very likely). There is probably a delay when reading data, because the entities are not updated at 15s interval, but with some delays (15-25s). I've gone back a few versions and can confirm that I don't see this issue with version 2024.02.6. The remote control works correctly and the updates are done exactly at 15s intervals.
johny-mnemonic
commented
7 months ago I can confirm the same behavior. Integration works just fine till you try to use Remotecontrol. No matter whether it's from automation or manually.
Seems like the integration gets completely stuck as only restart of HA helps. Trying to reload the integration just gets the service stuck as well.
Here is my debug log output:
2024-03-29 04:16:56.041 DEBUG (MainThread) [custom_components.solax_modbus.plugin_solax] Evaluated remotecontrol_trigger: corrected/clamped values: [('remotecontrol_power_control', 'Enabled Power Control'), ('remotecontrol_set_type', 'Set'), ('remotecontrol_active_power', 3000.0), ('remotecontrol_reactive_power', 0), ('remotecontrol_duration', 20.0)]
2024-03-29 04:16:56.042 DEBUG (MainThread) [custom_components.solax_modbus] Ready to write multiple registers at 0x7c: [1, 1, 3000, 0, 0, 0, 20]
2024-03-29 04:17:02.477 DEBUG (MainThread) [custom_components.solax_modbus.plugin_solax] Evaluated remotecontrol_trigger: corrected/clamped values: [('remotecontrol_power_control', 'Enabled Power Control'), ('remotecontrol_set_type', 'Set'), ('remotecontrol_active_power', 3000.0), ('remotecontrol_reactive_power', 0), ('remotecontrol_duration', 20.0)]
2024-03-29 04:17:02.477 DEBUG (MainThread) [custom_components.solax_modbus] ready to repeat button remotecontrol_trigger data: [('remotecontrol_power_control', 'Enabled Power Control'), ('remotecontrol_set_type', 'Set'), ('remotecontrol_active_power', 3000.0), ('remotecontrol_reactive_power', 0), ('remotecontrol_duration', 20.0)]
2024-03-29 04:23:04.534 WARNING (MainThread) [homeassistant.components.automation.solax_not_updated] Solax not updated : Already runningIt basically sets the Remotecontrol and immediately gets stuck. Probably it is somewhere in the autorepeat function.
I have an automation to detect stuck Solax integration and reload the integration, but as you can see on the last line, it reports Already running as the service which tries to reload the integration got stuck as well trying to reload the integration...
Downgrade to 2024.02.6 fixed it for me as well.
PatrikTrestik
commented
7 months ago It also crashed for me while using Remote control. But it works when I use only "Enable Power Control" which does no calculation and only sets "Active Power Target".
I'm going to check code if there is something obvious.
PatrikTrestik
commented
7 months ago Hang in debugger, good. It seams that there is some locking problem. I would like to fix it today if I find a time.
adamhf
commented
7 months ago @PatrikTrestik I'm seeing the same issue as you, issuing a PowerControl command such as 'No Discharge' causes the integration to lock up. Reverting to 2024.02.6 seems to have resolved the issue. I saw it for the first time last night after a reboot, I've kept up to date with HA core releases and versions of this plugin so unsure which combination caused the issue to surface.
Edit: This is with a Solax G4 3.7Kw Hybrid and the Waveshare RS485
Looking at my update history, this issue started after updating to 2024.03.07 from 2024.03.06 whilst running HA Core 2024.3.3
PatrikTrestik
commented
7 months ago https://github.com/wills106/homeassistant-solax-modbus/pull/827 should help.
If you have time please test from my branch even before it is merged.
simondrake
commented
7 months ago Still happening for me. @wills106 - can we reopen this?
lazy-pete
commented
7 months ago Also still having to reboot HA periodically
P
On Mon, 1 Apr 2024 at 15:30, Simon Drake @.***> wrote:
28120F89-654E-4FC5-81C7-CBBC38048AAB.jpeg (view on web) https://github.com/wills106/homeassistant-solax-modbus/assets/62928647/efeb6c5f-4bd1-4b52-bc68-0ac07a17050d
Still happening for me. @wills106 https://github.com/wills106 - can we reopen this?
— Reply to this email directly, view it on GitHub https://github.com/wills106/homeassistant-solax-modbus/issues/816#issuecomment-2029847564, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHMEIQYVC3USFC32F5FGLADY3FVO7AVCNFSM6AAAAABFBVRUNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRZHA2DONJWGQ . You are receiving this because you commented.Message ID: @.***>
Describe the bug
Last few weeks once/ twice a day the integration stops updating values.
This week the problems started occurring more often (many times a day). I created an automation to reload the integration, and after the reload the data starts flowing again.
The integration had been working without any problem for several months.
Integration Version
2024.03.6
Homeassistant core version
2024.3.1
Inverter brand
SolaX Power
Plugin used
plugin_solax.py
Serial prefix
H34A15
Inverter firmware versions
ARM 1.35 and DSP 1.33
Connection Method
Generic USB RS-485 adapter
Dongle firmware
Serial connection
Detailed Error Log
Additional context
No response