Hi everyone!
I’m hosting a live coding session this afternoon at 2:00 PM 
I’ll develop an integration with the EDF Tempo API to allow Gladys users to automate their smart homes based on the current and upcoming Tempo days
8 Likes
Also I invested quite a bit in new gear for the channel’s streams, it’s going to greatly improve the quality of the lives 
Dual monitor + Stream Deck, it makes it much easier to switch scenes in OBS.
And easier to see live comments!
Can’t wait to test it out later 
3 Likes
Another great live-coding session to rewatch at leisure! 
I’m coming back to the weather side that it would be nice to have in scenes to use it with Tempo EDF to have scenes like:
if « tempo-edf tomorrow = red day » and « weather tomorrow = bad » then « increase today’s heating setpoint by 1° » or « start the washing machine today » etc
if « tempo-edf current = blue day » and « weather today = sunny » then « start the washing machine » etc
Then we need to see if it’s possible with the information sent by OpenWeather in Gladys!
Thanks @cce66 The replay is available at the same link!
As always → Feature request to see if there isn’t already one
1 Like
Can’t wait to test this, looking forward to the next release. I’ll be able to remove what I had set up via Node-RED 
3 Likes
The development PR is available on GitHub:
I’ve added an interval to refresh the data every 2 hours on the widget.
It will make it into Gladys
2 Likes
@pierre-gilles The refresh every 2 hours is to prevent the displayed data from becoming outdated if we stay on the same dashboard without manually refreshing, right?
If that’s the case, I would also add a systematic refresh at 0:00, 6:00, 11:00 and 22:00 (which are the times when any of the ‹ couleur J › or ‹ couleur J+1 › or ‹ HP/HC › info is likely to change). Otherwise, if I displayed my dashboard at 10:45, it would show incorrect information from 11:00 until 12:45 (next refresh after 2 hours).
What do you think?
You’re right, I’ll change the refresh, but I won’t set up a trigger at a scheduled time; I’ll just make sure the « peak/off-peak hour » is calculated on the frontend, so it’s always correct!
1 Like