I know the issue still isn’t fixed, in the meantime a somewhat « hacky » solution is possible :
Sorry it’s not very in the spirit of Gladys but at the moment bandwidth is lacking on my side and I’m not the only one among the devs apparently ![]()
I know the issue still isn’t fixed, in the meantime a somewhat « hacky » solution is possible :
Sorry it’s not very in the spirit of Gladys but at the moment bandwidth is lacking on my side and I’m not the only one among the devs apparently ![]()
Good evening, @Sescandell
To help troubleshoot, @Terdious guided me through reinstalling this sensor; you’ll find that help in Terdious’s chat, where he explains from A to Z how to integrate this sensor into the Gladys database
Thanks again @Terdious
I just realized the message is a bit old, but for anyone who comes across it, they’ll find a solution while waiting for the bug fix
Hello everyone!
I opened a PR to address this issue on the Gladys side while waiting for some movement on the Zigbee2mqtt side regarding this duplicated-feature issue.
@cicoub13 @AlexTrovato If you have 2 minutes to give me a quick review I’d appreciate it!
Hi, that looks OK to me, but a reduce might be a bit heavy (I haven’t benchmarked).
Otherwise, you need to make a dictionary per externalId
Given the maximum number of features per device (50-100 max I’d say), I don’t think it makes a difference (reduce vs dictionary)