I finally got the deck working after giving up for a few months.
however when i make a change in configurator and push it through esp home, it shows as all being good, but the deck becomes unresponsive.
sometimes powering it off and on again gets it to work, other times like right now it just becomes a paper weight, i see the LED strip test flash but i get no ping and all the entities in HA become unavailable.
I really want to love this but so far it’s been nothing but pain, please help.
Hi @llama ,
Sorry to hear you are having issues. We have had one or two instances where the power supply we shipped with the localdecks did not supply enough power. Could you please try with a different power supply? If the one we shipped you is at fault, we will, of course, replace it for you; but this will help determine if the power supply is at fault.
So with the original power supply connected, i get two pings on a reboot then it goes unreachable
[core-ssh ~]$ ping 192.168.10.114
PING 192.168.10.114 (192.168.10.114): 56 data bytes
64 bytes from 192.168.10.114: seq=24 ttl=62 time=42.116 ms
64 bytes from 192.168.10.114: seq=25 ttl=62 time=66.383 ms
^C
--- 192.168.10.114 ping statistics ---
141 packets transmitted, 2 packets received, 98% packet loss
round-trip min/avg/max = 42.116/54.249/66.383 ms
any thoughts? I can’t use it because it simply does not stay connected to the network.
Reading CMake configuration...
Dependency Graph
|-- ArduinoJson @ 6.18.5
|-- Improv @ 1.2.4
RAM: [= ] 14.4% (used 47244 bytes from 327680 bytes)
Flash: [========= ] 87.0% (used 1595548 bytes from 1835008 bytes)
========================= [SUCCESS] Took 63.55 seconds =========================
INFO Successfully compiled program.
INFO Connecting to 192.168.10.114 port 3232...
ERROR Connecting to 192.168.10.114 port 3232 failed: timed out
ERROR Connection failed.[core-ssh custom_components]$ ping 192.168.10.114
PING 192.168.10.114 (192.168.10.114): 56 data bytes
64 bytes from 192.168.10.114: seq=35 ttl=62 time=59.066 ms
64 bytes from 192.168.10.114: seq=56 ttl=62 time=131.545 ms
64 bytes from 192.168.10.114: seq=66 ttl=62 time=53.612 ms
64 bytes from 192.168.10.114: seq=67 ttl=62 time=74.965 ms
64 bytes from 192.168.10.114: seq=68 ttl=62 time=97.622 ms
64 bytes from 192.168.10.114: seq=69 ttl=62 time=19.083 ms
64 bytes from 192.168.10.114: seq=70 ttl=62 time=41.414 ms
64 bytes from 192.168.10.114: seq=71 ttl=62 time=63.583 ms
64 bytes from 192.168.10.114: seq=72 ttl=62 time=87.834 ms
64 bytes from 192.168.10.114: seq=73 ttl=62 time=110.497 ms
64 bytes from 192.168.10.114: seq=74 ttl=62 time=31.366 ms
64 bytes from 192.168.10.114: seq=75 ttl=62 time=54.488 ms
64 bytes from 192.168.10.114: seq=76 ttl=62 time=76.777 ms
64 bytes from 192.168.10.114: seq=77 ttl=62 time=201.792 ms
64 bytes from 192.168.10.114: seq=78 ttl=62 time=19.987 ms
64 bytes from 192.168.10.114: seq=79 ttl=62 time=43.045 ms
64 bytes from 192.168.10.114: seq=80 ttl=62 time=66.135 ms
64 bytes from 192.168.10.114: seq=81 ttl=62 time=89.100 ms
64 bytes from 192.168.10.114: seq=82 ttl=62 time=112.371 ms
64 bytes from 192.168.10.114: seq=83 ttl=62 time=32.799 ms
64 bytes from 192.168.10.114: seq=84 ttl=62 time=55.797 ms
64 bytes from 192.168.10.114: seq=85 ttl=62 time=78.817 ms
64 bytes from 192.168.10.114: seq=86 ttl=62 time=101.844 ms
64 bytes from 192.168.10.114: seq=87 ttl=62 time=22.996 ms
64 bytes from 192.168.10.114: seq=88 ttl=62 time=148.791 ms
64 bytes from 192.168.10.114: seq=89 ttl=62 time=68.444 ms
64 bytes from 192.168.10.114: seq=90 ttl=62 time=194.056 ms
64 bytes from 192.168.10.114: seq=91 ttl=62 time=115.667 ms
64 bytes from 192.168.10.114: seq=92 ttl=62 time=37.459 ms
64 bytes from 192.168.10.114: seq=93 ttl=62 time=58.185 ms
64 bytes from 192.168.10.114: seq=94 ttl=62 time=81.219 ms
64 bytes from 192.168.10.114: seq=95 ttl=62 time=104.197 ms
64 bytes from 192.168.10.114: seq=96 ttl=62 time=25.548 ms
64 bytes from 192.168.10.114: seq=97 ttl=62 time=54.581 ms
64 bytes from 192.168.10.114: seq=98 ttl=62 time=71.026 ms
64 bytes from 192.168.10.114: seq=99 ttl=62 time=94.332 ms
64 bytes from 192.168.10.114: seq=100 ttl=62 time=117.081 ms
64 bytes from 192.168.10.114: seq=101 ttl=62 time=39.354 ms
64 bytes from 192.168.10.114: seq=102 ttl=62 time=60.718 ms
64 bytes from 192.168.10.114: seq=103 ttl=62 time=186.127 ms
64 bytes from 192.168.10.114: seq=104 ttl=62 time=107.372 ms
64 bytes from 192.168.10.114: seq=105 ttl=62 time=27.622 ms
64 bytes from 192.168.10.114: seq=106 ttl=62 time=50.484 ms
64 bytes from 192.168.10.114: seq=107 ttl=62 time=73.990 ms
64 bytes from 192.168.10.114: seq=108 ttl=62 time=97.695 ms
64 bytes from 192.168.10.114: seq=109 ttl=62 time=119.909 ms
64 bytes from 192.168.10.114: seq=110 ttl=62 time=41.587 ms
64 bytes from 192.168.10.114: seq=111 ttl=62 time=67.219 ms
64 bytes from 192.168.10.114: seq=112 ttl=62 time=87.337 ms
64 bytes from 192.168.10.114: seq=113 ttl=62 time=109.627 ms
64 bytes from 192.168.10.114: seq=114 ttl=62 time=30.310 ms
64 bytes from 192.168.10.114: seq=115 ttl=62 time=53.339 ms
64 bytes from 192.168.10.114: seq=116 ttl=62 time=92.413 ms
64 bytes from 192.168.10.114: seq=117 ttl=62 time=99.279 ms
64 bytes from 192.168.10.114: seq=118 ttl=62 time=20.721 ms
64 bytes from 192.168.10.114: seq=119 ttl=62 time=44.059 ms
64 bytes from 192.168.10.114: seq=120 ttl=62 time=65.997 ms
64 bytes from 192.168.10.114: seq=121 ttl=62 time=89.592 ms
64 bytes from 192.168.10.114: seq=122 ttl=62 time=214.597 ms
64 bytes from 192.168.10.114: seq=123 ttl=62 time=32.892 ms
64 bytes from 192.168.10.114: seq=124 ttl=62 time=57.162 ms
64 bytes from 192.168.10.114: seq=125 ttl=62 time=78.968 ms
64 bytes from 192.168.10.114: seq=345 ttl=62 time=35.004 ms <- here is where i disconnected and re-connected, the ping is still running but there has been no further response.
441 packets transmitted, 63 packets received, 85% packet loss
round-trip min/avg/max = 19.083/77.468/214.597 msHi llama
Can you please kindly confirm if the connection issues are only occurring whilst using the power supply that come with the LocalDeck?
llama It seems to be responding again now, I’ll find the original power supply and do some testing
If I’m reading this right, you’re saying the device seems to work with a different power supply? Is that right? 
Hi RebeccaH
it now behaves the same with the original power supply and running it off my Mac mini.
one interesting thing to note is that with the original power supply the boot led sequence is much faster, connecting the power supply to the USB connection on the side of the deck seems to get a consistent response for 71 pings and is now unreachable again.
Hi llama
Thanks for confirming.
That is certainly unusual. Could you please give us some details about your network? I have seen reports of users of Unify hardware having ESPHome devices rebooting due to the default data rate control setting.
[ Home Assistant Community Forum / Unify ESP32 Going Offline / Data Rate Control ]
Look forward to hearing from you
Brilliant. Please let me know if this helps.
I’m afraid it doesn’t seem to make much if any difference.
most of the folks in that thread report uptime of at least a day, i barely get 30 seconds of reachability.
it once again just came online for 186 pings and has now gone again, this was after i rebooted it and got a ping at sequence 16 then nothing until sequence 1078 through 1244 when it went offline again.
