Updating Alexa Media Player in HACS to v3.10.15 solved the notify issue for both it and Pushover…
And strangely, Restart Home Assistant is now working…
Wonderful release, as always. 
Thanks to everybody for all your hard work!!
I’ve ran into an issue with an “Times of the day”-binary-sensor and am wondering, if anyone else can confirm. Here’s my config:
- platform: tod
name: is_night
after: sunset
before: sunrise
Last night, the sensor wasn’t on as it always has been before the update. Have I overlooked some breaking change maybe?
This menu item is removed
I got this issue and it was because I was using Ethernet instead of WiFi on the Powerwall.
Thank you for pointing that out!! It’s now added and positioned in the middle of my side panel so I can always get to it quickly!
Not sure about real official source, we also had with custom component and it’s small adjustment
I did not know about that platform! I just added it and it’s working for me…
My config is segregated but…
configuration.yaml
binary_sensor: !include binary_sensors.yaml
binary_sensors.yaml
- platform: tod
name: Early Morning
after: sunrise
after_offset: "-02:00"
before: "09:00"
- platform: tod
name: Late Morning
after: "10:00"
before: "12:00"
- platform: tod
name: Night
after: sunset
before: sunrise
Thanks for checking! Perhaps I just set a second one up to test.
taking occasion after seeing you are talking about it. Mentioned by you settings has to be set for each device separately. Also each user has to set it on his own.
I suspect it was the easiest way to program, but it starts to be suboptimal while having more users. Asking every user for access to his/her mobile device is hmm awkward.
Don’t you know managing this option centrally by admin for all users regardless a device is under consideration?
Maybe there is some discussion I missed
2 Likes
Remove the alexa_media custom component and then the upgrade will work, I had the exact same issue and reported it on git hub. The log files don’t actually indicate this but it fixed my upgrade issue.
1 Like
It looks like you aren’t using the built-in rest integration, you’ve overridden it by copying the files into your custom_components folder and there have been changes since you’ve done this which mean your version is not compatible with 2021.12.
You either need to remove your custom version or update it to match the latest code in the official version.
Just wanted to say that I really like the new Hue integration. Enormous speed! Great!
1 Like
No, reverted to the previous version of HA. 
That sounds logical - and it was the crucial clue. Thanks very much!
That was a VERY BAD idea to move from this menu:
[…]
to this menu:
Fortunately, last week I just built a development dashboard in the style of the old settings page. 
Lucky me.
2 Likes
[about Customizing entities tab in configuration]
Release notes mention a revamp. I was not aware that revamp remove functionnality.
It’s a strange situation now because change made previously can’t be edited.
I don’t find a way to re-customize entities that I touched earlier.
Why this has been removed ?
To have had this option in the UI previously, you must have included a customize: section in your main config.yaml at some point. It’s common practice to put an !include here to keep all customisations in a separate file e.g. !include customize.yaml
I think any customisations you made should be saved there (not 100% sure on this to be honest), but you should be able to edit this file for future customisations. Full documentation here. [This would only apply to entities without a unique id that you can’t already change through the UI.]
Well duh, but the docs didn’t say anything about unsupported. I was trying to clarify if the device had an error mid way through the process and resulted in the word unsupported in the UI. Turns out I was right on that bit.
Because customizations are implemented on the entity now and everything is moving that direction. The customize UI was a temporary solution a number of years back, the temporary solutions time ran out. You can still customize entities by going to the entity in the entities page. If you need to customize a yaml entity (Entity without a unique_id) then you need to customize it in Yaml.
Check the supervisor logs. Is your system healthy?