0.95: AdGuard, Life360, Plaato Airlock

Blog
11

I had no idea about the A1 and A2 ratings for SD cards. I checked the card I just bought for my Pi 4 and it’s A1 so I’m good. Still going to move the db off the SD card to extend its life though

12

Looks like the “breaking changes” section has reverted to the old fairly vague descriptions.

What exactly does “Restore automation last_triggered with initial_state override” mean?

What does it break?

the link to the docs included in the breaking change entry doesn’t really give any info on this either.

13

I had the same issue that bt stopped working.
Backed up config and reinstalled, suddenly came back.

14

This usually means that if you’re using SSL, someone is connecting to Home Assistant using http://, or the other way around.

15

The person who usually contributes these is on holiday. Extended breaking changes are available in the PRs linked from the vague descriptions. Source of the blog post is here. Contributions to bring them to the blog post are welcome.

1 Like
16

If you would be interested in bringing USB boot (so we could use an external SSD, say to run Hass.os from), please consider supporting this feature request:

If you too would like to see SSD bootable Hass.os drives, please support the Feature Requesrt by voting for it.
I’m hoping it might be possible, @balloob ?

2 Likes
17

already done :slight_smile:

Kinda two fold though, I am also hanging out for the Pi 4 image too.

1 Like
18

Yeah, there’s something wrong with it. All of a sudden BT devices stopped working for me as well. However in my case disconnecting BT dongle and reconnecting it + HA restart helped

19

THANK franks

for adGuard

Been watching you channel

JOB WELL DONE :beers:

20 

Testing configuration at /home/homeassistant/.homeassistant/.
Failed config
  General Errors: 
    - Platform not found: tts.google_cloud

Successful config (partial)

won’t work for me :frowning:

21

Same for me

22

what did you reinstall? docker? or HA?

23

To be clear about my circumstances.
I reinstalled hassio, I run on a pi3.

24

oh right I see

25

Have may errors as below


2019-06-27 10:18:31 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/esphome/__init__.py", line 171, in complete_setup
    infos, services = await entry_data.async_load_from_store()
  File "/usr/src/homeassistant/homeassistant/components/esphome/entry_data.py", line 76, in async_load_from_store
    **restored.pop('device_info'))
  File "/usr/src/homeassistant/homeassistant/components/esphome/entry_data.py", line 106, in _attr_obj_from_dict
    return cls(**{key: kwargs[key] for key in attr.fields_dict(cls)
TypeError: __init__() missing 1 required positional argument: 'esphome_core_version'
2019-06-27 10:18:31 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/esphome/__init__.py", line 171, in complete_setup
    infos, services = await entry_data.async_load_from_store()
  File "/usr/src/homeassistant/homeassistant/components/esphome/entry_data.py", line 76, in async_load_from_store
    **restored.pop('device_info'))
  File "/usr/src/homeassistant/homeassistant/components/esphome/entry_data.py", line 106, in _attr_obj_from_dict
    return cls(**{key: kwargs[key] for key in attr.fields_dict(cls)
TypeError: __init__() missing 1 required positional argument: 'esphome_core_version'
All my ESPhome devices are not integrated
26

My ESPhome appears all funcioning and listed after the update, what version of ESPhome are you using?

28

same for me (after re-install HA to get it launch without error)

29

@finity
That’s the fix frenck mentioned in this post (you’ll remember it when you read it).

For all other readers who may be unfamiliar with this issue, I had identified a negative side-effect of using initial_state: true in this post. Someone’s automation was occasionally failing and it was due to the last_triggered property sometimes failing to contain a value.

I discovered that when you add initial_state: true to an automation, upon restart the automation’s last_triggered property is reset (i.e. set to ‘None’). Any templates you may have that perform calculations with this property will be negatively affected after a restart.

I mentioned this observation in another thread:

RE: initial_state
What it does is it overrides Home Assistant’s restore feature. It also resets an automation’s last_triggered attribute after each restart (you lose the record of the last time the automation was triggered).

I intended to update the documentation to mention this side-effect. The issue came to the attention of frenck who proceeded to implement three corrections:

  1. Fix the bug with Home Assistant’s restoration feature that was causing people to use initial_state: true beyond what it was originally intended for (implemented in 0.94.1 by baloob via PR 24390).
  2. Fix the bug that caused an automation’s last_triggered to be reset on startup if the automation used initial_state. This was deemed to be entirely new behavior and so is considered to be a ‘breaking change’ and the fix was relegated to a major release version (0.95).
  3. Corrected the documentation.
2 Likes
30

aarch64 docker image is still 0.95.0b1

31

Same error after a re-install too :frowning: