-
Notifications
You must be signed in to change notification settings - Fork 21
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
Increase default reporting frequency for LiXee ZLinky_TIC Smartenergysummation #116
Comments
There aren't no default reporting in ZLinky at the begining. That is the coordinator accros a plugin/box which send config report to the ZLinky. I think for this value It's ZHA which send a default config report with a low frequency |
Thank you for clarifying. It would probably be a good idea to set one; that's not an issue I've had with any other device, including connected plugs, etc. On the other hand, it's OK to leave it like that, as long as it's documented, IMO. |
Hi, It doesn't work for me, any idea why ? my log:
Thanks ! |
@Ozaroth did you change some options? I see "expect_reply", "read_before_write", "max_interval" among others, that I didn't specify when doing this. |
@MayeulC only the max_interval. service: zha_toolkit.conf_report and the result :
|
Hi, max_interval must be greater than 60 for reporting |
Thank you @fairecasoimeme it's working ! |
Hi, the conf_report seems to works, but active_power does not come more frequently service: zha_toolkit.conf_report
data:
ieee: 00:15:8d:00:05:ce:77:e0
cluster: 2820
attribute: 1291
min_interval: 10
max_interval: 61
reportable_change: 1
event_done: zha_done
service: zha_toolkit.conf_report_read
data:
ieee: 00:15:8d:00:05:ce:77:e0
cluster: 2820
attribute: 1291
any idea ? |
Thanks @MayeulC , you're a life saver ! I had to migrate to ZHA yesterday, because my integration in deCONZ was also failing after 1 day.. |
Hi @bachy, did you find an answer to your questions, by any chance? Thanks in advance |
Hi @nerthazrim No i never get to make it work. |
That cluster (CCASN, 2820/1291 aka b04/50b) sounds a bit weird:
And it's only available in standard mode. Are you sure it's the right one? I suggest you try to read a clister from the UI on the device page to confirm it returns a value, and the right one, before configuring the reporting period. Maybe you are looking for Edit: with PAPP, it should be: service: zha_toolkit.conf_report
data:
ieee: sensor.lixee_zlinky_tic_electricalmeasurement
cluster: 2820
attribute: 1295
max_interval: 200
reportable_change: 5
min_interval: 40 Notice how I replaced 1291 with 1295. I am a bit confused though, as when I perform a read from the interface, Of course, another option is to differentiate the energy, as E=P*t -> P=E/t (dE/dt, the derivative, is more technically correct). E in joules (=1 W.s), t in seconds, P in watts. |
Hi @Ozaroth, would you mind sharing the conf snippet you're using, please? :) |
Hi @nerthazrim you want my conf for active_power ? |
I'll open a ticket with in the ZHA project. I guess that's the way to go. |
Well, actually, quick one for you @fairecasoimeme: we can read here (on a similar issue)
Would it be possible that the ZLinky does not advertise properly a change in the "active_power" value to ZHA? Which then does not record a new value? |
The device pushes updates, but the coordinator can configure how often, which is what Edit: though the thread linked was for a Shelly product which uses Wi-Fi/Bluetooth/Ethernet, not Zigbee, so it's a bit different. |
Default reporting frequency is very slow. It's possible to increase it via ZHA Toolkit though:
Dev tools -> Service -> yaml mode
This configures the device to an arbitrary min reporting period of 40s, max of 200s, and min change of 1Wh. It would be nice to have it by default in the FW.
(Originally posted in #18 (comment))
The difference is pretty clear:
I am currently on FW v9, but the issue was present before as well v5, as well as the shipped version.
Related issues: #65 with @pipiche38 and @Tof-le-Chauve. Maybe @pdecat too from #19
The text was updated successfully, but these errors were encountered: