SMA scrape stop working in version 2024.4.4 #116289
Assignees
Labels
Comments
|
Please provide a link to the documentation of the used integration. Further also check and provide log messages, thx 👍 |
|
Sorry to say, it is the old way to use MODBUS not an integration as such there is one of MODBUS but that one never worked for my SMA inverter. A snippet of my configuration is: `modbus:
|
|
Hey there @janiversen, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) modbus documentation |
|
Pleas still check and provide some logs, thx |
|
Modbus is a proper integration ! and this is the only modbus integration in Home assistant, there are other integrations that uses it, like a custom component for SMA. Please provide a debug log as pr modbus integration documentation. It would also be nice to know what does not work.....saying it stopped working is not really helpful for anyone. And now to the funny part, there are no modbus changes between 2024.4.3 and 2024.4.4 as far as I know. |
|
And please remember to remove all custom components before making the debug log as pr instructions in the issue template. |
|
As said, for some older SMA inverters (12 years), does the integration not function, it will never make contact with the more simple webcon of the device. Therefore was the above way necessary described above with code in the configuration.yaml. It also does mean that there is no log, for this way, only the official for me not working integration gives out a log. I highly appreciate your time and effort you put into answering me, thanks. |
|
O I found a way to get a log, log output: `Logger: homeassistant.components.modbus.modbus Pymodbus: SMA: Error: device: 3 address: 30775 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.0.xxx:502]` Hope that helps. |
|
No I need a debug log as pr modbus integration documentation. The log above only tells your device is not connected. I am not sure which integration you are referring to, that do not work but it does not seem to be a HA integration and therefore not something we consider in this channel. |
|
I hope you might come up with some sort of idea how to fix it Jan, I understand this is not the forum. I can not get any other debug information nor reason why it stopt working after the update to core 2024.4.4. It is an official MODBUS integration as it has been before the enity add on for MODBUS as can be seen in the link you gave me: https://www.home-assistant.io/integrations/modbus. |
|
Without a debug log I will nit investigate further but simply conclude that even though there might be a bug, you did not want to help. Making a debug log is a simple task and the least you can do if you want us to use our time on your problem. |
|
Sorry I have no clue howto get a debug log from MODBUS. I did change configuration. yaml debug options, to get the error I got. But in the systems tab log there is not a MODBUS log! No clue how to get a debug, if I could I have send that to you immediately for help for this is certainly a problem i love to get resolved, for my energy dash is corrupted now, my temperature readings for the cooling automation of the inverter is corrupted, do I want a solution, well most definitely. |
|
there is no separate log for modbus only, but the debug logs are contained in the central homeassistent log - as all integration logs could be found there. |
|
As noted in the modbus integration documentation, there are NO talk of a separate log, just the homeassistant.log !! If you added the log options correctly, the log contains a lot more than the error (which you also got without the debug log), it contains all modbus communication. |
|
Hi @janiversen I seem to have the same issue with my SMA inverter. So let's see if I can get you the necessary info. What version of Home Assistant Core has the issue? What was the last working version of Home Assistant Core? What type of installation are you running? Integration causing the issue Link to integration documentation on our website Diagnostics information Example YAML snippet Anything in the logs that might be useful for us? Additional information |
|
Same here, SMA inverter of 2011, always worked fine. now every couple of days no new data until power off the breaker and restart HA It is working now, but here is the log: |
|
We need a debug log showing the problem! |
|
Ok, thought “frame check failed” is maybe already a hint 😉 So I wait until no new data is received and post the debug log then. Thanks |
|
No need to, just checked the sma code, it does not use the modbus integration so you need to talk to a sma maintainer. (sma uses pysma instead of modbus). Changing labels and unsubscribing |
|
@janiversen I do not use the sma integration but directly the modbus integration. See the config above. It starts with modbus … |
|
Then it has nothing to do with this issue, which is about the sma integration. |
|
Same thing here. I'm using Modbus since I never got the SMA integration to connect. Using the Modbus integration with my SMA inverter had been rock solid for years. Would there be anything else you need instead of above debug log? |
|
Hi @janiversen I believe the OP misnamed this. Looking at his yaml, he is using Modbus as well. If it helps, and as this was closed, I had opened a new issue for this under modbus. #116683 |
|
Hi @janiversen now the error came back, so here is my debug log. Looks like this connection error reappears every 10 seconds until I restart the inverter and HA |
|
You device or something in between breaks the connection, this is not a bug in the integration 2024-05-15 09:33:19.375 WARNING (MainThread) [pymodbus.logging] Failed to connect |
|
It worked for 6 days now. And when this happens the connection won't come back unless put the breaker down from the inverter and fire it up again. Even then I need to restart HA to have it working again for a couple of days. Ping request to the inverter is 100% fine all the time. Never had this issue before. Did not change anything on hardware side. Why did it work with older HA versions for ages without any error?!? And I am not alone ... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem
SMA scrape or modbus stopt working in core 2024.4.4 operating system 12.2. No values are parsed anymore.
What version of Home Assistant Core has the issue?
2024.4.4
What was the last working version of Home Assistant Core?
2024.4.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
SMA scrape
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: