Comments (7)
janiversen
commented on September 13, 2024
You are right what do you want me to respond differently.
I have never disputed it might be a software problem, but there are a lot more software in play than just the modbus integration. Between the 2 versions even python itself was changed.
I am sorry, but I have no idea where I should start looking for a problem within the modbus integration since there are no indications that it does something it should not do, all I can say is that at least some users including myself do not have a problem.
from core.
florie1706
commented on September 13, 2024
That is after reloading the inverter and the integration of the 2024.6.3 container, gets connected again immediately.
Will investigate further.
2024-06-26 10:48:17.983 INFO (MainThread) [homeassistant.components.modbus] Modbus reloading
2024-06-26 10:48:17.983 WARNING (MainThread) [homeassistant.components.modbus.modbus] modbus SMA_Wechselrichter communication closed
2024-06-26 10:48:17.983 DEBUG (MainThread) [pymodbus.logging] Connecting to 10.10.10.11:502.
2024-06-26 10:48:17.984 DEBUG (MainThread) [pymodbus.logging] Connecting comm
2024-06-26 10:48:17.992 DEBUG (MainThread) [pymodbus.logging] Connected to comm
2024-06-26 10:48:17.992 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-06-26 10:48:17.992 INFO (MainThread) [homeassistant.components.modbus.modbus] modbus SMA_Wechselrichter communication open
2024-06-26 10:48:19.597 DEBUG (MainThread) [pymodbus.logging] Adding transaction 1
2024-06-26 10:48:19.597 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-06-26 10:48:19.597 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x1 0x0 0x0 0x0 0x6 0x3 0x3 0x77 0x41 0x0 0x2
2024-06-26 10:48:19.685 DEBUG (MainThread) [pymodbus.logging] recv: 0x0 0x1 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x8 0x29 0xe2 old_data: addr=None
2024-06-26 10:48:19.685 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x1 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x8 0x29 0xe2
2024-06-26 10:48:19.685 DEBUG (MainThread) [pymodbus.logging] Frame check failed, missing part of message len 12, MBAP len 7 !!
2024-06-26 10:48:19.686 DEBUG (MainThread) [pymodbus.logging] recv: 0x3e old_data: addr=None
2024-06-26 10:48:19.686 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x1 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x8 0x29 0xe2 0x3e
2024-06-26 10:48:19.686 DEBUG (MainThread) [pymodbus.logging] Factory Response[ReadHoldingRegistersResponse': 3]
2024-06-26 10:48:19.686 DEBUG (MainThread) [pymodbus.logging] Getting transaction 1
2024-06-26 10:48:19.686 DEBUG (MainThread) [pymodbus.logging] Frame check, no more data!
2024-06-26 10:48:19.687 DEBUG (MainThread) [pymodbus.logging] Adding transaction 2
2024-06-26 10:48:19.687 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-06-26 10:48:19.687 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x2 0x0 0x0 0x0 0x6 0x3 0x3 0x78 0x37 0x0 0x2
2024-06-26 10:48:19.835 DEBUG (MainThread) [pymodbus.logging] recv: 0x0 0x2 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x0 0x0 0x19 old_data: addr=None
2024-06-26 10:48:19.835 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x2 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x0 0x0 0x19
2024-06-26 10:48:19.835 DEBUG (MainThread) [pymodbus.logging] Frame check failed, missing part of message len 12, MBAP len 7 !!
2024-06-26 10:48:19.836 DEBUG (MainThread) [pymodbus.logging] recv: 0xe7 old_data: addr=None
2024-06-26 10:48:19.836 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x2 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x0 0x0 0x19 0xe7
2024-06-26 10:48:19.836 DEBUG (MainThread) [pymodbus.logging] Factory Response[ReadHoldingRegistersResponse': 3]
2024-06-26 10:48:19.836 DEBUG (MainThread) [pymodbus.logging] Getting transaction 2
2024-06-26 10:48:19.836 DEBUG (MainThread) [pymodbus.logging] Frame check, no more data!
2024-06-26 10:48:29.597 DEBUG (MainThread) [pymodbus.logging] Adding transaction 3
2024-06-26 10:48:29.597 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-06-26 10:48:29.598 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x3 0x0 0x0 0x0 0x6 0x3 0x3 0x77 0x41 0x0 0x2
2024-06-26 10:48:29.755 DEBUG (MainThread) [pymodbus.logging] recv: 0x0 0x3 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x8 0x29 0xe2 old_data: addr=None
2024-06-26 10:48:29.755 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x3 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x8 0x29 0xe2
2024-06-26 10:48:29.755 DEBUG (MainThread) [pymodbus.logging] Frame check failed, missing part of message len 12, MBAP len 7 !!
2024-06-26 10:48:29.756 DEBUG (MainThread) [pymodbus.logging] recv: 0x51 old_data: addr=None
2024-06-26 10:48:29.756 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x3 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x8 0x29 0xe2 0x51
2024-06-26 10:48:29.756 DEBUG (MainThread) [pymodbus.logging] Factory Response[ReadHoldingRegistersResponse': 3]
2024-06-26 10:48:29.756 DEBUG (MainThread) [pymodbus.logging] Getting transaction 3
2024-06-26 10:48:29.756 DEBUG (MainThread) [pymodbus.logging] Frame check, no more data!
2024-06-26 10:48:29.756 DEBUG (MainThread) [pymodbus.logging] Adding transaction 4
2024-06-26 10:48:29.757 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-06-26 10:48:29.757 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x4 0x0 0x0 0x0 0x6 0x3 0x3 0x78 0x37 0x0 0x2
2024-06-26 10:48:29.905 DEBUG (MainThread) [pymodbus.logging] recv: 0x0 0x4 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x0 0x0 0x1a old_data: addr=None
2024-06-26 10:48:29.906 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x4 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x0 0x0 0x1a
2024-06-26 10:48:29.906 DEBUG (MainThread) [pymodbus.logging] Frame check failed, missing part of message len 12, MBAP len 7 !!
2024-06-26 10:48:29.907 DEBUG (MainThread) [pymodbus.logging] recv: 0x1 old_data: addr=None
2024-06-26 10:48:29.907 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x4 0x0 0x0 0x0 0x7 0x3 0x3 0x4 0x0 0x0 0x1a 0x1
2024-06-26 10:48:29.908 DEBUG (MainThread) [pymodbus.logging] Factory Response[ReadHoldingRegistersResponse': 3]
2024-06-26 10:48:29.908 DEBUG (MainThread) [pymodbus.logging] Getting transaction 4
2024-06-26 10:48:29.908 DEBUG (MainThread) [pymodbus.logging] Frame check, no more data!
from core.
janiversen
commented on September 13, 2024
Reloading both does not help identify a problem, test if reloading just one of parts make it work again.
Or did you mean reloading any of the parts make it work again?
from core.
florie1706
commented on September 13, 2024
Container with 2024.3.3 runs smoothly the whole time. No interaction needed.
Container with 2024.6.3 (or better said newer than 2024.3.3) stopped working (usually after 2 - 6 days), restarted the inverter as no connection is possible any longer (even with a restart/reload of the 2024.6.3 container). After the inverter restarted I reloaded only the 2024.6.3 container which is seen above.
When I am right, in the image I use (linuxserver/homeassistant) python was upgraded to 3.12 in 2024.2 and since that image, it stayed with python 3.12
from core.
janiversen
commented on September 13, 2024
So it seems clearly your device is blocking reconnect..
the reason it disconnects can be too long between reads
the reason it does not accept a new a new connect is because it happens too fast.
anyhow this is way beyond the modbus integration.
from core.
florie1706
commented on September 13, 2024
Maybe true, but why is, at the same time, the container with 2024.3.3 still able to connect (even a restart of the container does not change that) without error? In the network both containers have the same ip from the server host. That said I can fire up more containers with 2024.3.3 and 2024.6.3, all 2024.3.3 containers get a connection while the others do not.
Any option you could provide to have the time between reads changed? That would be great.
from core.
janiversen
commented on September 13, 2024
There are a lot of technical reasons why the old version works and the new not, basically it's because more or less everything changed.
This channel is for bugs not for support, I cannot help you more, I have given you several pointers..if you find something (fact) that points at the modbus integration I am happy to help.
from core.
Related Issues (20)
- Dexcom: last_updated time should change even if the state is the same between updates. HOT 2
- Fronius Integration Missing Device Ohmpilot after Fronius Firmware Update to 1.32.5-1 HOT 3
- New Ecovac DEEBOT NEO 2.0 PLUS does not work with ecovac integration HOT 5
- Tuya: Unknown error occurred upon integration configuration HOT 3
- Weather .get_forecasts for NWS station returns Failed to call service weather.get_forecasts. Unknown error HOT 6
- Detected blocking call to open inside the event loop by integration 'local_todo' HOT 2
- Detected blocking call inside the event loop by integration 'adguard' HOT 2
- `integration` calls `async_listen` with run_immediately which is deprecated HOT 2
- AirGradient temperature sensor below absolute zero HOT 3
- iCloud Integration requires reauth on every reboot/reload HOT 2
- Detected blocking call to listdir with args HOT 3
- Detected blocking call to listdir with args HOT 5
- Meteoclimatic HOT 12
- 'MpdDevice' object has no attribute '_playlists' HOT 2
- Support for Tuya smart universal IR with integrated temperature/humidity sensor HOT 1
- Failed login attemtps return HTTP 200, should return 401 HOT 1
- Apple TV entity picture HOT 2
- Beta 2004.7 breaks integration HOT 2
- 2024.6.4 cannot not start up HACS HOT 2
- AirTouch 5 Integration stopped working after AirTouch update HOT 19
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from core.