Lol ok, will be hard.
There is an issue opened on a jeedom forum ?
But if it s from deconz, we should have more return than that, for me there is something new in the code that panic the jeedom plugin, but I realy don’t see what is new on the last version, too much changes, and I don’t see something in rapport with notifiations.
Someone have an idea on github.
Can be a power measurement device that not working previously, that was enabled on the last version ? (or set with lower reporting values)
Can you disable some sensor in jeedom ? (and let them in the network ofc)
How do you disable the sensor ?
Are you sure jeedom don’t write some information on SQL database, when it receive notifications ?
All your plugs are used as routers ? You can unplug at least one of them ?
IDK how work the jeedom plugin, but from my memory it is python, you can ask to devs if you can edit a line for the plugin ignore some device (the ZHAPower and ZHAConsumption) to test ?
And for the moment, even with the GUI, it s hard to change the reporting values, so on jeedom without the GUI …
Sorry I m a little busied ATM, but I will install the last version this WE to compare too.
Ok so for information I m ATM on deconz 2.12.0 on a dev network with some various devices
Have started to count all websocket event at 2021-09-03 20:29:02.244
In 24h I will install the version v2.12.6 to compare.
Hopping for the change have not happen before the version 2.12.0 …
deconz 2.12.0
Starting at 2021-09-03 20:29:02, finished at 2021-09-04 20:34:03 > Websocket count : 14 700
deconz 2.12.6
Starting at 2021-09-04 20:34:03 finished at 2021-09-05 19:27:50 > Websocket count : 19 100
(for 23 h so will take 19 920 for 24h)
So for the same network with only 15 nodes, the version 2.12.6 have 30% mores notifications.
We are far away from your 300% increase IO, but I can’t explain it (if someone have an idea ?), and it can depend of devices in the network.
Jeedom devs have found something ? On my side I m using filtering on websocket notifications, I check the device, if the state is the same, I give up the notification, I give up too all “attr” notifications.
I have some personal problem ATM, so not a lot of time, but Tomorrow, I will make a code with more statistics, useless notification/usefull notification/ignored one, ect …
Because I don’t think 15 devices need 20k notification to update their states on a complete day. I think the solution is on the filtering.
Thank you for your reply!
I’ve no news from geekdom developers unfortunately. Do you want the link to jeedom discord subject ?
You have 30% more notification. I’ve jeedom and deconz on the same virtual machine so 30% * 2 and maybe more if jeedom made some treatment if the value are the same.