Need your help... after ESPhome 2024.10.2 Update it gone "offline" and can't get it work.

[OwlBawl]

Can see it as WiFi client in router but ESPhome dont establish connection, web portal not working also. First symptom after update was False "Regen start / Regen end" with "binary_sensor.clack_block_regen" active Reseted it with "button.clack_test_button_regen_stop" to restore work, then rebooted the esp32 and thats all. Tried upload recompiled firmware via OTA but also no luck...

[thedudefxp]

Does he get ip ? i had some thing last time its was lost the information in secrets.yalm. It show on router wifi but no ip lease

[fonske]

I have just updated with the newest version of esphome but everything works.

Do you use the correct github branch for your model? See readme. main: Clack WS PI valve (DiscValve) (ECOSOFT LESS-10 / 15 / 20 from AQMOS) ws1: Clack WS1 valve (CM(x) from AQMOS) ws1_usa: Clack WS1 valve with Gallons and Inches / US version See if you have a TOF1 or TOF2 version of the sensor (see readme) and setting in the clack.yaml https://github.com/fonske/clack-reader-v4/blob/ws1/readme/clack_explanation_en.md

And check secrets.yaml indeed if correct setting for your wifi

[OwlBawl]

I even don't use github branch, just compiled the same from my local copy 'include'... because i've made some custom distance changes previously

[OwlBawl]

As i see arduino framework also updated recently... maybe that's the problem also... don't know

[OwlBawl]

Does he get ip ? i had some thing last time its was lost the information in secrets.yalm. It show on router wifi but no ip lease

yes, it receives IP from router and router even ping it tries ping from HA terminal successfully also.

[OwlBawl]

recompiled using exteranal git component - also not API connection.... while pinging

[fonske]

Is your TOF sensor connected? Otherwise you could have reboots best to have it on Clack power and not usb, for clack reader V4 warning: do not connect or disconnect any power cables when power is on.

[OwlBawl]

Would check, but didn't touch it It connectecd with cable to Clack reader, and clack reader powered by Clack 15V? (as i remember voltage)

[fonske]

Yes i think its correct https://github.com/fonske/clack-reader-v4/blob/ws1/readme/Clack_reader_v4.1_connections_on_clack_ws1.pdf

[OwlBawl]

TOF cords are connected... It sent false Regen start at night (the regen is scheduled on 14:00 at day, and resourse wasn't used yet for regen) co

In HA from same 3:20 sensors resetet to 0 as it was regen, and from 5:10 all entities became unavailable... I succesfully rebooted it once in the morning 8:15 and it established API connection, and after 9:10 it gone offline till now...

Made few OTA updates already, rebotted my Unifi router and AP's... reboted HA and so on.

[OwlBawl]

Yes i think its correct https://github.com/fonske/clack-reader-v4/blob/ws1/readme/Clack_reader_v4.1_connections_on_clack_ws1.pdf

yes, it's connected from the beginning as it should and worked almost 2 mnths so (from ~9.09.24) But yes, anything could happen ofcourse

[OwlBawl]

the only thing I changed in code - was https://github.com/fonske/clack-reader-v4/issues/1 whan i found it, so nothing modified then. Oh! and changed from

time:
  - platform: sntp
    id: sntp_time
    timezone: ${timezone}
    # Enable this with your own NTP server if your device is on a no internet IOT lan. 
    #servers: 192.168.X.X
  #   servers:
  #    - 0.pool.ntp.org
  #    - 1.pool.ntp.org
  #    - 2.pool.ntp.org   

to 

time:
  - platform: homeassistant
    id: sntp_time
    timezone: ${timezone}

because i somewhy had 1 jan dates on all regens.

But also about 2 weeks ago and worked fine

[OwlBawl]

But as i see in router history - it don't powercycle. it connects to wifi and that's all I can use captivate_portal for OTA blocking it from WiFi connection but web_portal not responsive

[fonske]

Maybe you can try a basic configuration first on the Atom https://github.com/fonske/clack-reader-v4/blob/ws1/esphome/clack_test.yaml

To see if a tof sensor connection is a problem or not (reboots when there is a problem with it)

[OwlBawl]

That's seems good. I can open web portal, can see it in ESPhome now

Should I wait for reboots some time?

[OwlBawl]

INFO ESPHome 2024.10.2
INFO Reading configuration /config/esphome/clack-reader-v4.yaml...
WARNING GPIO35 is used by the PSRAM interface on ESP32-S3R8 / ESP32-S3R8V and should be avoided on these models
INFO Starting log output from 10.10.20.213 using esphome API
INFO Successfully connected to clack-test @ 10.10.20.213 in 0.066s
INFO Successful handshake with clack-test @ 10.10.20.213 in 0.019s
[21:22:29][I][app:100]: ESPHome version 2024.10.2 compiled on Oct 24 2024, 21:17:59
[21:22:29][C][wifi:600]: WiFi:
[21:22:29][C][wifi:428]:   Local MAC: 34:B7:DA:57:3B:40
[21:22:29][C][wifi:433]:   SSID: 'daad.iot'[redacted]
[21:22:29][C][wifi:436]:   IP Address: 10.10.20.213
[21:22:29][C][wifi:440]:   BSSID: 7A:45:58:17:ED:C1[redacted]
[21:22:29][C][wifi:441]:   Hostname: 'clack-test'
[21:22:29][C][wifi:443]:   Signal strength: -60 dB ▂▄▆█
[21:22:29][C][wifi:447]:   Channel: 6
[21:22:29][C][wifi:448]:   Subnet: 255.255.255.0
[21:22:29][C][wifi:449]:   Gateway: 10.10.20.1
[21:22:29][C][wifi:450]:   DNS1: 10.10.20.1
[21:22:29][C][wifi:451]:   DNS2: 0.0.0.0
[21:22:29][C][logger:185]: Logger:
[21:22:29][C][logger:186]:   Level: DEBUG
[21:22:29][C][logger:188]:   Log Baud Rate: 0
[21:22:29][C][logger:189]:   Hardware UART: USB_CDC
[21:22:29][C][logger:193]:   Level for 'esp32.preferences': DEBUG
[21:22:29][C][logger:193]:   Level for 'sensor': DEBUG
[21:22:29][C][logger:193]:   Level for 'text_sensor': DEBUG
[21:22:29][C][logger:193]:   Level for 'switch': DEBUG
[21:22:29][C][logger:193]:   Level for 'button': DEBUG
[21:22:29][C][logger:193]:   Level for 'number': DEBUG
[21:22:29][C][logger:193]:   Level for 'component': ERROR
[21:22:29][C][uptime.sensor:033]: Uptime Sensor 'clack_uptime'
[21:22:29][C][uptime.sensor:033]:   Device Class: 'duration'
[21:22:29][C][uptime.sensor:033]:   State Class: 'total_increasing'
[21:22:29][C][uptime.sensor:033]:   Unit of Measurement: 'days'
[21:22:29][C][uptime.sensor:033]:   Accuracy Decimals: 1
[21:22:29][C][uptime.sensor:033]:   Icon: 'mdi:timer-outline'
[21:22:29][C][uptime.sensor:034]:   Type: Seconds
[21:22:29][C][esp32_rmt_led_strip:187]: ESP32 RMT LED Strip:
[21:22:29][C][esp32_rmt_led_strip:188]:   Pin: 35
[21:22:29][C][esp32_rmt_led_strip:189]:   Channel: 1
[21:22:29][C][esp32_rmt_led_strip:214]:   RGB Order: GRB
[21:22:29][C][esp32_rmt_led_strip:215]:   Max refresh rate: 0
[21:22:29][C][esp32_rmt_led_strip:216]:   Number of LEDs: 4
[21:22:29][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'esp_button'
[21:22:29][C][gpio.binary_sensor:016]:   Pin: GPIO41
[21:22:29][C][light:103]: Light 'Led'
[21:22:29][C][light:105]:   Default Transition Length: 1.0s
[21:22:29][C][light:106]:   Gamma Correct: 2.80
[21:22:29][C][version.text_sensor:021]: Version Text Sensor 'clack_version'
[21:22:29][C][version.text_sensor:021]:   Icon: 'mdi:new-box'
[21:22:29][C][restart.button:017]: Restart Button 'ESP restart'
[21:22:29][C][restart.button:017]:   Icon: 'mdi:restart'
[21:22:29][C][captive_portal:089]: Captive Portal:
[21:22:29][C][web_server:153]: Web Server:
[21:22:29][C][web_server:154]:   Address: clack-test.local:80
[21:22:29][C][sntp:048]: SNTP Time:
[21:22:29][C][sntp:049]:   Server 1: '0.pool.ntp.org'
[21:22:29][C][sntp:050]:   Server 2: '1.pool.ntp.org'
[21:22:29][C][sntp:051]:   Server 3: '2.pool.ntp.org'
[21:22:29][C][sntp:052]:   Timezone: 'EET-2EEST,M3.5.0/3,M10.5.0/4'
[21:22:29][C][mdns:116]: mDNS:
[21:22:29][C][mdns:117]:   Hostname: clack-test
[21:22:29][C][esphome.ota:073]: Over-The-Air updates:
[21:22:29][C][esphome.ota:074]:   Address: clack-test.local:3232
[21:22:29][C][esphome.ota:075]:   Version: 2
[21:22:29][C][safe_mode:018]: Safe Mode:
[21:22:29][C][safe_mode:020]:   Boot considered successful after 60 seconds
[21:22:29][C][safe_mode:021]:   Invoke after 10 boot attempts
[21:22:29][C][safe_mode:023]:   Remain in safe mode for 300 seconds
[21:22:29][C][api:140]: API Server:
[21:22:29][C][api:141]:   Address: clack-test.local:6053
[21:22:29][C][api:145]:   Using noise encryption: NO
[21:22:29][C][wifi_signal.sensor:010]: WiFi Signal 'clack_wifi_signal_db'
[21:22:29][C][wifi_signal.sensor:010]:   Device Class: 'signal_strength'
[21:22:29][C][wifi_signal.sensor:010]:   State Class: 'measurement'
[21:22:29][C][wifi_signal.sensor:010]:   Unit of Measurement: 'dBm'
[21:22:29][C][wifi_signal.sensor:010]:   Accuracy Decimals: 0
[21:22:29][C][wifi_info:010]: WifiInfo IPAddress 'Clack IP'
[21:22:29][C][wifi_info:010]:   Icon: 'mdi:ip-network'
[21:22:34][D][sensor:094]: 'clack_wifi_signal_db': Sending state -59.00000 dBm with 0 decimals of accuracy
[21:23:34][D][sensor:094]: 'clack_wifi_signal_db': Sending state -59.00000 dBm with 0 decimals of accuracy
[21:24:34][D][sensor:094]: 'clack_wifi_signal_db': Sending state -58.00000 dBm with 0 decimals of accuracy

[OwlBawl]

I begin supposing it's kinda weird IP network problem, the only thing changed - dynamic IP adress and so new IP while other 11 esp's are working fine damn it Will try to disable IP static for test in main config

[fonske]

The reboots happen when there is a problem with the tof sensor or the connection to it. And you wont be able to see the ESP or the entities in home assistant. They become unavailable.

You could connect a tof sensor directly to the grove port on the atom and see for some log messages about i2c

i2c:
  - id: bus_a
    sda: GPIO2
    scl: GPIO1
    frequency: 800kHz
    timeout: 50ms

[OwlBawl]

I begin supposing it's kinda weird IP network problem, the only thing changed - dynamic IP adress and so new IP while other 11 esp's are working fine damn it Will try to disable IP static for test in main config

nope, just as I swithced back to my main config without static IP - API / Log unavailable again Would write your test config till tomorrow and have a rest for today.

[OwlBawl]

ok, so on the test firmware it worked last 12 hours with uptime Should i then switch tof to grove and see logs?

[OwlBawl]

hmm

added this to test.yaml

i2c:

• id: bus_a sda: GPIO2 scl: GPIO1 frequency: 800kHz timeout: 50ms

connected tof via cable extender I use - WiFi up, but no API connected tof via short cable without extender to m5stack - Wifi up, API ok, log NOT ok as I understand:

[10:10:54][C][i2c.arduino:071]: I2C Bus:
[10:10:54][C][i2c.arduino:072]:   SDA Pin: GPIO2
[10:10:54][C][i2c.arduino:073]:   SCL Pin: GPIO1
[10:10:54][C][i2c.arduino:074]:   Frequency: 800000 Hz
[10:10:54][C][i2c.arduino:077]:   Timeout: 50 ms
[10:10:54][C][i2c.arduino:086]:   Recovery: bus successfully recovered
[10:10:54][I][i2c.arduino:096]: Results from i2c bus scan:
[10:10:54][I][i2c.arduino:098]: Found no i2c devices!

And so i took of TOF and disassembled it... It definitely doesn't like place it should leave in ))

[OwlBawl]

I'll try to clear it and test then, but, anyway, Would appreciate if you can help me to comment out all ToF related stuff to just use / test reader without ToF (anyway with my small tank it's not so necessary for now, but need to monitor regen / block regen and so on)

[fonske]

I will try this weekend to change the code for you. Will take some time to check and adjust

[fonske]

Hi @OwlBawl

Can you try this version? branch ws1_no_tof https://github.com/fonske/clack-reader-v4/blob/ws1_no_tof/esphome/clack.yaml

The TOF sensor is taken out of the code I have tested it without the TOF sensor connected and the ESP works and entity's are visible.

[OwlBawl]

Thank you so much! It works

All this problems really were because of ToF death so. So glad to see it online again after two days of findings )

[OwlBawl]

As i understand this ones are also unusable without ToF? sensor.clack_fill_salt button.clack_reset_fill_salt '#' them in lovelace. Maybe I would order ToF later or leave it as is, counting my conditions of use. Thank you for your help.

[fonske]

I can 3d print also a sensor housing that fits ON the cover, maybe thats a bit more protected, when filling new salt, as the cover is taken off already.

Just let me know if that would be a better solution for you.

[OwlBawl]

Thank you, you can just share the 3D model and I'll print it somewhere locally not to bother you and eliminate post expenses if it ok.

[fonske]

Ok thats fine. I placed a copy here https://github.com/fonske/clack-reader-v4/blob/ws1_no_tof/readme/Clack%20Tof%20Holder.stl