-
-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Failed to call service select/select_option. Modbus Error: [Connection] Client is not connected #961
Comments
downgraded to Integration Version 2024.05.7 and changing "select." entities works again, |
Same issue here. Have 2nd instance for the same inverters running on the previous version and works. |
I just tried the Integration Version 2024.07.0b4, but getting the same error whenever I try to change any "select." entity (like for example select.solax3_charge_and_discharge_period2_enable) |
@02curls when updating to 2024.07.0bx did you remove the Integration, Restart HA and add it back in again? The reason I ask is that So it looks like HA is still stuck with 2024.05.7 init file, so it's miss configured. |
@wills106 no I did not, |
@wills106 I now even deleted the integration in HACS completely, restarted, downloaded the 2024.07.0b4, restarted, connected the inverter, restarted, the same problem remains |
Had the same issue. Also when delete and .... But for me it helped unplug the dongle wait 1min plug and then add the inverter. Nevertheless before doing this also removed the integration, restart HA and reinstall the integration and then did the unplug thing. Interesting thing, the other HA instance still had the connection. |
@wills106 I disconnected and deleted everything now again, upgraded to 2024.08.6, reconnected, I keep seeing these errors in logs: This error originated from a custom integration. Logger: pymodbus.logging Cancel send, because not connected! This error originated from a custom integration. Logger: pymodbus.logging Cancel send, because not connected! |
I'm having this exact same issue as well after updating to 2024.08.6. I deleted the integration, restarted and and added the integration. Restarted again. It reads values from the inverter but most of the time cannot control the inverter, giving the Failed to call service error. I have a Gen 3 inverter which is directly connected via ethernet. |
I've had the same problem when trying to upgrade to 2024.08.6. Most register writes were failing with this same Modbus Error: [Connection] Client is not connected message. I'm on an X1-Hybrid-Gen3 (H1E302), direct via ethernet. Reverted my main instance to 2024.05.7 in the mean time, will try again on a test instance if I can and see if Wireshark helps explain things. |
I've got the same inverter, connected the same way. How did you revert to 2024.05.7? I can only see 2024.08.x or Main in the list. Downloading Main didn't help me. Thanks, |
I also have the same problem after upgrading to 2024.08.6 when issuing a sequence of commands to change the Charger Use Mode followed by changing the Manual Mode Select. |
Do you get the Modbus error - no response after 3 attempts for the first command? I get that, even though the change seems to actually stick. After that it's the Client not connected error. |
upgraded to 2024.08.7 observations: when chaning the select.solax_charge_and_discharge_period2_enable, NOT IMMEDIATELY, but with some lag, I get the same error "Failed to call service number/set_value. Write: Error communicating with device" and the state of that entity DOES NOT CHANGE as wished logs here: This error originated from a custom integration. Logger: pymodbus.logging Cancel send, because not connected! This error originated from a custom integration. Logger: pymodbus.logging Cancel send, because not connected! |
@BillyRichards I did get the "no response after 3 attempts" when changing a "select." entity ONCE, but many more times on that same entity I just got the "Failed to call service number/set_value. Write: Error communicating with device" and the state of that entity DID NOT CHANGE as wished |
Unfortunately HACS does not go back far enough in versions to go back that far. I reverted by removing from HACS and HA configuration, then manually grabbing the 2024.05.7 zip from the releases page and then followed the manual install procedure. Finally added it in the HA config again. |
Thanks, I'll give that a try later. |
hello @wills106 is there anything else I can further investigate/try to help solve the problem? thank you
|
I'm just looking into increasing the number of attempts. That might help. |
Do you have logger configured as:
If so you get the following errors:
|
yes, and yes, I remember seeing the first 2 of those errors |
There was 3 connection attempts each with 3 retires. |
@wills106 not sure what that means in terms of time roughly, but as I mentioned before, 47 seconds is what it took on average |
upgraded to 2024.08.8, restarted, the same issue remains: when chaning the select.solax_charge_and_discharge_period2_enable, NOT IMMEDIATELY, but with some lag, I get the same error "Failed to call service number/set_value. Write: Error communicating with device" and the state of that entity DOES NOT CHANGE as wished at all |
This is affecting me as well since 08 Works for a bit after unplugging Wifi stick, then rebooting HA. Only affects changing settings, can still view entities Randomly fails which is a disaster as I rely on automations to stop house battery discharging when charging car on Octopus Intelligent Very grateful if you can identify and address the problem! |
I'm having this exact same issue as well after updating to 2024.08.6. I deleted the integration, restarted and and added the integration as suggested. Restarted again. It reads values from the inverter but I cannot control the inverter (e.g. charger use mode), giving the Failed to call service error. I have a Solax Gen 2 inverter which is directly connected via ethernet. As a side effect of deleting and reinstalling solax modbus my engeryboard lost the price information for all times before new installation. Any hints on how to reestablish historic price information ? |
I had this same issue, I am using latest HA Core and have now rolled back Solax to 2024.05.7 |
Has anyone tried 2024.08.10 or later? As that changed the |
Working fine on .10 so far!
Thanks
…On Sun, 25 Aug 2024, 08:10 wills106, ***@***.***> wrote:
Has anyone tried 2024.08.10
<https://github.com/wills106/homeassistant-solax-modbus/releases/tag/2024.08.10>
or later? As that changed the client.connect behaviour back to 2024.05.7
behaviour.
—
Reply to this email directly, view it on GitHub
<#961 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDVSJCIF6VSYOJZKUCNELS3ZTF7PBAVCNFSM6AAAAABK7GHXW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYG4YDQMJRGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Working well for me too. |
Closing down as appears to be fixed. |
Describe the bug
Since updating to the latest versions of
all entities are updating and displaying perfectly fine in HA,
but whenever I try to change any "select." entity (like for example select.solax3_charge_and_discharge_period2_enable)
I now always get "Failed to call service select/select_option. Modbus Error: [Connection] Client is not connected"
Integration Version
2024.07.0b2
Homeassistant core version
2024.7.2
Inverter brand
SolaX Power
Plugin used
plugin_solax.py
Serial prefix
H34A10
Inverter firmware versions
ARM 1.31 DSP 1.33
Connection Method
SolaX Pocket WiFi
Dongle firmware
3.015.02
Detailed Error Log
This error originated from a custom integration.
Logger: pymodbus.logging
Source: custom_components/solax_modbus/init.py:553
integration: SolaX Inverter Modbus (documentation, issues)
First occurred: 19:20:29 (5 occurrences)
Last logged: 21:00:15
Cancel send, because not connected!
This error originated from a custom integration.
Logger: pymodbus.logging
Source: custom_components/solax_modbus/init.py:575
integration: SolaX Inverter Modbus (documentation, issues)
First occurred: 19:20:14 (6 occurrences)
Last logged: 21:00:05
Cancel send, because not connected!
Additional context
No response
The text was updated successfully, but these errors were encountered: