-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
New API calls #83
Comments
Never got a decent response. Only some helpdesk person that did not know what he was talking about I altered my code in https://github.com/tijsverkoyen/HomeAssistant-FusionSolar/pull/78/files to call the new endpoint if the “old” one fails. |
Hi @tijsverkoyen thanks for the update. I tried some things but I was noticing that no data was coming in via the getDevRealKpi, did you find a workaround for this call? |
I should look into it. I don’t know for sure if I use that call in the integration. But I am on my phone at the moment. But I will check later |
@reyntjensw I was wrong. The integration does use I think the best approach is to get in touch with Huawei support. Keep me posted please! |
@reyntjensw any update on this issue. Feel free to reopen this issue is you get any news. |
Hi @tijsverkoyen just fyi I am looking at this https://github.com/jgriss/FusionSolarPy/tree/main. If I can translate the FusionSolarPy to node and get it working, I'll migrate everything to that. |
Thank you for the links. For most people the integration is working but is sometimes stuck for a unknown reason. |
I know the feeling ;-) |
Hi
I came across this post #68 (comment) and I am working on a similar integration for the Homey platform (https://github.com/reyntjensw/Homey-FusionSolar), where I am running into the same issue.
Some users are not able to use the plugin, because their account is to new.
What I was wondering is do you already have a use case for the api call ** getDevHistoryKpi**, I am not finding any examples online nor in the code base. Or did you get any feedback from Huawei?
Thanks in advance.
The text was updated successfully, but these errors were encountered: