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

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?

itsbri

Using events state for when the button is on. Using this method I can also do ‘mode’ switching and more.

Press, double press, hold 1s, hold 5s, button sequence (unlimited length).

Still working on the sequence one as wifi is causing some latency issues.

AAllport

Morning All, 👋.
Just checking in to make sure you’re aware that we’ve released v0.3 of the configurator, which should solve these issues!
I’ve also posted to explain what went wrong and why in the update thread.

itsbri Press, double press, hold 1s, hold 5s, button sequence (unlimited length).

It’s not well documented (yet), but we do emit events for single and double 🙂

« Previous Page