0.60 Problems

Installation Home Assistant OS
1

Why did I click that update button? Not much works after the update to 0.60. Wink is not discovered, a 4 Ch Sonoff running Tasmota using emulated Hur only shows one channel, groups are messed up… How can I get back to 59.2?

edit… it seems the 0.60 install was corrupt. Starting over and getting things back.
edit… spent some time putting things back together and have a strange problem left over. I have Hue and emulated hue devices connected and hassio now confuses them. After a power-up everything seems fine and I can see and control all devices but get the configure hue dialog on the web page. When I click it and then press the button on the hue it goes away but then an emulated hue device that was working fine assumes the identity of a real hue device. It even substitutes itself in a group that included the emulated device.

2

Can’t help with these problems but I do have my own problms after updateing.
HASSIO front end is realy slow, history is dead, and I get a bunch of weird errors after the update while before all was running as it should. Her the errors…

Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
03:20 /usr/lib/python3.6/site-packages/homeassistant/core.py (ERROR)
Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
03:20 /usr/lib/python3.6/site-packages/homeassistant/core.py (ERROR)
Unable to find service input_number/select_value
03:04 core.py (WARNING)
Unable to find service sensor/turn_off
22:51 core.py (WARNING)
Unable to find service input_number/turn_off
22:51 core.py (WARNING)

Well that is my prob after release 0.60

3

Check your available SD card space (ie: make sure the DB2 file hasn’t gotten massive and chewed up all your space). I had my HassIO going crazy last week and couldn’t understand why. It wasn’t until after I had unfortunately tried to go back in time with a snapshot that I discovered the DB2 file was about 4GB and I had no room left for HassIO to run.

It would be so much better if HassIO would give a warning that space is low rather than just suddenly acting strange and having certain functions not work. I have since implemented a DB restriction to only keep 2 weeks worth of data which should prevent it happening again.

4

It might be worth mentioning also, that SD cards have a pretty limited lifespan and will slowly begin to corrupt once a certain amount of data has been written to it

5

Thanks for the info. I did start over fresh so the db2 size is still small. I;ll replace the SD card once the stores open again. I have managed to get almost everything working again, but still have odd device issues where they swap places, randomly don’t show in history, group tabs or <> but are still controlled properly from automations.

6

I am also getting strange things going on with 0.6. I can’t get my config file to checkout and I haven’t edited it since the last known good version that worked previously. The returned config test output is below. The last line is something about light.True. I also see the error in my main hass.io Log
Unable to find component light.True
11:22 PM loader.py (ERROR)

Everything mostly seems to load but not sure what is going on with this.

Testing configuration at /config
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up mqtt
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up http
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up recorder
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setup of domain mqtt took 0.0 seconds.
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds.
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.0 seconds.
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up api
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up system_log
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up history
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.0 seconds.
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds.
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.0 seconds.
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up frontend
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 0.0 seconds.
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up sun
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up map
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up group
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up sensor
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up updater
2017-12-25 23:25:55 ERROR (MainThread) [homeassistant.loader] Unable to find component light.True
2017-12-25 23:25:55 INFO (MainThread) [homeassistant.setup] Setting up emulated_hue
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.2 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain map took 0.2 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain group took 0.2 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 0.2 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 0.2 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain emulated_hue took 0.0 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setting up config
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setting up logbook
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setting up hassio
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setting up tts
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.0 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setting up automation
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setting up switch
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setting up light
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setting up script
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setting up fan
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.0 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain hassio took 0.0 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 0.0 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 0.0 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain switch took 0.0 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain light took 0.0 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain script took 0.0 seconds.
2017-12-25 23:25:56 INFO (MainThread) [homeassistant.setup] Setup of domain fan took 0.0 seconds.
Failed config
General Errors:
- Platform not found: light.True

Successful config (partial)

7

Did you check breaking changes from the previous HA version? Please post your config.

8

I think what is going on with my configuration is that I have a real Hue Bridge and a Sonoff 4CH Pro acting like a Hue bridge and Hassio is confusing the devices from both as if they are from one bridge. In my config folder I have two phue-xxx.conf files with the IPs of the two devices (hue hub and Sonoff). Nothing to be done there though. I think I may have to move the Sonoff over to MQTT to avoid interfering with the Hue. My current config worked up to v0.60.

9

My Config is generally pretty basic. Here is my main file.

`homeassistant:

Name of the location where Home Assistant is running

name: REDACTED

Location required to calculate the time the sun rises and sets

latitude: REDACTED
longitude: REDACTED

Impacts weather/sunrise data (altitude above sea level in meters)

elevation: 112

metric for Metric, imperial for Imperial

unit_system: imperial

Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones

time_zone: America/Los_Angeles

Customization file

customize: !include customize.yaml

hassio:

Show links to resources in log and frontend

#introduction:

Enables the frontend

frontend:

Enables configuration UI

config:

http:

Uncomment this to add a password (recommended!)

api_password: REDACTED

Uncomment this if you are using SSL/TLS, running in Docker container, etc.

Checks for available updates

Note: This component will send some information about your system to

the developers to assist with development of Home Assistant.

For more information, please see:

https://home-assistant.io/blog/2016/10/25/explaining-the-updater/

updater:

Optional, allows Home Assistant developers to focus on popular components.

include_used_components: true

Discover some devices automatically

#discovery:

Allows you to issue voice commands from the frontend in enabled browsers

#conversation:

Enables support for tracking state changes over time

history:

View all events in a logbook

logbook:

Track the sun

sun:

#media_player:

- platform: sonos

emulated_hue:
exposed_domains:
- light
- switch

map:

Text to speech

tts:

  • platform: google

mqtt:
broker: core-mosquitto

#remote:

- platform: harmony

name: Family Room Hub

activity: 22684422

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
light: !include lights.yaml
switch: !include switch.yaml
sensor: !include sensor.yaml
fan: !include fan.yaml`

10

I can’t help with the emulated Hue, but it appears that my issue has been identified. https://github.com/home-assistant/home-assistant/issues/11183
Perhaps your issue is listed here? https://github.com/home-assistant/home-assistant/issues

11

I’m running Hass.io and am unsure how to check my SD card space. I think I found something a while back but can’t remember how. Any tips for this kind of docker setup (seems like VMs they each had defined space when I found it once before)? Also, for checking card health?

12

I use WinSCP to access my Pi running HassIO. With that I can see file sizes etc. I use the below code to keep the DB file size down.

configuration.yaml

recorder:
  purge_interval: 2
  purge_keep_days: 14
1 Like
13

Same but I’m only keeping a day. Hassio still locks up pretty much every day and needs a reboot. I’m using the noobs card I got from RS when I got the Pi3. Maybe I need to switch to a Samsung EVO. (It’s a 32gb card)

14

If you do, hopefully you have better success than me. I found that my Pi didn’t like high capacity cards and I ended up with an 8Gb old one that was lying around. The problem with the larger cards (brand new) became evident when HassIO wouldn’t even load after initial install. I tried out the old 8Gb and everything installed and booted up perfectly…

15

Interesting. The noobs card is 32gb. So if I get a new one I’ll get a smaller evo one.

16

my larger card wasn’t the NOOBS one this time around. I think the 8Gb I ended up with was originally a NOOBS that I formatted after it had OSMC previously…