search

esphome / issues

Issue Tracker for ESPHome
https://esphome.io/
294 stars 37 forks source link

MQTT connection socket error #45

Closed Michael0yodi closed 5 years ago

Michael0yodi commented 5 years ago

Device: D1 Mini, Sonoff Basic R2

Device is losing connection all the time, its restored automatically. the same behavior on both devices, tested power saving modes and other wifi settings without success, device responds to ping while losing mqtt connection.

Home Assistant: 0.87.1 Mosquitto broker hassio: Latest esphomeyaml

testmini-dc4f221d5129, disconnecting. 1549955558: New connection from 172.16.1.140 on port 1883. [INFO] found mqttuser on Home Assistant 1549955558: New client connected from 172.16.1.140 as testmini-dc4f221d5129 (c1, k1800, u'mqttuser'). 1549955862: Socket error on client testmini-dc4f221d5129, disconnecting. 1549955862: New connection from 172.16.1.140 on port 1883. [INFO] found mqttuser on Home Assistant 1549955862: New client connected from 172.16.1.140 as testmini-dc4f221d5129 (c1, k1800, u'mqttuser'). 1549956166: Socket error on client testmini-dc4f221d5129, disconnecting. 1549956166: New connection from 172.16.1.140 on port 1883. [INFO] found mqttuser on Home Assistant 1549956166: New client connected from 172.16.1.140 as testmini-dc4f221d5129 (c1, k1800, u'mqttuser'). 1549956188: Saving in-memory database to /data/mosquitto.db. 1549956470: Socket error on client testmini-dc4f221d5129, disconnecting. 1549956470: New connection from 172.16.1.140 on port 1883. [INFO] found mqttuser on Home Assistant 1549956470: New client connected from 172.16.1.140 as testmini-dc4f221d5129 (c1, k1800, u'mqttuser'). 1549956774: Socket error on client testmini-dc4f221d5129, disconnecting. 1549956774: New connection from 172.16.1.140 on port 1883. [INFO] found mqttuser on Home Assistant 1549956774: New client connected from 172.16.1.140 as testmini-dc4f221d5129 (c1, k1800, u'mqttuser'). 1549957078: Socket error on client testmini-dc4f221d5129, disconnecting. 1549957078: New connection from 172.16.1.140 on port 1883. [INFO] found mqttuser on Home Assistant 1549957078: New client connected from 172.16.1.140 as testmini-dc4f221d5129 (c1, k1800, u'mqttuser').

Home assistant logbook: 08:44 Test GP1 turned off 08:44 Test GP1 changed to unavailable 08:44 Test GP1 turned off 08:44 Test GP1 changed to unavailable 08:44 Test GP1 turned off 08:44 Test GP1 changed to unavailable 08:43 Test GP1 turned off 08:43 Test GP1 changed to unavailable 08:37 Test GP1 turned off 08:37 Test GP1 changed to unavailable 08:32 Test GP1 turned off 08:32 Test GP1 changed to unavailable 08:27 Test GP1 turned off 08:27 Test GP1 changed to unavailable 08:22 Test GP1 turned off 08:22 Test GP1 changed to unavailable 08:17 Test GP1 turned off 08:17 Test GP1 changed to unavailable 08:12 Test GP1 turned off 08:12 Test GP1 changed to unavailable 08:07 Test GP1 turned off 08:07 Test GP1 changed to unavailable

aero83 commented 5 years ago

I am having same issue. Socket error every 5 minutes. Causes the relay to click, and the lamp to flash on every disconnection.

Sonoff Basic. Flashed bin file compiled from HASSio this morning, addon. Mosquitto broker.

HA log. Logbook

Showing entries for
February 12, 2019

Period
1 day

Entity
February 12, 2019
9:47 AM
Sonoff Basic Relay turned on
9:47 AM
Sonoff Basic Button turned off
9:47 AM
Sonoff Basic Relay changed to unavailable
9:47 AM
Sonoff Basic Button changed to unavailable
9:42 AM
Sonoff Basic Relay turned on
9:42 AM
Sonoff Basic Button turned off
9:42 AM
Sonoff Basic Relay changed to unavailable
9:42 AM
Sonoff Basic Button changed to unavailable
9:37 AM
Sonoff Basic Relay turned on
9:37 AM
Sonoff Basic Button turned off
9:37 AM
Sonoff Basic Relay changed to unavailable
9:37 AM
Sonoff Basic Button changed to unavailable
9:32 AM
Sonoff Basic Relay turned on
9:32 AM
Sonoff Basic Button turned off
9:32 AM
Sonoff Basic Relay changed to unavailable
9:32 AM
Sonoff Basic Button changed to unavailable
9:27 AM
Sonoff Basic Relay turned on
9:27 AM
Sonoff Basic Button turned off
9:27 AM
Sonoff Basic Relay changed to unavailable
**Mosquitto`` log**
2019-02-12T15:11:37.899736850Z 1549984297: New client connected from 192.168.10.135 as ripper_lamp-5ccf7f958d57 (c1, k15).

2019-02-12T15:16:49.571702120Z 1549984609: Socket error on client ripper_lamp-5ccf7f958d57, disconnecting.

2019-02-12T15:16:49.586663330Z 1549984609: New connection from 192.168.10.135 on port 1883.

2019-02-12T15:16:49.586681151Z 1549984609: New client connected from 192.168.10.135 as ripper_lamp-5ccf7f958d57 (c1, k15).

2019-02-12T15:22:01.135613692Z 1549984921: Socket error on client ripper_lamp-5ccf7f958d57, disconnecting.

2019-02-12T15:22:01.139857356Z 1549984921: New connection from 192.168.10.135 on port 1883.

2019-02-12T15:22:01.139869428Z 1549984921: New client connected from 192.168.10.135 as ripper_lamp-5ccf7f958d57 (c1, k15).

2019-02-12T15:27:11.697340263Z 1549985231: Socket error on client ripper_lamp-5ccf7f958d57, disconnecting.

2019-02-12T15:27:11.710693547Z 1549985231: New connection from 192.168.10.135 on port 1883.

2019-02-12T15:27:11.710711603Z 1549985231: New client connected from 192.168.10.135 as ripper_lamp-5ccf7f958d57 (c1, k15).

2019-02-12T15:32:22.240031053Z 1549985542: Socket error on client ripper_lamp-5ccf7f958d57, disconnecting.

2019-02-12T15:32:22.247380860Z 1549985542: New connection from 192.168.10.135 on port 1883.

2019-02-12T15:32:22.247496874Z 1549985542: New client connected from 192.168.10.135 as ripper_lamp-5ccf7f958d57 (c1, k15).

2019-02-12T15:37:33.086094060Z 1549985853: Socket error on client ripper_lamp-5ccf7f958d57, disconnecting.

2019-02-12T15:37:33.092104140Z 1549985853: New connection from 192.168.10.135 on port 1883.

2019-02-12T15:37:33.092255526Z 1549985853: New client connected from 192.168.10.135 as ripper_lamp-5ccf7f958d57 (c1, k15).

2019-02-12T15:42:43.702886966Z 1549986163: Socket error on client ripper_lamp-5ccf7f958d57, disconnecting.

2019-02-12T15:42:43.708544174Z 1549986163: New connection from 192.168.10.135 on port 1883.

2019-02-12T15:42:43.708591390Z 1549986163: New client connected from 192.168.10.135 as ripper_lamp-5ccf7f958d57 (c1, k15).

2019-02-12T15:47:54.243089073Z 1549986474: Socket error on client ripper_lamp-5ccf7f958d57, disconnecting.

2019-02-12T15:47:54.247188368Z 1549986474: New connection from 192.168.10.135 on port 1883.

2019-02-12T15:47:54.247371468Z 1549986474: New client connected from 192.168.10.135 as ripper_lamp-5ccf7f958d57 (c1, k15)
bk8190 commented 5 years ago

I'm having a similar problem. I use the HTTP API and my Home Assistant shows that all of my boards (Lolin D1 Mini) temporarily become "unavailable" about 20-30 times per day. They always reconnect within several seconds of becoming unavailable.

Here's a Home Assistant log snippet:

`2019-02-12 11:40:03 INFO (MainThread) [aioesphomeapi.client] 192.168.X.Y: Ping Failed!

2019-02-12 11:40:03 INFO (MainThread) [homeassistant.components.esphome] Disconnected from ESPHome API for 192.168.X.Y

2019-02-12 11:40:03 INFO (MainThread) [aioesphomeapi.client] 192.168.X.Y: Error while reading incoming messages: Error while receiving data: 0 bytes read on a total of 1 expected bytes

2019-02-12 11:40:03 INFO (MainThread) [homeassistant.components.esphome] Successfully connected to 192.168.X.Y `

Sometimes it happens to multiple devices at once, where multiple devices drop out at once and then rejoin several seconds later.

OttoWinter commented 5 years ago

The HA logbook logs are expected (see availability, you can turn that off). That's not the issue here.

The mosquitto logs unfortunately also do not contain much information.

The main issue is that the ESP SDK is kind of unstable for certain network setups. That's an external issue in espressif's (closed source) code and therefore we cannot do anything against that.

For the logs, what would help the most would be USB logs directly from the device. For connection issues you obviously won't get any good logs over the air, because there's not network connection.

@bk8190 Let's keep this thread here to MQTT only please.

Everybody, please edit your posts and put your logs into triple backticks (google markdown code blocks). It gets quite hard to read this thread otherwise.

Michael0yodi commented 5 years ago

What is the proper way to provide the necessary logs via usb?

aero83 commented 5 years ago

Got the chance to check serial debug. It seems to be rebooting with error below, with the whole log below. Is there something I have configured incorrectly in HA? I'm pretty new with it. 

[E][api:063]: No client connected to API. Rebooting...
[I][helpers:277]: Forcing a reboot... Reason: 'api'
[C][ota:461]: There have been 0 suspected unsuccessful boot attempts.
[I][application:053]: Running through setup()...
[C][binary_sensor.gpio:016]: Setting up GPIO binary sensor 'Sonoff Basic Button'...
[D][binary_sensor:027]: 'Sonoff Basic Button': Sending state OFF
[C][switch.gpio:023]: Setting up GPIO Switch 'Sonoff Basic Relay'...
[D][switch:055]: 'Sonoff Basic Relay': Sending state OFF
[C][output.esp8266_pwm:023]: Setting up ESP8266 PWM Output...
[C][light.state:149]: Setting up light 'Sonoff Basic Green LED'...
[C][wifi:029]: Setting up WiFi...
[D][wifi:260]: Starting scan...
[D][wifi:275]: Found networks:
[I][wifi:308]: - 'NSA' (2C:30:33:F6:EA:27) ▂▄▆█
[D][wifi:309]:     Channel: 6
[D][wifi:310]:     RSSI: -27 dB
[D][wifi:312]: - 'ATTwSINXi2' (C0:A0:0D:3C:B8:20) ▂▄▆█
[D][wifi:312]: - 'Banditmachine' (A4:56:CC:09:BB:9E) ▂▄▆█
[D][wifi:312]: - '' (A4:56:CC:09:BB:9F) ▂▄▆█
[D][wifi:312]: - '' (A4:56:CC:09:BB:A1) ▂▄▆█
[D][wifi:312]: - '' (B2:FC:0D:DC:D3:31) ▂▄▆█
[D][wifi:312]: - 'My home' (A4:56:CC:97:50:06) ▂▄▆█
[D][wifi:312]: - '' (A4:56:CC:97:50:07) ▂▄▆█
[D][wifi:312]: - '' (A4:56:CC:97:50:09) ▂▄▆█
[D][wifi:312]: - '' (A4:56:CC:97:50:0B) ▂▄▆█
[D][wifi:312]: - 'KKGNET' (C0:C1:C0:DC:6A:FD) ▂▄▆█
[D][wifi:312]: - 'Brent' (58:6D:8F:1D:BD:BB) ▂▄▆█
[D][wifi:312]: - 'NETGEAR81' (B0:B9:8A:3A:30:B3) ▂▄▆█
[D][wifi:312]: - '' (7A:E1:03:88:83:99) ▂▄▆█
[D][wifi:312]: - 'ATT2LKF634 2.4' (E0:22:02:56:08:ED) ▂▄▆█
[D][wifi:312]: - '87C883' (F8:F5:32:87:C8:83) ▂▄▆█
[D][wifi:312]: - 'WoodruffMesh' (50:0F:F5:37:5C:B9) ▂▄▆█
[I][wifi:179]: WiFi Connecting to 'NSA'...
[I][wifi:349]: WiFi connected!
[C][wifi:240]:   SSID: 'NSA'
[C][wifi:241]:   IP Address: 192.168.10.135
[C][wifi:243]:   BSSID: 2C:30:33:F6:EA:27
[C][wifi:245]:   Hostname: 'ripper_lamp'
[C][wifi:250]:   Signal strength: -39 dB ▂▄▆█
[C][wifi:251]:   Channel: 6
[C][wifi:252]:   Subnet: 255.255.255.0
[C][wifi:253]:   Gateway: 192.168.10.1
[C][wifi:254]:   DNS1: 192.168.10.10
[C][wifi:255]:   DNS2: 192.168.10.10
[C][api:023]: Setting up Home Assistant API server...
[C][ota:129]: Over-The-Air Updates:
[C][ota:130]:   Address: 192.168.10.135:8266
[C][ota:132]:   Using Password.
[C][mqtt.client:024]: Setting up MQTT...
[I][mqtt.client:170]: Connecting to MQTT...
[I][mqtt.client:209]: MQTT Connected!
[W][mqtt.client:384]: Publish failed for topic='ripper_lamp/switch/sonoff_basic_relay/state' will retry later..
[W][mqtt.client:384]: Publish failed for topic='ripper_lamp/light/sonoff_basic_green_led/state' will retry later..
[I][application:089]: setup() finished successfully!
[I][application:097]: You're running esphomelib v1.10.1 compiled on Feb 12 2019, 08:14:21
[C][wifi:341]: WiFi:
[C][wifi:240]:   SSID: 'NSA'
[C][wifi:241]:   IP Address: 192.168.10.135
[C][wifi:243]:   BSSID: 2C:30:33:F6:EA:27
[C][wifi:245]:   Hostname: 'ripper_lamp'
[C][wifi:250]:   Signal strength: -39 dB ▂▄▆█
[C][wifi:251]:   Channel: 6
[C][wifi:252]:   Subnet: 255.255.255.0
[C][wifi:253]:   Gateway: 192.168.10.1
[C][wifi:254]:   DNS1: 192.168.10.10
[C][wifi:255]:   DNS2: 192.168.10.10
[C][binary_sensor.gpio:023]: GPIO Binary Sensor 'Sonoff Basic Button'
[C][binary_sensor.gpio:024]:   Pin: GPIO0 (Mode: INPUT_PULLUP, INVERTED)
[C][switch.gpio:049]: GPIO Switch 'Sonoff Basic Relay'
[C][switch.gpio:050]:   Pin: GPIO12 (Mode: OUTPUT)
[C][switch.gpio:066]:   Restore Mode: Restore (Default to OFF)
[C][output.esp8266_pwm:028]: ESP8266 PWM:
[C][output.esp8266_pwm:029]:   Pin: GPIO13 (Mode: OUTPUT, INVERTED)
[C][output.esp8266_pwm:030]:   Frequency: 1000.0 Hz
[C][logger:099]: Logger:
[C][logger:100]:   Level: DEBUG
[C][logger:101]:   Log Baud Rate: 115200
[C][light.state:266]: Light 'Sonoff Basic Green LED'
[C][light.state:268]:   Default Transition Length: 1000 ms
[C][light.state:269]:   Gamma Correct: 2.80
[C][api:072]: API Server:
[C][api:073]:   Address: 192.168.10.135:6053
[C][ota:129]: Over-The-Air Updates:
[C][ota:130]:   Address: 192.168.10.135:8266
[C][ota:132]:   Using Password.
[C][mqtt.client:058]: MQTT:
[C][mqtt.client:060]:   Server Address: 192.168.10.45:1883 (192.168.10.45)
[C][mqtt.client:061]:   Username: ''
[C][mqtt.client:062]:   Client ID: 'ripper_lamp-5ccf7f958d57'
[C][mqtt.client:064]:   Discovery prefix: 'homeassistant'
[C][mqtt.client:065]:   Discovery retain: YES
[C][mqtt.client:067]:   Topic Prefix: 'ripper_lamp'
[C][mqtt.client:069]:   Log Topic: 'ripper_lamp/debug'
[C][mqtt.client:072]:   Availability: 'ripper_lamp/status'
[C][binary_sensor.mqtt:025]: MQTT Binary Sensor 'Sonoff Basic Button':
[C][binary_sensor.mqtt:026]:   State Topic: 'ripper_lamp/binary_sensor/sonoff_basic_button/state'
[C][switch.mqtt:048]: MQTT switch 'Sonoff Basic Relay':
[C][switch.mqtt:049]:   State Topic: 'ripper_lamp/switch/sonoff_basic_relay/state'
[C][switch.mqtt:049]:   Command Topic: 'ripper_lamp/switch/sonoff_basic_relay/command'
[C][light.mqtt_json:072]: MQTT Light 'Sonoff Basic Green LED':
[C][light.mqtt_json:073]:   State Topic: 'ripper_lamp/light/sonoff_basic_green_led/state'
[C][light.mqtt_json:073]:   Command Topic: 'ripper_lamp/light/sonoff_basic_green_led/command'
[I][application:114]: Running through first loop()
[I][application:141]: First loop finished successfully!
[I][ota:154]: Boot seems successful, resetting boot loop counter.
[E][api:063]: No client connected to API. Rebooting...
[I][helpers:277]: Forcing a reboot... Reason: 'api'
[W][wifi:727]: Event: Disconnected ssid='NSA' bssid=2C:30:33:F6:EA:27 reason='Association Leave'

 ets Jan  8 2013,rst cause:1, boot mode:(3,7)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
vbb28d4a3
~ld
   [I][logger:071]: Log initialized
[C][ota:461]: There have been 0 suspected unsuccessful boot attempts.
[I][application:053]: Running through setup()...
[C][binary_sensor.gpio:016]: Setting up GPIO binary sensor 'Sonoff Basic Button'...
[D][binary_sensor:027]: 'Sonoff Basic Button': Sending state OFF
[C][switch.gpio:023]: Setting up GPIO Switch 'Sonoff Basic Relay'...
[D][switch:055]: 'Sonoff Basic Relay': Sending state OFF
[C][output.esp8266_pwm:023]: Setting up ESP8266 PWM Output...
[C][light.state:149]: Setting up light 'Sonoff Basic Green LED'...
[C][wifi:029]: Setting up WiFi...
[D][wifi:260]: Starting scan...
[D][wifi:275]: Found networks:
[I][wifi:308]: - 'NSA' (2C:30:33:F6:EA:27) ▂▄▆█
[D][wifi:309]:     Channel: 6
[D][wifi:310]:     RSSI: -32 dB
[D][wifi:312]: - 'ATTwSINXi2' (C0:A0:0D:3C:B8:20) ▂▄▆█
[D][wifi:312]: - '' (A4:56:CC:97:50:0B) ▂▄▆█
[D][wifi:312]: - '' (B2:FC:0D:DC:D3:31) ▂▄▆█
[D][wifi:312]: - 'Banditmachine' (A4:56:CC:09:BB:9E) ▂▄▆█
[D][wifi:312]: - '' (A4:56:CC:97:50:07) ▂▄▆█
[D][wifi:312]: - 'KKGNET' (C0:C1:C0:DC:6A:FD) ▂▄▆█
[D][wifi:312]: - '' (A4:56:CC:09:BB:9F) ▂▄▆█
[D][wifi:312]: - '' (A4:56:CC:09:BB:A1) ▂▄▆█
[D][wifi:312]: - 'Brent' (58:6D:8F:1D:BD:BB) ▂▄▆█
[D][wifi:312]: - '87C883' (F8:F5:32:87:C8:83) ▂▄▆█
[D][wifi:312]: - 'ATT2LKF634 2.4' (E0:22:02:56:08:ED) ▂▄▆█
[D][wifi:312]: - '' (7A:E1:03:88:83:99) ▂▄▆█
[D][wifi:312]: - 'ATTzFMdai2' (90:9D:7D:41:D1:C0) ▂▄▆█
[D][wifi:312]: - 'ATT7ISq6Ef' (DC:7F:A4:35:DF:49) ▂▄▆█
[I][wifi:179]: WiFi Connecting to 'NSA'...
[I][wifi:349]: WiFi connected!
[C][wifi:240]:   SSID: 'NSA'
[C][wifi:241]:   IP Address: 192.168.10.135
[C][wifi:243]:   BSSID: 2C:30:33:F6:EA:27
[C][wifi:245]:   Hostname: 'ripper_lamp'
[C][wifi:250]:   Signal strength: -41 dB ▂▄▆█
[C][wifi:251]:   Channel: 6
[C][wifi:252]:   Subnet: 255.255.255.0
[C][wifi:253]:   Gateway: 192.168.10.1
[C][wifi:254]:   DNS1: 192.168.10.10
[C][wifi:255]:   DNS2: 192.168.10.10
[C][api:023]: Setting up Home Assistant API server...
[C][ota:129]: Over-The-Air Updates:
[C][ota:130]:   Address: 192.168.10.135:8266
[C][ota:132]:   Using Password.
[C][mqtt.client:024]: Setting up MQTT...
[I][mqtt.client:170]: Connecting to MQTT...
[I][mqtt.client:209]: MQTT Connected!
[W][mqtt.client:384]: Publish failed for topic='homeassistant/light/ripper_lamp/sonoff_basic_green_led/config' will retry later..
[I][application:089]: setup() finished successfully!
[I][application:097]: You're running esphomelib v1.10.1 compiled on Feb 12 2019, 08:14:21
[C][wifi:341]: WiFi:
[C][wifi:240]:   SSID: 'NSA'
[C][wifi:241]:   IP Address: 192.168.10.135
[C][wifi:243]:   BSSID: 2C:30:33:F6:EA:27
[C][wifi:245]:   Hostname: 'ripper_lamp'
[C][wifi:250]:   Signal strength: -43 dB ▂▄▆█
[C][wifi:251]:   Channel: 6
[C][wifi:252]:   Subnet: 255.255.255.0
[C][wifi:253]:   Gateway: 192.168.10.1
[C][wifi:254]:   DNS1: 192.168.10.10
[C][wifi:255]:   DNS2: 192.168.10.10
[C][binary_sensor.gpio:023]: GPIO Binary Sensor 'Sonoff Basic Button'
[C][binary_sensor.gpio:024]:   Pin: GPIO0 (Mode: INPUT_PULLUP, INVERTED)
[C][switch.gpio:049]: GPIO Switch 'Sonoff Basic Relay'
[C][switch.gpio:050]:   Pin: GPIO12 (Mode: OUTPUT)
[C][switch.gpio:066]:   Restore Mode: Restore (Default to OFF)
[C][output.esp8266_pwm:028]: ESP8266 PWM:
[C][output.esp8266_pwm:029]:   Pin: GPIO13 (Mode: OUTPUT, INVERTED)
[C][output.esp8266_pwm:030]:   Frequency: 1000.0 Hz
[C][logger:099]: Logger:
[C][logger:100]:   Level: DEBUG
[C][logger:101]:   Log Baud Rate: 115200
[C][light.state:266]: Light 'Sonoff Basic Green LED'
[C][light.state:268]:   Default Transition Length: 1000 ms
[C][light.state:269]:   Gamma Correct: 2.80
[C][api:072]: API Server:
[C][api:073]:   Address: 192.168.10.135:6053
[C][ota:129]: Over-The-Air Updates:
[C][ota:130]:   Address: 192.168.10.135:8266
[C][ota:132]:   Using Password.
[C][mqtt.client:058]: MQTT:
[C][mqtt.client:060]:   Server Address: 192.168.10.45:1883 (192.168.10.45)
[C][mqtt.client:061]:   Username: ''
[C][mqtt.client:062]:   Client ID: 'ripper_lamp-5ccf7f958d57'
[C][mqtt.client:064]:   Discovery prefix: 'homeassistant'
[C][mqtt.client:065]:   Discovery retain: YES
[C][mqtt.client:067]:   Topic Prefix: 'ripper_lamp'
[C][mqtt.client:069]:   Log Topic: 'ripper_lamp/debug'
[C][mqtt.client:072]:   Availability: 'ripper_lamp/status'
[C][binary_sensor.mqtt:025]: MQTT Binary Sensor 'Sonoff Basic Button':
[C][binary_sensor.mqtt:026]:   State Topic: 'ripper_lamp/binary_sensor/sonoff_basic_button/state'
[C][switch.mqtt:048]: MQTT switch 'Sonoff Basic Relay':
[C][switch.mqtt:049]:   State Topic: 'ripper_lamp/switch/sonoff_basic_relay/state'
[C][switch.mqtt:049]:   Command Topic: 'ripper_lamp/switch/sonoff_basic_relay/command'
[C][light.mqtt_json:072]: MQTT Light 'Sonoff Basic Green LED':
[C][light.mqtt_json:073]:   State Topic: 'ripper_lamp/light/sonoff_basic_green_led/state'
[C][light.mqtt_json:073]:   Command Topic: 'ripper_lamp/light/sonoff_basic_green_led/command'
[I][application:114]: Running through first loop()
[I][application:141]: First loop finished successfully!
[I][ota:154]: Boot seems successful, resetting boot loop counter.
OttoWinter commented 5 years ago

@aero83 You have both mqtt and api enabled. When no client connects to the native api within 5 minutes a watchdog kicks in and reboots the device. Please disable the native api if you don't use it.

Michael0yodi commented 5 years ago

@OttoWinter Disabling API solved my issue. I did not reflect on this setting since (If I recall correctly) it where added in the guide when creating the initial configuration, even if stated in the documentation that it force a reboot every 5 minute, perhaps this can be further elaborated somehow or not included as default in the generated .yaml, anyway thanks for the support! :)

aero83 commented 5 years ago

Thank you. Solved issue, thought it might be a noob mistake.

OttoWinter commented 5 years ago

Ok then, I guess this issue can be closed then because the issue has been resolved.

For documentation: A PR in the docs repo to add a note would be welcome :)