2020.12: Automate with Blueprints!

You’re homing in on my experience level :slight_smile:

Updated HA to 2020.12.1, still not Denon fix. GitHub said fix was merged.

Three sites all with Denon’s, now need to learn to to restore 118.5, do have backups.

i cant see anything Denon related in that version

2020.12.1

@balloob balloob released this 7 hours ago

Just load the Denon component as a custom from 118.5, that should work too

Updated to latest version, whats happened to the history and the log book functions ? Now have to select individual entity ? any way you can switch it to view all entities like previously ?

Also Nest integration works but when you try to view history of temperature, just shows flat line ?

After some time it was fixed by itself.

Mine still work just like before, it list all entities.

It’s merged to the dev branch, not yet added to a release. Hopefully it’s added to the next minor update (2020.12.2 - to be released Dec 23) according to this.

ahh ok cheers Jody, obviously mine has some issue then, will have a look through the logs when i get home,only thing i can see quickly from the app is HACS is showing up as waiting for Homeassistant to finish start up

Will area_id be ever available as entity attribute? i.e. to use in templates? My use case would be smoke and water leaks alarms notifications in multiple house areas.

Can i upgrade docker on my ubuntu supervised to 5.20.10 after the last upgrade of supervisor?

This might not help you much … but I just deleted my scripted Twinkly integration to move to this official one and it worked fine for me when I added it via the UI.
So it is not a 100% broken thing.

Your use case makes sense but I feel like an attribute would be inefficient. A device’s area is a constant, it’s set as part of config and doesn’t change with the state of the device. So to make it an attribute you’d have to copy that value into each and every state change event for all entities of that device. And it would get even worse if they ever added area grouping since then a device and it’s entities could be in multiple areas.

I think instead what would be better is a device filter so you could get to associated device data from an entity or entity id. And then an area filter to get to associated area information from a device or device id. Then you could use that info in templates without adding it to all state changed events.

Either way I’d suggest making a feature request if you haven’t already as this is kind of buried. Could also bring it up on discord to get people’s thoughts on it.

The 2020.12 update on my Pi 3B broke things thoroughly. I’ve managed to restore to 0.118.4 but for some reason the system now thinks that rather than it being 1902 on the 17th December it is 1111 on the 13th September. That in turn is I think creating other problems. How can I force an update or otherwise correct the date and time? I am back up with SSH access but at a loss to know what commands to run.

This update broke my Velux KIX 300 (homekit controller) integration.
While all the sensors (CO2, humidity, temperature) and blinds work correctly, the windows have disappeared! They are shown as unavailable. I tried deleting and re-pairing the gateway but then the window devices are created but there are no entities attached to them!
I downgraded back to 0.118 and they work correctly again.
Any advice??

Thanks in advance.

A pi does not have a real time clock. It gets time from an ntp server on them intarwebs at startup. If it is showing the wrong time, it probably isn’t connected go the internet.

Thanks. But surely as I can see 2020.12.1 is now available in the supervisor dashboard it is connected to the internet? Is there a way to prompt it to reconnect to an ntp server and update whatever is keeping track of time and date?

Sorted with the Chrony add on. Still don’t understand what’s happened but at least a step closer to being back up and running.

1 Like

What happens, if nobody updates to x.x.0 and follows your suggestion ? :wink:
By the way: I wait at least for x.x.1 as well :relaxed:

Same here - worked great here. Updated HA to 2020.12.1 then got promted to upgrade HACS to 1.9…