Manual integration and node status

Hello,
I am trying like 2 days to make this working well like before but i couldnt and I need help!

My steps:

  1. Install fresh hassio
  2. Add repo and install homelib addon
  3. Connect wemos d1 mini by usb cable to raspberry.
  4. Go through tutorial to make simple node
  5. Adding BME280 sensor and pir/microweave config to node
  6. Trying upload it to wemos
  7. There is a part o log flog.yaml (6.0 KB)

First problem is all what i can press after upload firmware is “STOP” and if i click this i see button with name " Terminated process" There is no way to turn off this view beside pressing STOP
Second problem is i cannot integrate node and hassio, i tried to type “nodka1.local” but it is not working at all.Adn ofcourse nothing is detected automaticly

As you see in logs values are given, what i need to do to make it work like this version from old repo :frowning: :frowning: I just lost my patient to this.

Pressing the STOP button after everything is successfully uploaded and running is not a problem. You just exited the log viewer, and the node keeps working.

What happens if you ping to nodka1.local? Can you ping the node? Is your domain .local, or something else?
Can you try adding the node with its IP address? (I have no idea if that should work? @OttoWinter)

Can you share your node yaml file?

I again reinstall hassio to make it work, just in case. I just want to abandon this for this moment but if u answer i will give it next try :slight_smile:

Probably mdns is not working on my router (i cannot open configuration by hassio.local) so that means i need to set static ip. But if i remember well, even if i set static ip for node, i saw her in connected devices to wifi but still the status was offline. I configured BME280 sensor and it shows his status in log but again, i wasnt able to integrate it. The offline status keeps remaining :frowning: and that makes me sad and nervous, even if this work somehow :stuck_out_tongue:

Glad to hear hitting stop is not a problem :slight_smile:

Ok now it is going to be strange :smiley: I reinstalled hassio, create a node by this configurator, next i click edit and edit to sth like this

esphome:
  name: wemosmini1
  platform: ESP8266
  board: d1_mini

wifi:
  ssid: 'Nikola'
  password: 'mynetpassword'
  manual_ip:
    # Set this to the IP of the ESP
    static_ip: 192.168.100.21
    # Set this to the IP address of the router. Often ends with .1
    gateway: 192.168.100.1
    # The subnet of the network. 255.255.255.0 works for most home networks.
    subnet: 255.255.255.0

# Enable logging
logger:

# Enable Home Assistant API
api:
  password: 'mypassword'

ota:
  password: 'mypassword'

i2c:
  sda: D6
  scl: D7
  scan: False
  
sensor:
  - platform: bme280
    temperature:
      name: "BME280 Temperature"
    pressure:
      name: "BME280 Pressure"
    humidity:
      name: "BME280 Humidity"
    address: 0x76
    update_interval: 60s

binary_sensor:
  - platform: gpio
    pin: D5
    name: "PIR Sensor"
    device_class: motion
  - platform: gpio
    pin: D0
    name: "Microweave Sensor"
    device_class: motion

And it integrate normally and shows Online status

Next i created another node with confige like this:

esphome:
  name: wemosmini2
  platform: ESP8266
  board: d1_mini

wifi:
  ssid: 'Nikola'
  password: 'mynetpassword'
  manual_ip:
    # Set this to the IP of the ESP
    static_ip: 192.168.100.22
    # Set this to the IP address of the router. Often ends with .1
    gateway: 192.168.100.1
    # The subnet of the network. 255.255.255.0 works for most home networks.
    subnet: 255.255.255.0
    
# Enable logging
logger:

# Enable Home Assistant API
api:
  password: 'mypassword'

ota:
  password: 'mypassword'

i2c:
  sda: D2
  scl: D1
  scan: False

sensor:
  - platform: bme280
    temperature:
      name: "BME280 Temperature"
    pressure:
      name: "BME280 Pressure"
    humidity:
      name: "BME280 Humidity"
    address: 0x76
    update_interval: 60s
  - platform: adc
    pin: A0
    name: "TEMT6000 Illuminance"
    unit_of_measurement: lx
    icon: "mdi:weather-sunny"
    filters:
      - lambda: |-
          return (x / 10000.0) * 2000000.0;

output:
  - platform: esp8266_pwm
    pin: D6
    id: redgpio
  - platform: esp8266_pwm
    pin: D5
    id: greengpio
  - platform: esp8266_pwm
    pin: D0
    id: bluegpio

light:
  - platform: rgb
    name: "Multisensor Light"
    red: redgpio
    green: greengpio
    blue: bluegpio
#light_effects
    effects:
      - strobe:
          name: Strobe Effect With Custom Values
          colors:
            - state: True
              brightness: 100%
              red: 100%
              green: 90%
              blue: 0%
              duration: 500ms
            - state: False
              duration: 250ms
            - state: True
              brightness: 100%
              red: 0%
              green: 100%
              blue: 0%
              duration: 500ms
      - random:
          name: Random Effect With Custom Values
          transition_length: 2s
          update_interval: 2s
      - flicker:
          name: Flicker Effect With Custom Values
          alpha: 95%
          intensity: 3.5%

And this one is showing offline status. I copied everything from first node and change ip only and add some info about sensors.
I dont know how to go thorugh this. Two almost the same configs and one is working well the next one is not. I am watching connected devices to my network. Differences between one wemos and naother is one have network adapcter comapny: Espressif Inc. and this working now has this blank.

Guys please help me im getting sick of this. I am running out of clues here.

EDIT: I deleted automatic intergate and restart hassio. after this i added manually nodes and they dont have any sensor inside. In esphome dashboard both are offline, but when i click show logs they showing actual status of sensors

You could try adding a status sensor and a wifi signal strength sensor.
These should show up in hassio integrations.

If they appear in the logs, and show the state of the sensors (and this state is correct, and updates correct), then you are almost there.

What router do you have? Is everything on the same subnet?

I created a simple node as you proposed. There is a config:

esphome:
  name: test1
  platform: ESP8266
  board: d1_mini

wifi:
  ssid: 'Nikola'
  password: 'mynetpassword'
  manual_ip:
    # Set this to the IP of the ESP
    static_ip: 192.168.100.28
    # Set this to the IP address of the router. Often ends with .1
    gateway: 192.168.100.1
    # The subnet of the network. 255.255.255.0 works for most home networks.
    subnet: 255.255.255.0


# Enable logging
logger:

# Enable Home Assistant API
api:
  password: 'mypassword'

ota:
  password: 'mypassword'

sensor:
  - platform: wifi_signal
    name: "WiFi Signal Sensor"
    update_interval: 60s

binary_sensor:
  - platform: status
    name: "Test1 Status"

There is a upload by usb log. Before first line there was many “compiling” lines but i think they arent matter.

Compiling .pioenvs/test1/FrameworkArduino/umm_malloc/umm_malloc.c.o
Archiving .pioenvs/test1/libFrameworkArduino.a
Linking .pioenvs/test1/firmware.elf
Retrieving maximum program size .pioenvs/test1/firmware.elf
Building .pioenvs/test1/firmware.bin
Checking size .pioenvs/test1/firmware.elf
Memory Usage -> http://bit.ly/pio-memory-usage
DATA:    [====      ]  39.5% (used 32344 bytes from 81920 bytes)
PROGRAM: [===       ]  31.2% (used 326392 bytes from 1044464 bytes)
======================== [SUCCESS] Took 260.88 seconds ========================
INFO Successfully compiled program.
INFO Connecting to 192.168.100.28
INFO Uploading /config/esphome/test1/.pioenvs/test1/firmware.bin (330544 bytes)
Uploading: [============================================================] 100% Done...


INFO Waiting for result...
INFO OTA successful
INFO Successfully uploaded program.
INFO Starting log output from 192.168.100.28 using esphome API
INFO Connecting to 192.168.100.28:6053 (192.168.100.28)
WARNING Initial connection failed. The ESP might not be connected to WiFi yet (Error connecting to 192.168.100.28: timed out). Re-Trying in 1 seconds
INFO Connecting to 192.168.100.28:6053 (192.168.100.28)
INFO Successfully connected to 192.168.100.28
[13:43:13][I][application:098]: esphome-core version 1.11.2 compiled on Feb 28 2019, 13:38:58
[13:43:13][C][wifi:348]: WiFi:
[13:43:13][C][wifi:244]:   SSID: 

[redacted]
[13:43:13][C][wifi:245]:   IP Address: 192.168.100.28
[13:43:13][C][wifi:247]:   BSSID: 

[redacted]
[13:43:13][C][wifi:248]:   Hostname: 'test1'
[13:43:13][C][wifi:252]:   Signal strength: -68 dB ▂▄▆█
[13:43:13][C][wifi:253]:   Channel: 7
[13:43:13][C][wifi:254]:   Subnet: 255.255.255.0
[13:43:13][C][wifi:255]:   Gateway: 192.168.100.1
[13:43:13][C][wifi:256]:   DNS1: 1.1.1.1
[13:43:13][C][wifi:257]:   DNS2: 1.0.0.1
[13:43:13][C][binary_sensor.status:047]: Status Binary Sensor 'Test1 Status'
[13:43:13][C][binary_sensor.status:047]:   Device Class: 'connectivity'
[13:43:13][C][logger:159]: Logger:
[13:43:13][C][logger:160]:   Level: DEBUG
[13:43:13][C][logger:161]:   Log Baud Rate: 115200
[13:43:13](Message skipped because it was too big to fit in TCP buffer - This is only cosmetic)
[13:43:13][C][sensor.wifi_signal:042]: WiFi Signal 'WiFi Signal Sensor'
[13:43:13][C][sensor.wifi_signal:042]:   Unit of Measurement: 'dB'
[13:43:13][C][sensor.wifi_signal:042]:   Accuracy Decimals: 0
[13:43:13][C][sensor.wifi_signal:042]:   Icon: 'mdi:wifi'
[13:43:13][C][api:089]: API Server:
[13:43:13][C][api:090]:   Address: 192.168.100.28:6053
[13:43:13][C][ota:129]: Over-The-Air Updates:
[13:43:13][C][ota:130]:   Address: 192.168.100.28:8266
[13:43:13][C][ota:132]:   Using Password.

After this status of node is still offline. They arent show automaticly in hassio but after manual integration sensors show up and it seems they are working, signal is -71 dB, status online (in hassio).

Router Huaiwei HG8247, everything in the same subnet.

Your node is working correctly.

Because mDNS is not working, it is showing offline in the ESPHome dashboard. Next release will make it possible to fallback to ‘normal’ ping connections. So next release you should be able to have them view as online.

You need to integrate them the way you did. So everything should be fine.

If you now add the other sensor (as in your previous config), they should show automatically. (because the node is added)

Please try adding the other sensors the same way, and let it know here if it worked.

Maybe you have 1 bad node, with hardware failure?

Hello! Thanks for your answer and help.
I hope next release will show status correctly and i wont see any offline status.
As you writed, i manually added node, added sensors to config and they are visible and working in hassio. On the other node too.

So there left a problem with offline status but i hope it will be fixed soon :slight_smile:

1 Like

Ouch, i was sure i have problems behind but it seems it is not true :frowning: @OttoWinter

2019-03-01 13:35:03 WARNING (MainThread) [homeassistant.components.esphome] Error getting initial data: Timeout while waiting for API response! 2019-03-01 13:42:37 WARNING (MainThread) [homeassistant.components.esphome] Error getting initial data: Timeout while waiting for API response!
13 times.

Im using duckdns and nginx, mby it is problem? Mby i should forward some more ports for esphome?

What ports did you open? From where to where?

Are the nodes on the same subnet as the home assistant server?

See https://github.com/esphome/issues/issues/80. And no you do not need to open any ports for esphome.

I have 80 and 443 open.
Nodes are in the same subnet as home assistant server.

@OttoWinter
I read it before. It seems my router doesnt support mdns.

How did you open the ports if they are on the same subnet?

This is misunderstanding. As open ports i mean to give hassio server acces from outside (raspberry pi). I just thought mby esphome need acces to some port :stuck_out_tongue: All devices are in one subnet

I am having the same error and the web interphase of HA does not load. Would you please let me know if you find a solution for this? Thanks!

For this Problem in this thread there is a solution

ESPhome uses mDNS witch is a multicast protocol, multicast does not cross vlans.

You have 4 options:

Use a Firewall/Router that permits mDNS to cross vlans
Use Avahi reflector on a RPI connected to all vlans
On hass.io add the "status_use_ping=true"
On esphome docker dashboard use the env "ESPHOME_DASHBOARD_USE_PING=true"

see: Dashboard status light not working across subnets/zones · Issue #641 · esphome/issues · GitHub

But your missing ha webinterface has nothing to do with this