-
Notifications
You must be signed in to change notification settings - Fork 510
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
Smartenit ZBMLC30 ?? #792
Comments
Best information are provided by screenshots from the node endpoints and Cluster Info Panel of basic cluster after reading its attributes. Also Screenshot of Node Info Panel. |
Thanks for the details, with the above screenshots we can add the power readings via Simple Metering cluster or at least start to whitelist them. |
<Thanks for the details, with the above screenshots we can add the power readings via Simple Metering cluster or at least start to whitelist them.> Simple metering is all I should need watts would be best followed by amperes or lastly KWH.. Watts because it should be a good size number and should be quick.. |
The Simple Metering cluster usually only reports life-time consumption (kWh), and sometimes current power (W). Try reading the cluster in the deCONZ GUI: Current Summation Delivered (0x0000) is the life-time consumption; Instanteneous demand (0x0400) the current power. The scale typically differs per device, and only a few devices support the formatting attributes. For voltage (V), current (A), and sometimes frequency (Hz), you'd need a Electrical Measurement cluster (0x0B04). This cluster also contains power (W). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
What information would I need to get to you so you can add this device.. It presently shows up as a light {I'm a NOOB so it maybe just installed incorrectly } and it does switch on and off , but I beleave it can also supply power readings... Thank You.
The text was updated successfully, but these errors were encountered: