I have an Off-peak Evening and Weekend subscription and the Weekend HC data is not being reported to Gladys.
I created a PR to add this EASF03 data.
I also took the opportunity to fix the display of the icon and text for the RELAIS expose because nothing was showing.
However, I have a question about whether we could improve the display of the features, because for example there are a lot of indexes, intensity, power but we don’t really know what they correspond to! Without opening the zigbee2mqtt page it’s impossible to know which is which…
See below.
This is what I would like to do:
2 Likes
Thanks for the PR @_Will_71, it’s merged and it will be included in the next Gladys release 
That would be really great, yes! How would you like to go about it? Create features specific to the Lixee TIC?
In my view, yes, because with generics, when we end up with several identical functionalities I find it difficult to know which is which
If you have other ideas, I’m open to suggestions.
No, I think it’s fine to create very specific features in some cases like this, at least we can offer a more precise experience
I would suggest something, but where I’d be less sure is the German translations.
I will use online tools to translate, but I don’t yet
ChatGPT @_Will_71 for translation, much more effective than Google Translate or others.
It seems that Pierre-Gilles uses it as well.
2 Likes
Thanks for the advice @Terdious,
1 Like
Yes, I take the JSON in French, paste it, and ask to translate it into English and German:
it takes 10 seconds 
2 Likes
Ok, I’ll do that, thanks.
I just tried it and it’s clear that it’s effective. Thanks for the advice!
2 Likes
@pierre-gilles the PR with the specific features
1 Like
Thanks @_Will_71! Great job Did you test it?
And is it backward compatible? If someone runs this version of Gladys while they already have a Lixee, will it break or will it work?
I ran real-world tests with my LIxee TIC but I added it to my new instance for testing.
I’ll run another
@pierre-gilles, I just ran a test and indeed it breaks things a bit. The only remaining feature is the one about signal strength that I didn’t modify.
I saw migration files, I think I need to do that to provide a migration from the old features to the new ones.
I’ll take a look over the weekend at what I can do.
Edit: it breaks everything, no it’s just the display on the dashboard
1 Like
@_Will_71 I’m closing this thread because the EASF03 data has been added to Gladys Assistant 4.47.0:
Shall we discuss it in another thread in Développement?