I am currently continuing my work on the scene, and working on 2 new types of actions:
Get Device Value
This block retrieves the current value of a device feature to be used in the scene later. This can be used in a message block for example, to send a message « Today it is XX°C » for example, or in a condition block to choose where to continue the scenario.
This block allows you to create conditions. In short, if the conditions are validated, the rest of the scenario is executed, otherwise the scenario stops.
The latest version v4 of Gladys now includes scene management, wow, finally, thank you very much! But well, I have to admit my frustration Indeed, in the « triggers » there is not a « basic » one in my opinion: to allow an action to be triggered at a specific time (take over the capabilities of crontab?). Second point, in the actions, I can choose to turn on a light but … mine do not appear in the list, even though they appear on the dashboard Could a nice developer bring the correction that would make me happy to finally be able to use Gladys?
Interesting, what kind of lights do you have? Is it Philips Hue? The displayed devices are only the devices that are of category « light » and feature « binary ».
Hello @pierre-gilles, and thank you for your response. It’s not actually « lights » per se, but Sonoff switches that control lamps. I base my home automation on this, it’s very practical and inexpensive, and I keep all my light fixtures!
Ok, that’s why they don’t appear in the list because the list only displays devices that are declared as « lights » (Gladys can’t guess that your Sonoff switches control lamps :p)
@link39 had the same thought with his lamps connected to remote-controlled outlets, we’re discussing it here on the forum →
Hello everyone,
Following what was said about the progress,
I had issues with Codecov on the CalDAV PR. It kept returning 0% coverage, so I rebased the code with your latest changes and a new problem appears. GitHub has been waiting for the response for almost 24 hours. Would anyone have any idea what to do?
@bertrandda It’s not your fault, it’s Codecov messing up again… I thought I was done with them but still having issues… I’ll check it out when I review your PR
Thanks for your corrections and this great Caldav integration that I can’t wait to see in Gladys
Given the number of sites talking about it and the coverage on the Dark Sky website, it unfortunately doesn’t seem like an April Fool’s joke… or it’s in bad taste.
Damn it after Snips, it’s Dark Sky that’s shutting down… all we need now is for Philips and Xiaomi to close their APIs and then we’ll all cry!
After that, it’s an opportunity to see that there is another great API, openweathermap, which seems to work without an API key with a free tier more than sufficient for us (60 API calls per minute).
Has anyone created a Gladys integration to replace the DarkSky integration which is now obsolete?
@link39 (and others) You who are a Z-Wave expert, could you tell me what’s missing from Gladys 4 to be the « perfect application » for managing Z-Wave devices on the market?
I have in mind:
Editing node properties
Managing association groups
Improving the « Network » tab to better understand the performance of a Z-Wave network.
Do you see other things?
Gladys needs to be self-sufficient in terms of Z-Wave, and above all, it must work 100% of the time. I think we have all the cards in hand with v4 to have a super clean Z-Wave integration, not much is missing!
Indeed, in the « triggers » there is not a « basic » one in my opinion: to allow an action to be triggered at a specific time (take over the capabilities of crontab?). Second point, in the actions, I can choose to turn on a light but … mine do not appear in the list, even though they appear on the dashboard 
Could a nice developer bring the correction that would make me happy to finally be able to use Gladys? 
I’ll check it out when I review your PR 