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

[question] Aeon Labs Home Energy Meter G2 to much information #232

Closed
haavardNO opened this issue Jan 13, 2021 · 6 comments
Closed

[question] Aeon Labs Home Energy Meter G2 to much information #232

haavardNO opened this issue Jan 13, 2021 · 6 comments
Assignees
Labels
question Further information is requested

Comments

@haavardNO
Copy link

One of the devices I have added recently is a Home energy meter.
I have used this device in my previous HA application (Indigo for mac) and zwave2mqtt. On both platforms the sensors made sense. But when added to zwavejs2mqtt there is a lot of sensors that I have never seen before. Like previous values and delta time etc... I sort of just want the energy readings. When created in Home Assistant it creates so long names that it is difficult to make out what is what.

Is it supose to be like this, or is there something faulty with the way zwavejs2mqtt is reading it?
Skjermbilde 2021-01-13 kl  18 11 53

@haavardNO haavardNO added the question Further information is requested label Jan 13, 2021
@robertsLando
Copy link
Member

@haavardNO Could you show me the names you are getting? Have you tried to set a custom entity name? @billiaz

@Swiftnesses
Copy link

Swiftnesses commented Jan 13, 2021

I get this with my Aeon plug, the previous value is required to store the value when you reset values (the button in your screenshot), the delta entities can just be hidden / disabled (either in the zwavejs side, or the Home Assistant side).

@haavardNO
Copy link
Author

@robertsLando no I have set a name and location in the zwavejs2mqtt UI, and I have changed the name in HA afterwards. But it is pain to find the device that gives the correct value since there is so many. This metering device has one clamp. This generates 21 devices. The other metering device I use has 3 clamps, that device generates 36 devices. I guess I can tweak it to figure out what is what.
Skjermbilde 2021-01-13 kl  20 35 22
Skjermbilde 2021-01-13 kl  20 40 12
Skjermbilde 2021-01-13 kl  20 41 03

@robertsLando
Copy link
Member

I think I need to configure a way to skeep discovery for some values. @billiaz I think that in case of meter CC some values should be skipped, then we could also provide a way to ignore the discovery of some specific values using the gateway values table

@varet80
Copy link
Collaborator

varet80 commented Jan 14, 2021

i found a nice way to do this. I will also add the pr here.

@varet80
Copy link
Collaborator

varet80 commented Jan 14, 2021

Made a small patch: #237

robertsLando added a commit that referenced this issue Jan 15, 2021
robertsLando added a commit that referenced this issue Jan 21, 2021
* fix: sanitize slash in properties

* fix: better id sanification

* fix: lint errors

* fix: other lint errors

* fix: usage of propertyKey/name

Fixes #239 #232

* fix: joinProps helper and sanitize object id

* fix: move sanitifaction methods to utils

* fix: lint issues

* fix: sanification of numbers

* fix: typo

* fix: remove meter type from meters object id

* fix: add missing toLowerCase

* fix: add missing toLowerCase

* fix: lint issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants