local deck keeps dropping pings. I can't get it to stay on the network

jakeman

Hello,

I set up my local deck today but sadly after turning it off and back on to move it to a different location I just can’t get it to stay on wifi. I am running a ping to its ip address and after rebooting it, a few pings respond but then it drops off the network. Any idea what I can do? I read somewhere that it could be due to RF interference. I have a lot of Zigbee devices around so maybe that’s it? Does the local deck work on 5GHz wifi? I keep rebooting it so that I can change test it on 5GHz SSID, but I can’t get it stable for long enough to update and try before it drops off.

Any ideas?

Thanks!

jakeman

another question, how can I reset this to factory default so that I can start over? I have a feeling that after trying for hours to get it to work it may be sensible to start fresh.

Thanks!

jakeman

So I gather that one has to flash this
https://github.com/LocalBytes/localdeck-config/blob/main/packages/localdeck-codegen/esphome-localdeck.yaml
To bring it to factory defaults?

I have done that, how can I get back to the stage where I can follow this video? (Adam’s video about setting up local deck for the first time)

the local deck does not appear under Devices and Services to be provisoned by Bluetooth.

Anyway, thanks again, after 5 hours, im going to sleep

jakeman

I restored HA from Backup, flashed the localdeck github ymal to the device via usb cable, and I’m back to square one. Every time I restart the local deck, the device responds to 2-3 pings and then it disconnects.

Logs have this in a loop
WARNING Can’t connect to ESPHome API for localdeck: Error resolving IP address: [Errno -5] No address associated with hostname (APIConnectionError)
INFO Trying to connect to localdeck in the background

sometimes it connects for a few seconds, and it drops off again.

I’m going to leave it for the time being, I don’t think I can do anything else, if anyone has an idea that would be super apprecieated, this device is so nice, I hope I can start using it soon 🙂

RebeccaH

Hi @jakeman

Sorry to read your LocalDeck isn’t working as expected!

Well done for flashing via USB. Can you confirm if your LocalDeck shows up in your router settings? This would give me an idea if it’s struggling to connect to the network or just Home Assistant.

jakeman

RebeccaH

Hello RebeccaH
Thanks for responding. It does show up in my router’s DHCP leases but only during the times when it briefly connects. I am sending a continuous ping to the LocalDeck’s IP address (I made a DHCP reservation on the router so that it is always given the same IP) and during the time when a few pings respond, I can see it on the router (not that it is relevant but for completeness sake I am using a pfSense router). Today it stayed online for about 15 minutes, and I was able to use the LocalDeck’s buttons to turn LocalBytes Tasmota plugs on and off, this is the longest it stayed online so far.

jakeman

Maybe this will give a clue, the LocalDeck randomly started working (It has been plugged in the whole time and I saw the the lights came on.) everything was working fine for a day until I went to ESP Home Builder and clicked View Logs - Wirelessly. The moment I did that the connection dropped and I can’t reconnect again.

jakeman

just to report in case others are having similar issues, this seems to have made it more stable

wifi:
  # ...
  power_save_mode: none

but the above will only be accepted if the code below is commented out

output:
  - platform: template
    id: improv_status
    type: binary
    write_action:
      - light.control:
          id: keypad_button_01_light
          state: !lambda return state;
esp32_improv:
  status_indicator: improv_status
  authorizer: keypad_button_01

this is as detailed by @AAllport
in this thread: https://forum.mylocalbytes.com/d/63-localdeck-disconnects-sending-keepalive-failed/

RebeccaH

Hi @jakeman

Really glad those changes have made it more reliably stay on your network. And thanks for sharing the fix!

If you do encounter issues again, please reach back out.