-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
[device support] Frient EMIZB-141 #813
Comments
Apologies - I thought it was supported |
It is. As indicated on the page you refer to, battery information should be available. If I understood your message correctly though, you are requesting additional new functionality. |
:-) I just imagined that if it was supported, that it should report power and energy as well as battery? or am I missing something? |
Does it anywhere say on the page you linked that it provides a service/characteristic for that kind of information? It does not, because such a service does not exist in HomeKit itself and because I haven't implemented the custom service and characteristics from Eve. |
OK - I read the page wrong - the exposes section lists the info that zigbee2mqtt supports. Thanks for clarifing. |
It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions! |
Is there an existing issue for this?
Describe the bug
The Frient power meter EMIZB-141 that I have is supported and working in zigbee2mqtt, but only exposes a battery in homebridge I think - see logs below.
Any ideas?
Related devices
No response
Related Devices
No response
Steps To Reproduce
No response
Expected behavior
I would expect power, battery and energy to show up.
Device entry
No response
Status update
No response
Messages from this plugin
This plugin
v1.9.3
Homebridge
1.7.0
Zigbee2MQTT
1.34.0
Homebridge Config UI X (if applicable)
v4.55.1
The text was updated successfully, but these errors were encountered: