-
Notifications
You must be signed in to change notification settings - Fork 71
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
Power Plug not updating values for power consumption? #328
Comments
Interesting, just tried also V1.0.0, same unable to add power plug with user name / password added with API keys and worked fine. |
Hi, just tried what @hallard suggested, but no success? I deleted all API-configured devices (Power-Plugs) and added one Power-Plug from scratch (V: 1.1.0). Hence no change (power consumption is not updated again), but now I can NOT add other Power-Plugs anymore? What is also confusing is, that add anohter device -> will result in an error: "do_reconfigure_existing"? To add more devices, you have to go to the 3-dot-Menu and "Reconfigure" the API-Interface, which then gives you the option to add, delete devices, or finish configuration. With "configuration" I tried several options, such as "1" , oder "50" or "100" and 3, 4 or 5 secondes update-intervalls, but without any success? Very strange, that your integration works, and mine not? |
Same issue here with Public API (V1.1.0 and V1.2.0): Smart Plug values are not updated every few seconds. If I reload the Integration, the value is updated only once to the correct value. |
Hello
Thank you for the new Integration-Method with the API. With API-Version now Power Plugs are shown in HA too! This is great.
But unfortunatly the power values are not updated every few Seconds, as specified in the Configuration Tab? If you reload the Integration, the value is updated once to the correct value; but later no more?
I am using Integartion 1.1.0. with HA Core 2024.9.1
PS: Updates of Devices via the old version (username & password) are working fine for me, but Power Plugs are not available in this version :-(
The text was updated successfully, but these errors were encountered: