0.115: B-Day release! Media browser, tags, automations & WTH

mikeyb5753 · September 30, 2020, 3:32pm

Since updating to 0.115.6 my hive heating devices are unavailable but nothing in logs.

Buster · September 30, 2020, 4:23pm

Since 115.4 -115.6 Hass frontend has been stopping for some reason. I’ve been trying to track down the issue and figure out what logs I should be grabbing. I have turned on logger debug but the homeassistant logs just stop with no apparent error. This is the homeassistant docker log it just stops at 09:37 https://pastebin.com/J8SxeGp8 I’ve been looking through the other hassio docker logs and not finding much to go on.

phillprice · September 30, 2020, 5:19pm

This is due to the Hive API changing so the integration is broken unless someone can figure out how to now login with their new schema. Unfortunately it may not be possible.

SeByDocKy · September 30, 2020, 6:20pm

The 0.115.6 is eating one more time some extra Mo .(the 0.115.4/0.115.5 solved more or less the problem

nickrout · September 30, 2020, 6:44pm

Can you point to the github issue for that?

nickrout · September 30, 2020, 6:57pm

What is a Mo?

The changes from 0.115.4 to 0.115.5 were one line in a tts integration.

The changes from 0.115.5 to 0.115.6 was a change to google assistant.

These seem unlikely to render much difference, but it is if course possible. The small changes will make it easy for you to track down.

petemagnusson · October 1, 2020, 4:45am

Going from 0.115.4 to 0.115.6 i lost my Dashboards i had created, anyone ells seen this?

tom_l · October 1, 2020, 4:50am

As Nick said above .5 and .6 were very small changes to two integrations. This should have no effect on dashboards. It didn’t for me. Something else is amiss with your system.

Mariusthvdb · October 1, 2020, 7:40am

ha, we’re back to TTS issues… this template

 {{as_timestamp(now())|timestamp_custom('%d %b %X')}}

now is pronounced as

(incorrect) nul 1 o c t (correct from here) 9 hour 38 minutes and xx seconds

while being correct and unchanged in the editor,

and here since forever.

anyone else hearing this oddity?
issue filed: https://github.com/home-assistant/core/issues/40925

phillprice · October 1, 2020, 8:04am

You say that but from .5 to .6 lots of things randomly became unavailable, going back to .5 and suddenly they were back again. And yes I can see the code footprint is unrelated so there’s something odd going on.

SeByDocKy · October 1, 2020, 4:16pm

memory

Check the huge drop

nickrout · October 1, 2020, 6:09pm

You still haven’t told me what a Mo is?

123 · October 1, 2020, 6:26pm

Abbreviation of megaoctet, the French term for megabyte.

http://gdt.oqlf.gouv.qc.ca/ficheOqlf.aspx?Id_Fiche=8873683

tom_l · October 1, 2020, 7:24pm

I read that as megaocelot.

liuk4friends · October 1, 2020, 8:28pm

Hi there,
Since updating to 0.115.6, my ‘Netatmo weather station’ sensors became unavailable.
I can’t see any specific error in logs…
Anyone else experiencing this issue?

nickrout · October 1, 2020, 8:29pm

What were you on before 0.115.6?

snarby · October 1, 2020, 9:28pm

Same here, no Netatmo weather station although can see it in integrations. Tried deleting and reinstalling but just have unavailable next to all the sensors

teddy · October 1, 2020, 9:37pm

Great integration. However, so far in ShellyForHass I was able to use the physical switch (input) on the shelly as a binary sensor in hassio while I was able to configure the relay(s) as lights. Both does not seem to work now. For a Shelly 1 I only get one device and one entity, which is the relay, but no binary sensor representing the state of the input. I rolled back to 0.114 for this reason. Any ideas?

liuk4friends · October 1, 2020, 10:02pm

0115.5 and Netatmo sensors were working without problems

nickrout · October 1, 2020, 10:05pm

I can’t see any changes from 0.115.5 to 0.116.6 that would cause that, can you? 0.115: B-Day release! Media browser, tags, automations & WTH