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
Hello,
Following the last call to the community, I bought the Lixee module. I’m on single-phase, with an off-peak/peak (HC/HP) tariff, but it seems the data aren’t coming through on my end…
Any idea what’s wrong? Has anyone seen this behavior before?
Are you sure you’re in standard mode?
Also, did you reconfigure the module after changing the options?
I also removed the Relay; I don’t know what that corresponds to ![]()
Ah, damn, good catch — I was in historical mode ![]()
But I didn’t understand the reconfiguration thing — what does that refer to?
Basically, a restart of the device is needed to apply the settings.
For historical mode, the information is in other « expose ».
That corresponds to what you have on your meter.
To switch to standard mode, you can request it from your energy supplier.
Indeed, after a reboot and removing the filters it seems to work much better, looking forward to the integration on the Gladys side, thanks for the work and the advice!
[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?