Skip to content
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

improve power meter #1197

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from
Draft

improve power meter #1197

wants to merge 6 commits into from

Conversation

timoschilling
Copy link
Collaborator

No description provided.

@timoschilling
Copy link
Collaborator Author

Here is a pre-release build with the changes from this PR. Would be cool to get some feedback.
Note: From my point of view the Eve app is rounding current power consumption to an int value, in other HomeKit apps I can see float values with this firmware.

shelly-homekit-ShellyPlus1PM.zip
shelly-homekit-ShellyPlugS.zip
shelly-homekit-ShellyPlug.zip
shelly-homekit-Shelly25.zip
shelly-homekit-Shelly1PM.zip

Please leave a note if I missed a device with power management.

// cc rs38

@5xPa
Copy link

5xPa commented Jan 22, 2023 via email

@timoschilling
Copy link
Collaborator Author

@5xPa what Shelly do you use?

@5xPa
Copy link

5xPa commented Jan 22, 2023 via email

@rs38
Copy link

rs38 commented Feb 4, 2023

sorry for answering so late,

your provided prereleases has the same version as the old
Version:2.11.2 that was a bit confusing.
After a 2nd try it updates to
Build:20230119-205815/2.11.2-17-gf6ac761-master

the local UI now shows 1 decimal but the HK or Eve still show an Integer.
IOS 16.3 HK shortcut same as #1194
(Eve however always shows integers)

@rs38
Copy link

rs38 commented Feb 4, 2023

Test with a LED lamp dimmable 0-8W:

should also add that in my case the consumption shown in the local UI (of a LED lamp dimmable 0-6W) is obviously skipping all decimals other than x.1 and x.0 and the original shelly firmware shows kind of random fake or "noise" decimals and the internal resolution of the sensor is obviously only ~1W.
Therefor is simply makes no sense for more than an integer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants