0.84: Cloud webhooks, Wunderlist and USGS Earth Quakes

nickrout · December 17, 2018, 9:45pm

Beyond suggesting you clear your browser cache, how do you expect any help with so little information.

James_Arrowsmith · December 17, 2018, 10:21pm

what information do you need? i have cleared the browser cash and still it show no entities what so ever. there is no error messages. if i go to the history or log book tabs i can see the the list of all the items but on on the main page where everything should be its blank.

this link seems identical: https://www.reddit.com/r/homeassistant/comments/a5su7o/no_entities_after_upgrading_to_841/

ha_steve · December 18, 2018, 1:17am

Are you using lovelace? If so, did you read/do what it said to preserve yaml mode for lovelace in the relase notes? Did you set your log level to debug and look for error messages in the log file?

You have to understand you did the equivalent of calling a mechanic and saying “My car won’t run. It’s a BMW.”

Teocell · December 18, 2018, 8:29am

Hey guys! I was waiting for the Netatmo Home coach integration from a long time! I have a Hassio setup on a Raspberry Pi. The Netatmo discovery function didn’t find my Home Coach, even if I disable it and I configure the Sensor, it doesn’t work. Any clue? (Of course it can find the Thermostat)

Thanks in advance,
Marco

Marius82 · December 18, 2018, 8:40am

Has someone an answer?

sparkydave · December 18, 2018, 9:01am

‘id’ was changed to ‘path’ in 0.84

konzolec · December 18, 2018, 9:16am

Any news regarding this? Really annoying.

Should be Open, Closed and not off (same goes for Away, Home and not not_home

DavidFW1960 · December 18, 2018, 9:16am

Mine are all still ID: I don’t see path anywhere. 0.84.3

Marius82 · December 18, 2018, 9:36am

I upate from 083.3 where I used Lovelace. Then I do the following steps, because I use Lovelace before:
https://www.home-assistant.io/blog/2018/12/12/release-84/#for-existing-lovelace-testers

You can do this by opening the Lovelace UI and click on Configure UI, this will prompt you to change to storage mode. This will unlock a new option in the menu called “raw config editor”. Open this and paste the content of your ui-lovelace.yaml file into it and click save.

But I still get the same error as marcurs in his post:

I noticed this error when trying to edit the Lovelace UI from web.
The error disappears manually removing ID field.
The ID field was automatically generated by HA in some previous update. Is it still necessary or can it be removed?

HA_id_issue1099×494 36.7 KB

sparkydave · December 18, 2018, 9:37am

@Marius82 see the first breaking change on the above page

Mariusthvdb · December 18, 2018, 10:04am

do you happen to use Custom-ui? It was not compatible and now has been updated. Fixed the disappearing groups in my desktops and mobile devices.

github.com

andrey-git/home-assistant-custom-ui/blob/master/CHANGELOG.md

## Changelog

#### 2019-05-18
*   Hotfix for HA 0.94+

#### 2019-03-24
*   Fix for `icon-color` for HA 0.88+
*   Fox config panel for HA 0.90+

#### 2019-01-13
*   Hotfix for `extra_badge` for HA 0.85+

#### 2018-12-17
*   Hotfix for HA 0.84.1+

#### 2018-08-31
*   Fix for icon_color not being applied on HA >0.77 (by Jérôme)
*   This version requires HA 0.77+

#### 2018-08-06

This file has been truncated. show original

aidbish · December 18, 2018, 10:46am

there is a github issue open for it.

Targettio · December 18, 2018, 12:40pm

A couple of questions about the lightwave component.

Does it communicate with the lightwave hub locally, or do the API calls go via the internet
Does the component work with both generation 1 and 2 lightwave items (with state reporting on Gen 2)?

If it is local and has state reporting then I think this a big new feature! Thanks

patrik996 · December 18, 2018, 1:45pm

Mine is working fine. Running hassio though.

konzolec · December 18, 2018, 2:05pm

allright, thnx will check.

conradh · December 18, 2018, 2:12pm

Thank you. I fixed it. Component can only recognize the usb device by ID.

royduin · December 18, 2018, 7:04pm

It’s a bug! See: https://github.com/home-assistant/home-assistant-polymer/issues/2354, the “friendly names” should be visible by default. Probably fixed in the next release 0.84.4 with this PR: https://github.com/home-assistant/home-assistant-polymer/pull/2356

DavidFW1960 · December 18, 2018, 11:07pm

I see that but in my imported lovelace it is still showing ID not path and it’s not crashing. It’s not clear from the docs how path is to be used - it seems totally different to the ID.

It shows ID’s for the views and uses that in the URL and also ID’s for the cards… Strange it’s crashing your(?) system but not mine.

Mariusthvdb · December 18, 2018, 11:30pm

fwiw, using yaml mode, I had views with id: name which were automatically created by ne of the available scripts (not the current Lovelace functionality).

Loading Lovelace wouldn’t recognize these and used numbered views instead. Which were automatically created following my regular HA view: yes groups now by the Lovelace functionality.

Changing id: to path: in all of my view files, made my original views re-appear immediately in the path and browser window.

DavidFW1960 · December 18, 2018, 11:50pm

I just asked on Discord and apparently all the ID’s can be deleted so I’m going to do that and see if anything breaks. Wish me luck!