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
OpenDTU v24.2.12 breaking API changes #139
Comments
Thank you for sharing. We will have to implement the newer firmware by time. You don't have the output of the JSON, don't you? |
just tested with openDTU [v24.2.12]and run in the same. The new version provides much less compared to the v24.1.18. Just swapped to 24.1.18 as this was my last stable version. |
First get inverster and serial numbers: We have to query every SN now separately: |
@henne49 i just anonymised the serial number and name, as well as the limit_absolute. |
same issue here... with the last version we have to request the data by inverter :O |
ran into the samme gap :D |
I have created a PR which should fix the API change and work with old and new API, please test the PR, if you can. |
@henne49 many thanks!! |
Just upgraded opendtu to v24.2.16 and can confirm venus os and vrm portal are working fine with dbus-opdendtu-1.1.0. Thanks for the quick fix! |
same for me, everything working again. Thanks so much |
Just tried the latest version of OpenDTU, but as expected dbus-opdendtu stops working. I had to go back to v24.1.26...
"REAKING CHANGE: Web API Endpoint /api/livedata/status
To reduce the heap usage it is necessary to send the inverters one by one instead of a huge response. A simple call to
/api/livedata/status
returns just some very general information. If detailed inverter information are required the inverter serial number has to appended?inv=<serial number>
.The websocket also returns only one inverter at a time. It as to be assembled at client side."
The text was updated successfully, but these errors were encountered: