For the last few days now (around 0.92.x), something is killing my instance of HA. I have a script that runs when the alarm is set and that code is below.
## Turn on radio in rumpus and ensuite when alarm sets ##
- alias: 'Turn on radio when alarm is armed'
initial_state: true
hide_entity: true
trigger:
platform: state
entity_id: alarm_control_panel.home_alarm
to: 'armed_away'
## script in scripts folder [radio_alarm.yaml] ##
action:
- service: script.turn_on
entity_id: script.radio_alarm
## Turn off radio in rumpus and ensuite when alarm unsets ##
- alias: 'Turn off radio when alarm is unset'
initial_state: true
hide_entity: true
trigger:
platform: state
entity_id: alarm_control_panel.home_alarm
to: 'disarmed'
action:
- service: media_player.volume_set
data:
entity_id:
- media_player.insignia_speaker
- media_player.ensuite_speaker
- media_player.bathroom_speaker
volume_level: '0.50'
- service: media_player.media_stop
entity_id:
- media_player.insignia_speaker
- media_player.ensuite_speaker
- media_player.bathroom_speaker
Lately though, again around 0.92.x, that radio is not stopping when the alarm is unset and when that happens, HA becomes unresponsive on the frontend although SSH and Samba still work. When itâs in this state, no automations work so it well and truly dies. The only way to recover it is to do a host reboot.
I ran hassio ha logs and got the following:
/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py:847: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecureRequestWarning)
There have been changes made to media_player in 0.92.x. Maybe one of them affects your system.
Hereâs one but there are others:
media_player - The media_player component will now guard against calling services that are not supported by the entity. This means that if you attempt to invoke media_player.turn_on , but the entity does not indicate it can be turned on through supported_features , the service will not be called and will not log any message. This is a breaking change as in the past it would have called the turn_on implementation. There may be platforms that do not properly set supported_features which may result in service calls not being invoked where they would have previously.(@andrewsayre - #22878) (media_player docs)
Thanks. I think Iâve found it? When we go out and set the alarm, we often leave the property via a gate to the beach that Iâve wired with a xiaomi door sensor. This both notifies our Google homes that the gate opened and also turns my PTZ towards the gate for 10s and take a camera snapshot.
The PTZ presets are defined in a bunch of shell commands that are no longer working and kill HA when invoked. Iâll roll back to 0.91.4 and try again.
interesting post you made. I am experiencing something that might just be related. Weâve installed a few Google Homes lately, and are still learning to use them⊠One of the things we do wrong is ask Google to âturn of light so and soâ and because of misunderstanding, Google Home turns off all lights⊠which is annoying of course, since most of them are set to a dedicated setting, so its a real pain to have that back up and running.
But, and here comes the related issue: if that happens, my Ikea lights are no longer controllable in the HA frontend. Something kills the connection between Ikea and HA. I have to restart HA to get things back up and connected again.
Secondly, I experience never before experienced Ikea hub Offliners⊠Could Google home integration in HA have anything to do with this? Donât receive errors as far as I see, but the Google Home installation in our setup seems to have caused unexpected side effectsâŠ
btw what do you mean by:
Does it give you a TTS message then, or is there a specific meaning to notifying Google Home?
thks!
Ensure each Google Home is set to the right language.
Ensure you give your devices unique names that donât rhyme with âallâ like âhallâ. Otherwise, saying turn off hall lights can be mistaken for turn off all lights. So hall might become foyer?
Look for language anomalies. My Googles are set to Australian but in NZ we say âpoolâ quite differently to how they say it in Aussie. So âturn on pool lightâ becomes âturn on outside lightâ to avoid any confusion.
In regards TTS, I find this to be the most valuable part of HA. When events happen in the house, HA sends a voice message to all five Google Homes. I have things like;
âThe courtyard gate just openedâ
âWelcome home Davidâ
âThe garage door was left open so I just closed itâ
âThe washing machine has finishedâ
My wife laughed when the last one went off for the first time but now she loves it!