woody4165
(Woody)
November 29, 2018, 7:45pm
91
A new issue for me after upgrading.
I have Node Red installed on a separate server, working until update to 0.83.
Now the connection to Hassio is not working anymore.
I’m using API pass (in the picture removed) and it’s defined in secrets.yaml
Is there anything new that I have missed?
Thanks
1 Like
kevjs1982
(Kevjs1982)
November 29, 2018, 7:48pm
92
That’s probably related to https://github.com/home-assistant/home-assistant/pull/18733 - fix due in 0.83.1
Another poster was going to see if they could get it to worth with the moder tokens.
woody4165
(Woody)
November 29, 2018, 7:50pm
93
Thanks.
I am going to downgrade to 0.82.x, but I don’t remember what was the latest NON-beta version, any help please?
Thanks
jusdwy
November 29, 2018, 7:51pm
94
0.83 broke my Lovelace
http://hassio.local:8123/frontend_latest/app-0fd67575.js:89:305 Uncaught TypeError: Cannot read property ‘state’ of undefined
2:49 PM components/system_log/init .py (ERROR)
http://hassio.local:8123/local/custom_ui/dark-sky-weather-card.js?v=4:144:85 Uncaught TypeError: Cannot read property ‘state’ of undefined
2:43 PM components/system_log/init .py (ERROR)
still can load /states without issue. No states in /dev-state seem to be acting up, and everything was working previous to upgrading from 0.82.1
update:
not sure what happened, but when I went from /states to /lovelace it partially loaded. the main page view is blank, but I can click thru my others views without issue. main page does include the custom dark sky card.
and when i comment out the dark sky card it works. something changed with how HA interprets custom cards?
update update: (SOLVED!)
@balance82
I asked this in Discord today, and Arsaboo stated it is updated on his repro: https://github.com/arsaboo/homeassistant-config
The way I ended up fixing this was:
Rename the dark-sky-weather-card.js to dark-sky-weather.card.js.old
Create a new dark-sky-weather-card.js in www/custom_ui. Contents for the file here
In the ui-lovelace.yaml file, replaced the contents for the old weather card with the following:
- id: dark_sky_animated_card
type: custom:dark-sky-weather-card
…
issue was with entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature not starting at 1 in ui_lovelace.yaml.
(also minor change in the dark-sky-weather-card.js to update pressure to mbar)
Schneider
(Antonio Schneider)
November 29, 2018, 7:56pm
96
Hello guys! Thanks for this awesome update.
I am amazed how fast lovelace UI loads now, great work!
Asus component working fine now, just a bug (maybe?) on how download/upload sensors shows data:
Both sensors shows the other’s value. In the image above, I was just downloading, at 50mbps, no upload whatsoever… Very strange.
Here is how it shows on the Asus WebUI:
Also: any adive on using track_new_devices
parameter now? I ratter set it manually for each new device.
Thanks!
markbajaj
(Mark Bajaj)
November 29, 2018, 8:07pm
101
Working now.
Followed advice from someone on here (sorry can’t see your post now!)
remove OwnTracks from device_tracker and put in the configuration.yaml on its own
OwnTracks:
Anyone else seeing issues with Schlage Z wave locks? Have a BE468 and a BE469. Both respond to local operation of the lock, but if I lock/unlock through Hass, the status never updates. Saw the update in the change log so I’m guessing it has something to do with that PR.
skynet01
(Alex)
November 29, 2018, 9:14pm
104
Any update on when an updated version of DenonAVR will be merged into the release? It’s been about 2 month since it got updated (https://github.com/scarface-4711/denonavr ) Would love to use my new receiver
RT-AX88U - everything works, but i cant disable track mode for new devices for it.
gurbyz
(Gerben)
November 29, 2018, 9:27pm
106
I also have this error with google tts since today, but I’m still on 0.81.6 (HassIO). So I think this error is not related to the new release directly.
cogneato
(Cogneato)
November 29, 2018, 9:40pm
107
Dinges28
(Richard)
November 29, 2018, 9:43pm
108
Having the same issue here…
Hass works normaly, but every 2 minutes log is flooded with this message
1 Like
Is it still working? Mine was only working for 10 mins, but i’m using telnet on a RT-AC66U.
Schneider
(Antonio Schneider)
November 29, 2018, 10:05pm
110
I am using SSH and it works great, apart from the Download/Upload sensor data. Not sure how to set track_new_devices
now. Thanks.
jeanniquini
(Jean Niquini)
November 29, 2018, 10:16pm
111
Same here. Did the downgrade work for you?
jeanniquini
(Jean Niquini)
November 29, 2018, 10:35pm
113
node-red is not connecting to the HA.
Login attempt or request with invalid authentication from 192.168.X.X
jeanniquini
(Jean Niquini)
November 30, 2018, 12:00am
114
@balloob
This error is occurring when I run an ifttt webhook:
Error executing service <ServiceCall switch.turn_off (c:4eb3ebc0579844abb7deb328c5253e54): entity_id=[‘switch.lampada’]>
Traceback (most recent call last):
File “/home/jean/apps/Homeassistant/lib/python3.5/site-packages/homeassistant/core.py”, line 1177, in _event_to_service_call
await service_handler.func(service_call)
File “/home/jean/apps/Homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity_component.py”, line 177, in handle_service
self._platforms.values(), func, call
File “/home/jean/apps/Homeassistant/lib/python3.5/site-packages/homeassistant/helpers/service.py”, line 250, in entity_service_call
permission=POLICY_CONTROL
homeassistant.exceptions.Unauthorized: Unauthorized
What do you mean? denonavr
already uses the latest package available (0.7.6).
We can’t update the component if the PR (I assume you want https://github.com/scarface-4711/denonavr/pull/65 ) for support isn’t merged and a new version gets released on pypi.