Nothing Showing Up - DIscovery vs router issues?

Installation
1

I have the home assist up and running, the newest version on a 64 bit raspberry pi. The samba works.
But nothing gets discovered.
For a brief moment in time, 1 of my 2 wemo light switches showed up.
But I don’t see the roku, nor the honeywell thermostat. Nor the iRobot Roomba.
I think there may be some router settings that need to be tweaked, but there are umpteen options.
I assigned the Hassio its on static IP address, as I also have done with each of the 2 wemo power switches (each for a lamp). Still they don’t show up.
Wemo switches both work with Alexa, and the app on my phone (using both wifi and cellular connections). Regarding the Wemo, I even made sure all the firmware was updated.
I am using a LAN connection from the raspberry pi to the router.
Any suggestions or thoughts are appreciated.
Here’s my configuration code:

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: XX.XXXX (i have the real coordinates in the actual program)
  longitude: XX.XXXX
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 0
  # 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
  # Customization file
  customize: !include customize.yaml

# Show links to resources in log and frontend
introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

http:
  # Secrets are defined in the file secrets.yaml
   api_password: XXXXX (I have my real password here)
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # base_url: example.duckdns.org:8123

# 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:
wemo:
media_player:
  - platform: roku
climate:
  - platform: honeywell
    username: [email protected]
    password: XXXXX
    scan_interval: 600
vacuum:
  - platform: roomba
    host: 192.168.1.60
    username: [email protected]
    password: XXXXX

# 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:

# Enables a map showing the location of tracked devices
map:

# Track the sun
sun:

# Weather prediction
sensor:
  - platform: yr

# Text to speech
tts:
  - platform: google

# Cloud
cloud:

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

panel_iframe:
  configurator:
    title: Configurator
    icon: mdi:wrench
    url: http://192.168.1.197:3218
2

You might need to specify a static ip address for the Wemo’s in config yaml.
I do find that it takes a while for wemos to pop up on my system…

3

any thoughts on nothing else being discovered, despite my coding for them?
Do you think it makes a difference that I used the 64-bit image of the OS when I flashed my initial set up, not the 32 bit one (that is marked recommended)? The raspberry pi has a 64 bit processor.
O the server, I have plug and play functionality turned on, with 2 hops as the default. Does this make any difference?
I’m all new to this computer coding, and I appreciate your help and patience. I was very psyched to get this home automation thing up and running, and this platform looked ideal, but I’m having a heck of a time getting off the ground here. It’s very frustrating. Thanks again.

4

I find ‘discovery’ to be quite useless for me. Add your devices to your config and they will show up.

1 Like
5

People will say variously that the 64bit version is:

  1. experimental
  2. unstable
  3. incompatible with some addons
  4. a work in progress

However, in my experience, I have been running the 64 bit version for a month I think - maybe longer… ever since version 1.7 and I’m running the beta stream and I always update immediately and also I updated the host to 1.9. I have not had a single issue with 64 bit.

Both the 32bit and the 64bit are a lot slower than the old ResinOS version but HassOS is the future and also, once it’s ‘up’ it is no different speedwise.

Discovery for me works fine.

I don’t even have a clue what you mean by this or what you actually setup???

Again, with Wemo, I find it takes up-time for them to be ‘discovered’ You can fully configure the component manually though by setting the ip address in the config yaml… see the docs for wemo!

6

After listing the static IP’s under the wemo section, and updating the WEMO app and multiple firmware updates through the app, the 2 wemo swtiches now show up fine. and work!
And the Roomba now shows, too! Doesn’t work.
The honeywell doesn’t show up at all.

For future reference, when I save snapshots, and want to go back to an old one, is it recommended to use the first option, or the second option (wipe and install)?

7

I use wipe and restore.
I have had mixed luck restoring snapshots. When I restore a snapshot on a clean install it works perfectly (usually have to delete the database!) However if I restore a snapshot on a working system I get mixed results.