I’m confused as to what the difference is between the darksky platform and the darksky sensor. Is the sensor eventually being migrated to a platform and 0.61 is just an in-between phase? Is there a benefit to one over another?
What about using pieces of the platform within a view or card? I tried using weather.dark_sky.daily_forecast_summary in a view but it did not like that.
Those are attributes of the entity (weather.dark_sky), there are many ways to interact with that but not how you have it listed. To display in the front end you may want to read up on it here.
At the list at the bottom? It shows daily_forecast_summary as an attribute, but when I try to display that with weather.dark_sky.daily_forecast_summary, weather.dark_sky.attributes.daily_forecast_summary, or weather.dark_sky.attributes["daily_forecast_summary"] I get an invalid entity ID error.
(EDIT: Use the developer tool for templates to play around with this, it makes it easier to see what needs to go in the config)
For the ecobee (I haven’t loaded up the dark_sky one since I use the sensors) I use
{{states.weather.bigbee.attributes}}
and it will return a json object and if you look you see the first item is “forecast”, which if i add .forecast to my template above I get an array (squre brackets). This tells me that I need an array indexer, which leads me to
{{states.weather.bigbee.attributes.forecast[0]}}
Which then returns another json object and I can select whichever one I want by name, for example
Can I use something like {{states.weather.bigbee.attributes.forecast[0].condition}} in a view, or would that only be usable inside something like outputting it via TTS?