Great!!
OK, so I’ll fix that too!! Still the problem on Chrome as well!! But not on Firefox and yet I’ve tested everything: zoom / unzoom / page enlargement / page reduction / mobile version!! It’s perfect on Firefox!!!
Worse, Chrome loses access to the signal quality icons!!
I searched for an hour before I noticed!!No, I didn’t have any surprises in Discover. And I only have the thermostat for now.
Hi @PhilippeMA, if you have a bit of time I’d appreciate it if you could try again — in the end it wasn’t much to add to include the unsupported devices, and it will allow prioritization according to demand / issue
Okay, sorry for the inconvenience then, that’s normal!! ^^
Thanks again!!
Did you add handling for unmanaged devices?
With an image and a note specifying that they are not yet supported in Gladys?
Yes, that’s it!! And, like Philips Hue, a direct link to a GitHub issue!!
No image for the moment (because I’m not supposed to know ^^ even though I almost do ^^) … It lets me see, notably, that all my valves are not up to date …
And when clicking on the redirect button:
You did a good job anyway!
Looks like you’ve got some NetAtmo gear
Thanks a lot!! That’s nice!! Let’s hope the code quality is up to par too ^^ We’ll see that when we get back. The tests are finishing!
Yes ^^ On the Netatmo side, I think I have everything ^^ Once launched, it should come together quickly!!
This is starting to add up to a hefty sum.
86% coverage!! We’re almost there!! It’s coming along. I hoped to finish tonight… but tomorrow is the last one before the holidays!! Really can’t wait!!
I just noticed something about the thermostat component regarding its width.
Below is a screenshot of one of my dashboards
If you look the thermostat in the living room doesn’t have the same width as the ones above.
Even though the name is identical.
I ran tests and the width also depends on the length of the name of the line just above
If I reduce the size of the temperature sensor name the thermostat’s width increases
And if I reduce it further I get the same width as the ones above
When I look again at the dashboard I created for Netatmo and see the size of the name on the line above the thermostat I now understand why the value is getting cut off.
So the bug comes from the thermostat. @pierre-gilles we have a bug — I’ll open a GitHub issue.
Well spotted!! What’s crazy is that I couldn’t reproduce it on Firefox even though the names are the same!! ^^
Thanks so much for the tests!! I’m almost done ^^ just a few small subtleties here and there ^^
Thanks @_Will_71!!
Oh !! Yes !!
@pierre-gilles, I think I’m ready for a first review when you get back from vacation …
Happy holidays to everyone. As for me, I’m hitting the road tonight for the mountains ^^
Edit: For now, I just need to get back to the documentation!!
Edit 2: Since continuing to write tests caused me to modify/improve the code, I updated the test image for those who might have the courage to test again. Ready in about 1 hour.
Thank you very much in advance.
For your playlist 
Here we go!! Resuming the documentation ^^
@Tlse-vins, do I need to take anything into consideration?
The first part is up to you to explain the integration as thoroughly as possible and what needs to be done to connect, …
The second part, you can reuse the section of the Sonos documentation to integrate the widget.
Same screenshot, same sentence, same closing sentence, …
I’ll do a test during my vacation.
I tried your new image. No issues on my end.
Here’s a recap of the different scenarios for the thermostat width problem
So the width depends on the thermostat name (makes sense) but also on the name of what comes before and after the thermostat.
I think you meant “nothing to report” (RAS) and not “reset to zero” (RAZ)? 
Yes, it’s true, you’re right 
I think it’s time to take a vacation
Edit: so I fixed it.
