-
-
Notifications
You must be signed in to change notification settings - Fork 673
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
Add Zendure #17149
Add Zendure #17149
Conversation
This doesn't work if the global server is used which many advanced users even in Europe have chosen since it's supposedly more stable and offers newer devices faster etc. |
Thank you, will update asap. |
I'm preparing a pull request for the template with some additional examples etc. right now. |
First off all a HUGE THANK YOU ! To y'all for trying your damn hardest to implement the wishes of the users - you all have my deepest respect. (As I had a peek into the code there was no way in hell i could have accomplished this) I don't want to be a PIA, but the current "Bad Request error" I get while trying to configure is related to the fact, that currently the EU server is used in general and not the global one - correct? Error is: |
Probably. Waiting for @Raudi1 if he wants to grab it. |
I already did the pull request. But only for the template. I could probably figure the rest out, but it would probably take me a couple of hours at least since I'd have to set up a dev environment and take a good look at all the code first and then do it wrong a couple of times before I get it right. I don't have the time for that right now since I'm a dentist with my own practice. The last quarter is always the most busy. |
I still can't add my Zendure device even with the correct server. When I try to validate it, I get the error |
I can confirm that the global login doesn't work. EU works find. Maybe the device can only be setup in the matching region? |
Working find for me. |
Normally the device should be found on the corresponding server where the Hyper is connected to - either the global or the EU. Hence the different URLS. It should not make any difference - the response from the server should be the same. I will try to remove the server on the global one and switch over to the European to see if that works. Oddly enough I still find MQTT entries from my former tries to get the Hyper connected in my logs although it is not configured in the Yaml or the GUI.
I thought maybe that was my problem that entries are double, but I am not able to remove it at the moment. |
I have the official MQTT and the ioBroker adapter working. If I use the manual method with edit: I just set up a testing instance and was able to get the trace log. It still tries to use the EU server, even if I select global in the dropdown: |
Sorry - i could have caught that bug - but I didnt - I can confirm this find.
|
Ah, region was missing from the template, fixed! |
Fix works - i was able to add the battery with the nightly build. (I dont use the Hyper as inverter) Thanks @andig! However @Raudi1 can you confirm that when the Hyper is discharging it is shown as "Batterie laden" instead of "Batterie entladen"? OutputHomePower should be the value discharging (as in Battery-Output-to-Home-Power) Please correct me if I am wrong. |
|
Fix #14797
Note that battery control is not supported. A local api is announced for 2025, we'll revisit then.