-
Notifications
You must be signed in to change notification settings - Fork 428
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
Cannot get POWR2 to report status #941
Comments
I have a similar issue. Voltage is reporting properly but current and power are not. |
I can't do anything when your device really reports zero power and current. |
When the values on the device for power and current are 0 I'm happy for it to report 0 in HA, When the values are not 0 I would expect it to report that to HA but it doesn't. (Unless I'm repeatedly polling the device with the update_entity workaround - see OP for when this can be a problem in itself.). |
You don't read docs carefully. Auto mode uses local and cloud connection simultaneously. There is one cloud command that can force device auto updates. Device will send updates locally. But command can be send only with auto or with cloud mode. |
I did read your docs carefully and it specifically says local mode can be used and that it does not require internet connectivity. Great that is what I want too. The only need for cloud connectivity , you suggest , is to get a list registered devices. Fine when my devices change I'll use auto mode to update my device list. But my devces are not changing so I'm happy to continue to use the file that is saved locally. At no point anywhere do you say internet connectivity is required to get the power/voltage/current values from your device. If that is the situation then say so in your readme , make it unambiguosly clear to everyone exactly what functionality you are giving up not using auto or cloud mode. |
Docs says:
Cloud help not necessary for some pow devices. But for user with problems it could help. I'm not related with sonoff or ewelink, so don't know why this happens. |
Please reopen the issue if it is still relevant |
Ever since upgrading to SonoffLAn 3.x I've been unable to get power/current/voltage readings reported back to home assistant from amy POWR2 devices. I didn't have any issues prior to v3.
In the first instance I have the error reported in the supervisor log that the "sensor.sonoff_1000cd9566_current has unit A which is unsupported for device_class power" same error for sensor.sonoff_1000cd9566_voltage . Neither device was being recognised as the correct device class. Eventually I managed to figure out I needed to add a customized device class to my config file:
That at least got rid of the device_class error. But I still was not getting any voltage/power/current reported to HA ( other than the voltage figure detected at the startup of HA - after that it just flatlined with no variation at all ).
If I repeatedly called the update_entity service ( every 3 mins say ) I could get some values reported , but if the update_entity call coincides with a switch.turn_on or off call it would cause them to fail. In the case of the turn_on by causing the entire device to go offline or in the case of a turn_off to just not work leaving the device in a turned on state. As far as I can see the update_entity call is supposed to be used to advise the user that there is a new code update available for a device or entity , so why this service is supposed to be used to report values like power etc I simply don't get.
I've tried to config the devices as follows :
N.B. The code above is correctly formatted I believe in the config file , but I just cannot get the 'insert code' option here to retain formatting so Ive had to use - for space to represent indentation.
But I get nothing reported.
When running an update_entity call every 3 mins I have seen the voltage fluctuating by as much as between 250v to 242v in just 20 mins so if this reporting config was doing something it should surely be able to report that.
Will someone please tell me what I have to do to get this to report back the status of these devices ?
The supervisor logs don't seem to show anything relevant , just multiple instances of stuff like this - that I think have already bee reported:
the debug logs are just things like this:
The text was updated successfully, but these errors were encountered: