After 2 months, it started to work.
Thanks to @TheJulianJES that implemented it on 2025.11.0
Anyone have an idea on how to reset the “Summation Delivered” every month?
There are more interesting attributes available, like the projected bill, current_day and previous_day consumption, but seems it’s not implemented yet.
My idea is once the kWh price is set, the dashboard will display the costs for the current day, the previous day, and the entire month.
Thanks
There are more interesting attributes available, like the projected bill, current_day and previous_day consumption, but seems it’s not implemented yet.
Those are standard ZCL attributes. If return None when reading, they’re not supported by the device. Otherwise, I’ll take a look at that soon as well.
I’m not sure how far the device itself would actually contribute to this.
Creating sensors for the electricity costs is something you should already be able to do easily within HA by using sensors/helpers for tracking costs.
For resetting the consumption via a button entity, I’ve put an issue to track this for myself. Then, you could automatically “press” that button once per month in an automation, for example:
Most users would not want to reset their consumption for tracking purposes though, since this is not expected for that ZCL attribute, so it can negatively impact HA’s long term statistics.
Does this also happen to you who every now and then reads values that are totally out of the ordinary?
It happens to me about 1 time a month that it also reads absorptions of over 7000w for about two minutes (my contract is for 5Kw but it can go up to 6.5Kw then turns off). So 7Kw is an impossible value without turning off everything.
It therefore doesn’t happen often but having associated automations with the exceeding of certain thresholds this is very inconvenient for me sometimes…
Maybe the reader is not very well positioned over the led, taking wrong measurements?
it’s centered… I like things done well.
If it were poorly centered the error signals would be more frequent but it happens once every month (in the recent two months). In the end I solved it by mentioning the condition “if less than 6.5kw” in this way all readings above 6.5 are not taken into consideration. I think it could be due to many factors… such as interference (even if the device is only a little more than a meter away… but it is still close to a high electrical flow)
@Skyman1 Ideally, we’d have some ZHA debug logs from when this happens exactly, but you’d get a bunch of logs after a month.
I’ve thrown together a quirk that could maybe fix this. See: Fix Frient EMI LED divisor and multiplier by TheJulianJES · Pull Request #4485 · zigpy/zha-device-handlers · GitHub
There are install instructions at the bottom. If this works, we can upstream it into ZHA (quirks) directly.
I’ve opened a PR on ZHA to support exit and entry delays.
Once this get’s merged I have a another one ready for HomeAssistant core to use it. Add Exit/Entry Delay Support for IAS ACE Alarm Panels by malywut · Pull Request #664 · zigpy/zha · GitHub
Works perfectly with my Frient keyboard
@malywut Nice! FYI, I believe to show the proof-of-concept use case even better you can go ahead and open the follow-up PR for Home Assistant’s core right away with link to upstream PR as depency and just set that core PR into a ”draft” to let other people/developers know it is still a work-in-progress and is dependent on upstream PR to first be merged + zha package updated in Home Assistant’s core to get it.
@malywut remind you to set the PR for Home Assistant’s core to ”Draft” which is something you can do yourself on GitHub:
After you convert that PR to a draft then it will clearly be marked as such making it perfectly clear to everyone that it is still a WIP.
Sorry Hedda, couldn’t resist.
7 months later, this "Works with Home Assistant" device is still not compatible with Home Assistant 
Got tired of waiting for the Intelligent Keypad to work as you would want it, so I wrote a custom quirk for it paired with an automation blueprint that makes it work seamlessly with Alarmo.
@Hman did you make a pull request for a new custom ZHA device handler or submit a device support request to the zha-device-handlers repository to mke ZHA developers aware of it?
If you do not at least report issues to the zha-device-handlers repo when ZHA devs migh miss it.
If not get merged there then each and every end-user will need to manually install it themselves.
