Issues moving from Home Assistant to Hass.io

Configuration
1

I have a working Hass.io system with Samba running in a VirtualBox VM. I’m currently using Home Assistant on another machine. When I copied my configuration files from Home Assistant to the VM there were at least 2 issues. First, Im still using
!include_dir_list automation/
on home assistant but the VM only found the applications in the first folder. Do I really need to migrate all my applications to a single applications.yaml file for Hass.io or am I missing something? Second, The configuration for Tuya is being ignored in Hass.io. Here it is:

tuya:
  username: myusername
  password: !secret tuya_password
  country_code: 1
  platform: smart_life

I’d greatly appreciate any assistance.

2

I’m assuming by “applications” you mean automations? If so, as long as you have only one automation in each file with !include_dir_list it should work. What do you mean by “only found the [automations] in the first folder?”

Also, what do you mean by the tuya config being ignored? Any errors in the log?

3

Opps, I did mean automatons. And my automation folder has 12 sub-folders. Only those automations in the first sub-folder /alarms made it into the VM… Automations in the other 11 sub-folders didn’t show up. And I was in such a hurry to get my Home Assistant back online, I forgot to check the logs. Jeez…what was I thinking.

4

That’s weird about the automations subfolders. Not sure why that wouldn’t be working. Did you reload automations using the button in the frontend?

Also, just to clarify, you’re still running Home Assistant with Hass.io. Hass.io is one method of installing Home Assistant that enables additional functionality (add-on store and snapshot capability). This is a good read if you don’t understand what I mean.

5

I have Home Assistant running in a venv on a Ubuntu based laptop. I have Hass.io running in Vbox on different Ubuntu desktop system. I reloaded my automations with the button to no effect. Also upon closer inspection I have no scripts at all. Only the handful of applications I actually have appear in the logs. There is no mention of scripts. As far as tuya is concerned it found a couplew of lights and switches but missed others. Perhaps there’s a name problem I can check under ‘states’

6

Can you post your entire config?

7

The Tuya issues were all associated with names that got overwritten at some point. That issue is now fixed. Here it is I think I got rid of all the secret stuff:

homeassistant:
  auth_providers:
    - type: homeassistant
    - type: trusted_networks
      trusted_networks:
        - addr/24
        - 127.0.0.1

# Name of the location where Home Assistant is running
  name: cassandra
# Location required to calculate the time the sun rises and sets
  latitude: lat
  longitude:long
# Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 1118
# 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/Chicago

  customize: !include customize.yaml


namecheapdns:
  domain: home.com
  password: !secret namecheap_password

#speedtestdotnet:
#  server_id: 16142
#  scan_interval:
#    minutes: 15
#  monitored_conditions:
#    - ping
#    - download
#    - upload

lovelace:
  mode: yaml

tplink:
  discovery: true

media_player:
  - platform: vlc
    name: vlc


camera:
  - platform: generic
    name: wyze_one
    still_image_url: http://addr
    stream_source: rtsp://stuff


wink:

# Show links to resources in log and frontend
#introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:


# enable nmap presence detection
device_tracker:
#  - platform: nmap_tracer
#    hosts: addr.120-124
#    home_interval: 15

  - platform: ping
    hosts:
    list


#custom_updater:
#component_urls:
#  - https://raw.githubusercontent.com/robmarkcole/Hue-sensors-HASS/master/custom_updater.json

notify:
  - name: notify
    platform: pushbullet
    api_key: !secret notify_api_key

  - name: sms
    platform: smtp
    server: smtp.gmail.com
    port: 587
    timeout: 15

    sender: [email protected]
    username: [email protected]
    password: !secret bdtgmail_password
    recipient: [email protected]
   
# Discover some devices automatically
discovery:
  ignore:
    - directv
#    - wink

api:

cloud:
  alexa:
    filter:
      include_entities:
        - input_boolean.my_bedtime
        - input_boolean.wakeup
        - input_boolean.bark
        - input_boolean.dinner_ready
        - input_boolean.wegone
        - input_boolean.nap_time
      include_domains:
        - switch
        - light
        - fan
      exclude_entities:
        - input_boolean.barking_enable
        - input_boolean.hue_switch
        - input_boolean.dim_bedroom_enable
        - input_boolean.double_door_button
        - input_boolean.double_garage_door
        - input_boolean.double_garage_door_alarm
        - input_boolean.in_alarm
        - input_boolean.pbx_srvr
        - input_boolean.livingroom_lights
        - input_boolean.misters_on
        - input_boolean.nightlighting
        - input_boolean.sunrise_enabled
        - input_boolean.testing
        - input_boolean.answer_door
        - input_boolean.master_bedroom_lights
        - input_boolean.hue_switch
      exclude_domains:
        - automation
        - device_tracker


 


#http:

#  api_password: long stuff  base_



system_health:



# 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


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

# scene descriptions
# scenes: !include scenes.yaml

# Enables support for tracking state changes over time
history:

recorder:

# View all events in a logbook
logbook:

hue:
  bridges:
    - host: addr
      allow_unreachable: true
#      filename: phue.conf

tuya:
  username: [email protected]
  password: !secret tuya_password
  country_code: 1
  platform: smart_life

python_script:

logger:
  default: error
  logs:
    homeassistant.components.python_script: debug
    homeassistant.components: info
    homeassistant.components.device_tracker: critical
    homeassistant.components.camera: critical    


# Track the sun
sun:
sensor: !include sensors.yaml

ambient_station:
  api_key: stuff
  app_key: more stuff
red_conditions:





script: !include_dir_merge_named scripts/

switch: !include switch.yaml

light: !include lights.yaml

input_boolean: !include input_boolean.yaml

envisalink: !include envisalink.yaml


zwave:
  usb_path: /dev/ttyACM0
  polling_interval: 30000
  autoheal: False


# Text to speech
tts:
  - platform: google_translate
    service_name: google_say
#    service_name: google_say

ring:
  username: '[email protected]'
  password: !secret ring_password

binary_sensor: !include binary_sensors.yaml

climate:
 
group: !include groups.yaml

shell_command: !include shell_commands

mqtt:
  broker: 192.168.1.17
  port: 1883
  keepalive: 60
  client_id: sbmqtt
  username: name
  password: !secret mqtt_password

mqtt_statestream:
  base_topic: bark
  include:
    domains:
      - input_boolean

automation: !include_dir_list automation/
8

Next time I try my VM I need to check permissions on the automation and script folders.