-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UPDATES... kind of 🐜 #88
Comments
Hey @taburineagle Btw. did implement any of those 'busy' signs in the files for the webbased? I was contemplating looking into updating it, if something new has appeared. |
@fribse - I'll have to check into MicroPython! I've actually never used that variant, but it looks interesting. C would still work, I'm guessing - semantically, I'd just have to change the name for the ESP version to something else, as just "NeewerLite" has already been taken 😄 ESP-NLP... or something... I have actually added that in a while back - it might have gotten lost in the fray of updates - I pushed a busy signal update in the latest commit to the WIP-HTTP-Server-Mods branch... |
Ha ha, uh, the big change in naming. |
I just tried the 'new' version, but I get a list "index out of range" when I replace the two files.
|
Hmm, interesting... are you still using the older custom preset file structure? The one from #81? When I tested it with the old-to-new style converter, everything worked here on my end, but there may have been an eccentricity I didn't notice. Are you saying if you have no |
Looking at that screenshot, it looks like it just successfully connected to CE:D9:49:A3:1F:F7 (it shows this at the top), but the table still shows lights aren't completely linked yet. Are you saying if you let it look for lights and link them, the message at the top doesn't go away if you let it run for a longer period? (the HTTP Server busy message just shows the last message received from the program when it's busy, so in the screenshot above, it's still working on connecting to the lights and isn't 100% ready for anything else yet)... |
Hello! It has been a long time since I've been here, and the reason is... wait for it... ants -
Or, to be more specific, necessity to work on other projects because of ants. A camera enclosure I've been running had an ant infestation that not only destroyed the hardware I designed inside of the enclosure, but also destroyed the camera somehow - to the point where a fully-functional 4K camera can no longer record in 4K because of... reasons - it sees the 4K shot, it sets it up like normal, but refuses to write data for 4K (HD is fine however)... so I'm guessing something inside the memory of the camera (the buffer perhaps) is shot. Due to that, I've spent the last few months working on a completely new system (both engineering completely new hardware, software and layout logistics) that has kind of become a white whale of a project - one that I have needed to see through to the end. I've done it, designed an entirely new PCB, written an entirely new (and much better, honestly) daemon in C, etc. - but it's taken 2 months of complete focus that has taken me away from other projects like NeewerLite-Python. One plus-side to that is I've had the chance to code with an ESP32, and see the kinds of things it can do (originally I had a cobbled together PCB that I designed running a ATTiny chip connected to a Pi Zero, I simplified the entire thing using just an ESP32) - so I might actually be able to port a version of NeewerLite-Python (it wouldn't be Python any more, but meh) to an ESP32 using the built-in WiFi and Bluetooth, which I think was a vision @fribse had years ago for a project like that based on a microcontroller instead of a PC.
Ha, tl;dr - I'm still here. Haphazard, but here 😊
The text was updated successfully, but these errors were encountered: