LocalDeck Configurator - LocalDeck Files Error: [GET] "/api/index-files": 500

David

My LocalDeck arrived yesterday. Hardware is great, all fits together nicely. I’ve connected the LocalDeck to my network without issue and HomeAssistant can see it.

I can’t get the Configurator to work. It installs and starts but then gives an error:

LocalDeck Files
Error: [GET] “/api/index-files”: 500

Digging into the add-on logs I have:

[nuxt] [request error] [unhandled] [500] ENOENT: no such file or directory, scandir ‘/homeassistant/esphome’

What do I do next?

AAllport

Hi David,

Have you installed the ESPHome addon and adopted the device? LocalBytes Blog / Getting Started with LocalDeck / HomeAssistant Config
This will create any necessary files!

We’ll look to improve the error messaging soon.

David

Got it. It wasn’t clear to me which bit of ESPHome I was missing since I already have some ESPHome bits showing in HomeAssistant. The instructions are a little brief, including a link to https://esphome.io/guides/getting_started_hassio.html (or the Add-on button) would have helped me.

I’m now stuck at the Reinstall Firmware stage. If I go to ESPHome -> Install -> Wirelessly I get:

Failed config

At least one platform must be specified for ‘ota’; add ‘platform: esphome’ for original OTA functionality

I expect I’m missing a step somewhere else but I don’t know which.

AAllport

Nope, that’s not a you isssue!
Looks like CI broke, so we didn’t actually release the 2024.06 fix.

Will get that sorted ASAP

AAllport

We’ve just published v0.2 of the configurator, that should fix things for you!

bushbrother

I am getting 404
Page not found: /api/hassio_ingress/zFhd5fWKAfLa22YqD1dVQhpfKm-uVbv2k-Y0FLY6ZvE/ from the configurator UI now … if i press the “go home” button it shows the yaml file to configure like it did before, but now it doesnt save anything (even though it says it has) and the print button just says the same thing.

AAllport

What version of HomeAssistant are you running?
The 404 is a new one…

bushbrother

AAllport

2024.7.1

Seems it keeps throwing an error when pushing save/print … also reset doesnt work 🙁

at link (node:internal/modules/esm/module_job:75:36)
2024/07/07 16:38:30 stderr at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:39)
2024/07/07 16:38:30 stderr at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:250:38)
2024/07/07 16:38:30 stderr at ModuleLoader.resolve (node:internal/modules/esm/loader:373:25)
2024/07/07 16:38:30 stderr at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:404:12)
2024/07/07 16:38:30 stderr at defaultResolve (node:internal/modules/esm/resolve:1193:11)
2024/07/07 16:38:30 stderr at moduleResolve (node:internal/modules/esm/resolve:973:20)
2024/07/07 16:38:30 stderr at packageResolve (node:internal/modules/esm/resolve:916:9)
2024/07/07 16:38:30 stderr at new NodeError (node:internal/errors:405:5)
2024/07/07 16:38:30 stderr [nuxt] [request error] [unhandled] [500] Cannot find package ‘@localbytes/esphome-config-ts’ imported from /usr/src/app/server/chunks/routes/api/editor.post.mjs

AAllport

Right, I see. We’ve got a reproduction.

I appreciate your patience. This is ultimately a result of the broken build, and then updates happening.
In short, it’s an us problem, not a you problem.

Please standby, we’re doing everything we can to get things resolved ASAP.

We’ll also be re-investing our findings into making the build pipeline more robust as we go forwards!

bushbrother

AAllport No problem - glad you know what it is 🙂

AAllport

I’d love to say we’ve solved the problem, things are still going a bit weirdly…
That said, we’ve found a solution.

Given the issue seems to be in the CI pipeline, we’ve just bypassed that and a working build from my local dev machine.
At the very least, it gives us a bit more time to finish off the current LocalDeck build, and then make the build pipeline a lot more sturdy.

ESPHome 2024.06 should now be working in Configurator v0.2.1!

David

AAllport
LocalDeck Configurator now seems to be working although it is a little strange. Should I get the same 4×6 grid of buttons when I click on secrets?

I still can’t Install from ESPHome, same

At least one platform must be specified for ‘ota’; add ‘platform: esphome’ for original OTA functionality

error

bushbrother

Really struggling now. Decided things were messed up, removed from ESPHome, started again, now seems its not working at all 🙁 Occasionally it connects back to Wifi.

Where do I get the working configurator from? Build on github is v0.2 from yesterday and HA seems to think v0.2.1 ?

I am using ESPHome 2024.6.6

EDIT: v0.2.2 is working … a bit.

rdeangelis

I had to roll back to the very first configurator and everything is working. With the latest it wouldn’t connect to wifi and it was very unstable.

I’ll do some more tests later.

rdeangelis

The configurator rollback didn’t really work tbh I was just manually using the older version of the yaml file in ESPhome to fix the problem. I quickly realized it wasn’t saving the config.

I managed to get a few buttons working without configurator by taking part of new config and entering it in the old config, and it works but it’s too difficult and time consuming to get the led and everything else working manually. Hopefully we have a fix soon but 0.2.2 not working at the moment, mine just keeps rebooting continuesly.

With an older version of the Yaml file which you might get from backup (if you have it) you can get it going again (by uploading the new fmw via usb) but configuration of buttons without configurator is no fun.

bushbrother

Ok your experience matches mine, which makes me feel better at least!

Not seen any activity on forum or github today sadly …

Sherlock

bushbrother

Not seen any activity on forum or github today sadly …

My dude, just because you’ve not seen activity doesn’t mean stuff isn’t happening in the background! Patience, and patches will most surely be with you shortly. Adam has proven time and time again that he’ll resolve these problems and make people happy.

You’re an early adopter, snags happen 😃

bushbrother

Sorry if I sounded impatient, and yes I know he is working on it … I was just trying to work out if it was me, or if others are in the same boat …

Just itching to use it 🙂

RebeccaH

Adding to @Sherlock just want to reiterate that stuff is happening behind the scenes at Local Bytes HQ. We’re a small business and this is our first from-scratch product release. We’re doing our best to divide our time between software fixes and sending out stock yet to be shipped.

As always, thanks for your continued patience!

itsbri

For what it’s worth, the device is entirely usable without the HA add-on. I opted to not even install it and went straight into Node-RED to start assigning service calls. Since I’m a heavy NR user it’s no different to setting up a zwave or zibgee switch with the added bonus of being able to light the switch up.

All I did to get it working was to connect from my PC to the device via WiFi and added to ESPHome on my HA instance. As soon as it showed as ONLINE I swiftly forgot about ESPHome and went straight into assigning flows in NR.

rdeangelis

itsbri you make a good point.

If you need it for basic usage direct service calls are great, otherwise NR for advanced flows is of course much better.

How are you interacting it in NR? Are watching and interacting with home assistant localdeck entities, or some other way?