ESPHome logs flooded with on and off states

fskelly

With my Local Deck i get my log filled with this
Time level Tag Message
11:38:54 [D] [binary_sensor:036]
‘keypad_row_03’: Sending state OFF
11:38:54 [D] [binary_sensor:036]
‘keypad_row_21’: Sending state ON
11:38:54 [D] [binary_sensor:036]
‘keypad_row_03’: Sending state ON
11:38:54 [D] [binary_sensor:036]
‘keypad_row_21’: Sending state OFF
11:38:54 [D] [binary_sensor:036]
‘keypad_row_03’: Sending state OFF
11:38:54 [D] [binary_sensor:036]
‘keypad_row_21’: Sending state ON
11:38:54 [D] [binary_sensor:036]
‘keypad_row_03’: Sending state ON
11:38:54 [D] [binary_sensor:036]
‘keypad_row_21’: Sending state OFF
11:38:54 [D] [binary_sensor:036]
‘keypad_row_03’: Sending state OFF
11:38:54 [D] [binary_sensor:036]
‘keypad_row_21’: Sending state ON
11:38:55 [D] [binary_sensor:036]
‘keypad_row_03’: Sending state ON
11:38:55 [D] [api.connection:1375]
Home Assistant 2024.7.3 (192.168.178.251): Connected successfully
11:38:55 [D] [binary_sensor:036]
‘keypad_row_21’: Sending state OFF
11:38:55 [D] [binary_sensor:036]
‘keypad_row_03’: Sending state OFF
11:38:55 [D] [binary_sensor:036]
‘keypad_row_21’: Sending state ON
11:38:55 [D] [binary_sensor:036]
‘keypad_row_03’: Sending state ON
11:38:55 [D] [binary_sensor:036]
‘keypad_row_21’: Sending state OFF
11:38:55 [D] [binary_sensor:036]
‘keypad_row_03’: Sending state OFF
11:38:55 [D] [binary_sensor:036]
‘keypad_row_07’: Sending state OFF
11:38:55 [D] [binary_sensor:036]
‘keypad_row_21’: Sending state ON
11:38:55 [D] [binary_sensor:036]
‘keypad_row_03’: Sending state ON
11:38:55 [D] [binary_sensor:036]
‘keypad_row_07’: Sending state ON
11:38:55 [D] [binary_sensor:036]
‘keypad_row_21’: Sending state OFF

And then the device reboots and I loose connectivity, get the device to be stable and actually work is a case of unplug, re-plug, reset and a lot of hoping and praying. What am i doing wrong?

jhopple

I have been seeing this also, but without the reboot.
If I don’t touch the device it stops, when I start to touch it or move the device it starts again.

AAllport

The log-spam is a known quirk, but can easily mask the actual issue at play.
As a debugging step, I’d be tempted to disable the sensor so you can see if there are any other issues happening.

matrix_keypad:
  id: keypad
  keys: ABCDEFGHIJKLMNOPQRSTUVWX
  rows:
    - pin:
        number: GPIO21
#        allow_other_uses: true
    - pin:
        number: GPIO20
#        allow_other_uses: true
    - pin:
        number: GPIO3
#        allow_other_uses: true
    - pin:
        number: GPIO7
#        allow_other_uses: true
  columns:
    - pin:
        number: GPIO0
        drive_strength: 5mA
    - pin:
        number: GPIO1
        drive_strength: 5mA
    - pin:
        number: GPIO10
        drive_strength: 5mA
    - pin:
        number: GPIO4
        drive_strength: 5mA
    - pin:
        number: GPIO5
        drive_strength: 5mA
    - pin:
        number: GPIO6
        drive_strength: 5mA
binary_sensor:
#  - platform: gpio
#    id: keypad_row_21
#    pin:
#      number: GPIO21
#      allow_other_uses: true
#  - platform: gpio
#    id: keypad_row_20
#    pin:
#      number: GPIO20
#      allow_other_uses: true
#  - platform: gpio
#    id: keypad_row_03
#    pin:
#      number: GPIO3
#      allow_other_uses: true
#  - platform: gpio
#    id: keypad_row_07
#    pin:
#      number: GPIO7
#      allow_other_uses: true

Given I can see the Connected Successfully line, I’m shocked that it’s not showing in Connected in HomeAssistant.

Nb: We’ve issued a PR here, which should fix the log spam
https://github.com/esphome/esphome/pull/7163

jhopple

Disabling the binary sensors does kill the log spam and I don’t see any other issues in the log.

AAllport

Sorry, this slipped through the net…
So, once you’ve disabled the binary sensors, is the device staying connected to the WiFi?

If it’s dropping connection, you should see some log output (when plugged in over USB), which will shed more light on the matter.
Failing that, you may find it helpful to disable the WiFi Power Save, you can find info here - LocalDeck Disconnects - Sending keepalive failed

MichaelMKKelly

I saw this log spam and interestingly it seems to happen when viewing logs via wifi and after a while the connection drops and it needs rebooting. however I did not see the same problem if i monitored logs via usb and things seemed to remain stable, but as soon as I connect to the logging via wifi i get spam and a disconnect shortly thereafter.

device seems to be still up but wifi has just stopped working. shortly after usb output starts showing keepalive fails (i assume because wifi is down)

perhaps some kind of interference from the wifi is causing states to rapidly change? or maybe its an issue with the logger?

or perhaps my observation is just coincidence perhaps someone else could try to replicate?

rdeangelis

My LocalDeck wifi doesn’t always work either, and like Michael above I’m certain to lose connection if I view the logs via wifi from ESPhome. In addition the wifi issue is pretty much always present.,

I manage to get it connected to wifi at times and it works for long periods of time but If I disconnect and reconnect it chances are it won’t manage to connect.
It’s pretty much random wether it successfully connects to wifi or not.

Also everytime I re-flash it via wifi it connects and starts logging and immediately drops (when it works).

I have to flash it via usb to get it going again but doesn’t always connect. :

AAllport

Just wanted to check in here.

RE the log-spam… this underlying issue has been fixed in ESPHome 2024.08 esphome/esphome#7163.
We’ll be pushing out changes to remove the log spam when it’s released.

In short, the matrix_keypad component didn’t correctly set up the pins, so we used a binary sensor to fix things.
The downside is that it floods the logs.
That said, this in itself will not cause an issue with the LocalDeck functionality/WiFi

If you’re seeing issues with WiFi connectivity, you’ll want to take a look at this thread - https://forum.mylocalbytes.com/d/63
TLDR:

wifi:
  power_save_mode: NONE

Hope this helps!

AAllport

Just a heads up,

Our PR has just been released under ESPHome 2024.08.

We’ll be looking to update the configurator 🔜 to make the aforementioned updates that will remove the log spam.
This should land in Configurator v0.6, but may be a week or two out!