dutchdevelop / blledcontroller Goto Github PK

In the new version 5.1.24 the red error checking no longer works.

I was browsing the source and believe this if this mqtt severity status code may have been misspelled

'Fetal' was perhaps intended to be 'Fatal'

Line 10 of the mqttparsingutility

return F("Fetal");

Please ignore/close this if I'm mistaken

BBLED was delivered yesterday march
Try to update firmware but the device doesn't show up in the USB list.
Initially used an USB-C power cable, but now I have used the correct USB-C data cable (with trident symbol).
Took the board out of the housing to make sure the plug was correctly inserted
(re)installed [CH340 drivers] but the BLLED still doesn't show up in de device list.
Please advice
Kind regards,
Ton

It would be amazing if there was a setting in BLLED to only have the LEDs triggered when the printer is not idling. For example, lit white when printing, red when errored, and green when complete. Otherwise, turn the LEDs off.

i see no way to dim the lights, unless i install a dimmer dial..

the multicolr led strip i purchaced is dimmable, but BL-LED is the only controler installed.. with no instructions provided to send it commands

Hello,

I want to use the experimental firmware, with the dimmable option for the LED, because i think mine are too bright, but i get an error when i try to change the firmware with the "upload" menu and upload the .bin file, here the error :

I download the .bin here : https://github.com/DutchDevelop/BLLEDController/blob/main/firmware/esp32dev/BLLC_Expirimental_20.10.23.bin

I check the board, and i have the es32 board

i also try with every Expirimental and the v.07 version but everytime i got this error

Thx in advance

Add option in de webgui to manually turn on/off the LED strip during maintenance and/or replacing parts where the printer is off.
Current firmware turns off the led when the printer is turned off.

Version 5.1.24 does not switch off the LED's when the console switches off the Printer Light. Also Green status at the end of the print is not working. Also during LIDAR Flow analysis the light does not switch off .... basically 5.1.24 is fundamentally broken.

Was looking for something like change Color X when at x% or something like every X mins report progression via blinks/color cycle ect. Just some way for the leds to show printer progress.

Would also love a way to add in custom colors. EX: Blue=Pause, Yellow=Filament run out ECT.
These 2 things would be great for someone who's printer is not even in the same end of the house as we are. I use the BL LED to keep a eye on my printer without having to keep the handy app up or having to keep my pc running.

Loosing connection seems to indicate a weak connection to the network. Even if the printer has a good connection, the light will go off every time I lose connection and come on when it reconnects. However, after a while, it won't reconnect, and I need to remove power to reconnect.

I have found that, at the end of the print, the green end of print status remains lit and no longer exits this state, and I can no longer manage the white light.
It would be useful to deactivate, in the P1 series, the shutdown function during plate leveling, it does not have Lidar and is not needed; while it is useful to observe the procedure better with more light!

I think i found a bug in the Code. The finish state (green light) is not left because a bracket is not at the right place.
The closing bracket needs to be behind ">= 300000)"

https://github.com/DutchDevelop/BLLEDController/blame/0763358e4dc4158633b3bb70be3c480c71d9acba/src/leds.h#L271

Thanks!

Receiving the above error in logs. The RGB cycle keeps on cycling LEDs

Hi,

I'm getting an error "Deserialize error while parsing mqtt" in the console.
Light and printing status are not replicated to the board.
Logs also contain

Mqtt message received,
FreeHeap:
9224
stg_cur not in message
lights_report not in message

I have the same issue using STABLE and EXPERIMENTAL firmware.
The access code is correct as HomeAssistsant is using the same MQTT connection to the printer and the status and controls there are working fine

The LEDs turn off as expected during the LIDAR scan of the test pattern. However, the LEDs remain on for the LIDAR scan of the first layer. First layer scan should also disable the LEDs until completed to prevent interfering with the camera.

I have the password screenshot, but I need the default Username for the webpage login. I forgot to add the access code on the setup.

TIA!

Since updating to either the latest stable released 17th March, or to the final version by Wile1411, once the 30 min timeout turns off the LEDS, they remain off permanently. Opening or closing door, turning printer LED on or off, causing an error, does not bring the LEDs back on, I have to restart the BLLED contoller, then it works normally again until the next timeout.

At least on the X1C we have this entitiy: "_enclosure_door", which signals, if the door is open or not.

It would be nice to have the lights switch to white as soon as you open the door. No matter which color was displayed before.

Like, if there is an error, then BLLED turns on red light. But to take care of the problem, you want to have proper light. So when you open the printers door, the white light should come up automaticly.

Also when the print is finished and you see green light. Just walk to the printer and open the door to get proper light to remove your parts. That would be convienient.

New bug in ver. 19.3.24:
LEDs will enter red "error" state on non-serious non-halting advisories. For example "HMS_0C00_0300_0002_0001: Filament exposure metering failed" (https://wiki.bambulab.com/en/x1/troubleshooting/hmscode/0C00_0300_0002_0001).

By testing with the colour setting, this appears to have been categorised under "HMS Severity, SERIOUS". This cannot currently be mitigated without completely disabling Error Detection, as there is no way to set the LED CW/WW state as part of the UI (only RGB state) so the standard illumination (RGB off, CW/WW on) cannot be set.

My use of the controller is perhaps a little different to others because I use the controller inside my office, to get a virtual status of the printout in the garage. And since I am color blind, I would like to be able to identify different printer stages with some kind of blink patterns.

Btw. Is't possible to connect 2 controllers to the printer without issues, eg. one to lit up printer and one in office?

Just ordered one of these from etsy, really looking forward to using it. Had a few suggestions to increase the functionality.

Saw that you implemented brightness control, so it'd be nice to be able to set different colors for the various faults instead of them all being red.

Another nice feature would be being able to flash or cycle between two colors. Again, this would be nice for various faults to differentiate. That way red still means a problem, but then the 2nd color would indicate what type of problem.

Rainbow mode to cycle through the rainbow colors would just be cool for all us RGB fanboys out here. Might be a nice light show for when the printer is idle or successfully completed a print.

It would be helpful to use the date format YYYY-MM-DD in the binary file names so that newer versions sort to the bottom.

Hey there!

I installed the new firmware on my device, and it's running smoothly, but after ~4h of printing, LEDs are turned off, and impossible to turn them back on, unless by powering off the device, and then powering on again...

Do you have any idea why?

Thanks

I'd like it if the LEDs could be controlled manually (either via MQTT or the Web UI) on/off, and also configure the brightness for when they are on.

Hi Pascal,

I purched your great device in July.
Since I haven't had the time to install it up to now, I tried yesterday.

Unfortunately this thing doesn't connect to my bambulab printer, so I tried to flash the firmware.
So I tried conneting with USB on my iMac but the flash routine states, "Your ESP8266 board is not supported".
Could you please help me how to flash the latest firmware onto this?