Repository navigation
Replies: 1 comment
Update & SolutionI managed to completely resolve the issue. The problem was not with the Deye logger or its Modbus TCP configuration on Port 502 (the Link2 settings were perfectly fine). Instead, the issue stems from an incompatibility between recent Home Assistant/Python updates and the codebase of this specific, archived repository. It triggers severe asynchronous blocking errors and internal exceptions ( How to fix this for anyone facing the same issue:
It will connect instantly and natively via pure Modbus TCP without any errors. I am closing this discussion as resolved! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone / Developer,
I am having trouble getting any data from my Deye inverter using this integration. All entities remain as "Unavailable" (No disponible) in Home Assistant.
Here are my specific hardware and configuration details:
Environment Details
deye_hybrid.yaml(Also testeddeye_sg04lp3.yamlinitially)Context & Steps Already Taken
Due to recent Deye firmware security changes in the 1.7.x branch (where the traditional local port 8899 is blocked), I have manually enabled the native Modbus TCP feature on the logger's local web interface:
Modbus TCPprotocol on Port502. Link1 remains untouched on default (Deye MQTTS).502and thedeye_hybrid.yamldefinition file.Despite the logger's Link2 being properly saved and active on port 502, the integration is still unable to fetch or populate any sensor data.
My Questions
mbtcp) required by the newer 1.7.2 firmwares when using port 502?deye_hybrid.yamlfile (such as forcing a specific parser or connection type) to make it work under this firmware setup?Any guidance or diagnostic steps would be highly appreciated. Thank you so much for your amazing work on this integration!
All reactions