There’s a lot of information coming in!!!
That’s great, I can already imagine the scenes.
There’s a lot of information coming in!!!
That’s great, I can already imagine the scenes.
Awesome!
What do you still have left to do to finish integrating this Zigbee module?
Optimize !
I’m overloading my database ( it’s too verbose )
For those who already have the pairing module, I strongly recommend that you configure the TIC (teleinformation) according to your needs.
Example:
My configuration
What is exposed:
Gladys:
![image|689x
You wouldn’t have an issue with the keep history per feature and the aggregation, would you?
I’m reposting the link to the Lixee module for those who might be interested.
Not directly, it’s a bit sneakier.
At each poll and depending on the chunk, all the states are republished on MQTT, so I had 4 to 5 states per second for each feature. That doesn’t help ![]()
Ah yes, indeed ^^ So the configuration is important!!
Thanks for the advice
Ah, damn, good catch — I was in historical mode ![]()
But I didn’t understand the reconfiguration thing — what does that refer to?
[quote=« VonOx, post:44, topic:6061 »]
For those who have already paired the module
No, and that’s clearly not possible, it depends on each person’s subscription
Yes, but the famous « measurement_poll_interval » — that’s common to all installations, right?
Default is 60 seconds, I had a different value because I have the TIC before official support
Ah ok!
In that case, can you confirm that for newcomers who buy the ICT now, there shouldn’t be any problem and we shouldn’t see the excessive resource usage we saw with you?