-
Notifications
You must be signed in to change notification settings - Fork 496
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 consumption reporting through state.power
#423
Comments
2.05.04 is online now for all platforms.
Albeit I like the simplicity of |
Thanks!
If the plug supports attribute reporting, this would probably be easier, but if it doesn't we'd need to poll the sensor. It's mains powered, so no big deal, but no easy poll manager. Anyways, it seems kinda academic: the ubisys reports something, but definitely not the consumption of the attached lights. It varies from 12 (when the dimmer is off) to 5 (when the connected lights are at full birghtness). Maybe the power drawn by the dimmer itself? The OSRAM plugs seems to report 28000 when the power is off, and 400 when their power is on, irrespective what power the the connected device is drawing (or even if a device is connected). It works brilliantly for the Heiman, though. |
Hi Guys So from what I can read here and with the links the Xiaomi (Lumi.plug) is still not supported in terms of consumption? I am using HA and while I see a consumption entity I cannot see any data in HA. I Thanks in advance guys :) |
Hi, I'm using the OSRAM Smart+plugs but Phoscon API is returning me this: (without state.power) Is there anything I can do to get state.power shown (and ultimately visible in HASS)? |
v2.05.04 should support power consumption through the Electrical Measurement cluster. A new attribute,
state.power
should appear in the/lights
resource for plugs (and lights, switches, dimmers, etc) that provide this cluster. It should report the current power consumption in Watt.I've got this working for the Heiman smart plug and OSRAM Smart+ (new) and LIGHTIFY (old) plugs. The Heiman does support attribute reporting on Active Power, but the OSRAMs don't.
Some remarks:
addLightNode()
;state.power
. It does a forced poll, after you switch the plug on or off, but if you just change the consumption of the attached device, without changingstate.on
of the plug, it might take some time beforestate.power
is updated;@manup, I'm not sure if we can support the ubisys, Xiaomi, and others, which provide the Electrical Measurement (or Analog Input) cluster on a different endpoint than the OnOff cluster. Maybe we should expose power as a ZHAPower
/sensors
resource instead, leveraging the sensor whitelist and ignoring the device type. What are your thoughts on this?The text was updated successfully, but these errors were encountered: