I figured it out. It was user error.
I have the same issue as you but my time_pattern changes are correct. I’m going to roll back to 85 for now.
that’s one approach I guess… but eventually you are going to have to fix it so why not now?
So, after some tinkering, I added back the missing wemo and found that all automation jobs were disabled (enabled them fix it)
The new GUI editing tool is cool and make it easy to play with lovelace
Got an error while upgrading with pip 19.0.1, pip 18.1 works fine (python 3.7.2). pycparser seems to do something wrong.
Collecting pycparser (from cffi>=1.1->bcrypt==3.1.5->homeassistant)
Downloading https://www.piwheels.org/simple/pycparser/pycparser-2.19-py2.py3-none-any.whl (111kB)
100% |████████████████████████████████| 112kB 1.6MB/s
Exception:
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/pip/_internal/cli/base_command.py", line 176, in main
status = self.run(options, args)
File "/srv/homeassistant/lib/python3.7/site-packages/pip/_internal/commands/install.py", line 346, in run
session=session, autobuilding=True
File "/srv/homeassistant/lib/python3.7/site-packages/pip/_internal/wheel.py", line 886, in build
assert have_directory_for_build
AssertionErrorhave a workaround for AsusWRT use telnet protocol works on 0.86
Just updated to 0.86.2 from 85.1, no issues. Great work devs and congratulations on the lovelace milestone.
Same here. Tried upgrading to 0.86.2 and it broke badly. The UI looked likes this before (using a lot of groups basically on a per-room basis)
But it changed to
so all of the grouping are gone.
And also some automations broke (not a time / time_pattern issue):
2019-01-25 09:52:22 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]: Service notify.TelegramXXYYZZ does not match format <domain>.<name> for dictionary value @ data['action'][0]['service']. Got Noee /.../configuration.yaml, line 324). Please check the docs at https://home-assistant.io/components/automation/
Went back to 0.85.1 and everything works as expected.
use lowercase in you service
like notify.telegram…
This used to work in previous versions (even when using upper/lowercase). Any chance that this is an undocumented breaking change then?
Can’t understand about ZigBee management panel, is it out yet? how to access it? will it work with zigbee2mqtt / raspberry pi + cc2531 stick?
hi all,
my update worked nicely for me.
now i am just wondering about best practise to reference custom components without using YAML mode. or is it required to use YAML mode if you have content like this
resources:
- url: /local/simple-thermostat/simple-thermostat.js?v=1
type: module
when I run in YAML mode everything works and the custom card is rendered. as soon as i switch to default lovelace, it says the card is not know - obviously because the resources are not loaded.
any hints?
regards,
markus
Use raw editor to add custom components
Hi! Something’s going wrong… can not update from yesterday.
Could not contact Home Assistant Update to check for updates
What is going wrong? Are there issues with my connection?
i think i tried that and the resources were still not picked up. is that the official way to do it? i guess i did it wrong 
Yes it’s the ‘official way’
There was a bug in 0.85.0 (?) that wiped it out I believe but for now that’s the official way to do it.
1 Like
confirmed! thanks!
Yepp, my scraper broke down to. I even did a clean install of my server (becaus of other issuse) and scraper still dead…
The new slugify means entity ids now follow strick rules. its so much easier to just fix your issues by reading the updated documentation your error links to than going back to an old version expecting it to continue working in the future.
1 Like
Thanks for the reply. I probably do have Apple betas on, I should have turned that off. I’ll do some more investigation on my end.