Closed CreasaBE closed 7 months ago
Another X1c, single AMS user with esp32 running experimental.
blled wasn't responding to chamber light status changes, they always stayed on.
MQTT Explorer shows correct chamber light status. So I unplugged 24v power and hooked up to USB-C to view the debug logs. Chamber status light changes WERE currently reflected in the logs.
After disconnecting from USB-C and plugging blled back into 24v power supply, blled is NOW responding correctly to chamber light status changes. Yippee.
blled mqtt
Another X1c, single AMS user with esp32 running experimental.
blled wasn't responding to chamber light status changes, they always stayed on.
MQTT Explorer shows correct chamber light status. So I unplugged 24v power and hooked up to USB-C to view the debug logs. Chamber status light changes WERE currently reflected in the logs.
After disconnecting from USB-C and plugging blled back into 24v power supply, blled is NOW responding correctly to chamber light status changes. Yippee.
blled mqtt
tried that a few times with the different firmwares but unfortunately a NOGO here..
tried that a few times with the different firmwares but unfortunately a NOGO here..
Yap, same for me. I hope @DutchDevelop will fix it soon. So far, unfortunately, the board is completely unusable for me.
For me it's kinda annoying to get no feedback from @DutchDevelop. I spent money for a product which doesn't work. Okay, might happen. However, I wish a bit more communication about the status quo, though.
Try joining the discord server. He's more active there - https://discord.gg/7zZxwkhBPx
Try joining the discord server. He's more active there - https://discord.gg/7zZxwkhBPx
I know that. But the software is here, and all its issues too. So the discussions about it should be made transparent to all and not behind a Discord wall.
@DutchDevelop any update please? Or should we send our boards back and get a refund?
@phranck @CreasaBE i dont get notified whenever someone writes here. i really suggest you discuss stuff in discord because i am active there and not here. interms of your issue its not quite clear. looking at @CreasaBE his logs and his topic it seems that its not receiving the mqtt. This could be caused by various things. like your networks firewall, Incorrect serialnumber, or the printer being dumb. The least you can try is a factory restart on your printer which can solve mqtt problems as proven by someone earlier who had similar issues. you're free to return the blled controller by etsy's policy. I'm sorry you're expericing this but theres nothing much i can do.
@DutchDevelop any update please? Or should we send our boards back and get a refund?
Or we try out another product. While searching the net I discovered there are other boards doing similar stuff. One of them is this Lumin board.
Have to discover if it fits my needs.
You could but be advised that the creator of that board backstabbed me and had access to all my schematic / Gerber files.
I will try to recreate whatever @CreasaBE is experiencing, which is going to be a difficult task
You could but be advised that the creator of that board backstabbed me and had access to all my schematic / Gerber files.
Damn... How's that possible? 😳
A GitHub repo isn't the place for discussion of that sorts of things. So refrain from doing it if you want to discuss anything related to it, find another place to do so that isn't this repo. I should have been clear on this when I removed your first comment
This could be caused by various things. like your networks firewall, Incorrect serialnumber, or the printer being dumb.
There is no firewall inbetween (same vlan), serial no is correct (as it's the same in HA and HA works, same as with the MQTT Explorer), how can the printer be dumb when it is clearly in the MQTT packet as shown from the logs of MQTT Explorer and even HA sees light status
Is there a way to completely clear the board so that nothing, but absolutely nothing remains of any kind of config and to restage the board completely? (not using the 'format' option in the web installer)
@phranck @CreasaBE i dont get notified whenever someone writes here. i really suggest you discuss stuff in discord because i am active there and not here.
I suggest you enable notifications then, because whenever someone adds a comment to the issue post I get a mail notification. As we already said, Discord is not a support channel, discord is a fancy pancy chat program and I have enough chat clients already.
Thank you for the information I'll go dig deeper in this situation.
You can erase/ format it with platformio. It's an vscode extension. With platformio you can also directly flash the firmware on it by downloading the repo and opening it
Thank you for the information I'll go dig deeper in this situation.
You can erase/ format it with platformio. It's an vscode extension. With platformio you can also directly flash the firmware on it by downloading the repo and opening it
Thanks, I'll try it this evening or friday at the latest and let you know. Maybe something got stuck in between upgrades from stable to development, even after reflashing several time. I'll try to reformat it completely and reinstall from scratch and keep you updated
Alright sounds good
Just erased the firmware and flashed the ESP8266 via linux commandline with ESPTOOL did the setup, rebooted but still same issue. Currently no power source connected except for the USB port. but still no joy. Latest experimental version 'BLLC_Experimental_10.1.24.bin'
Mqtt message received,
FreeHeap:
8576
Mqtt payload:
{}
stg_cur not in message
lights_report not in message
Mqtt message received,
FreeHeap:
8576
Mqtt payload:
{}
stg_cur not in message
lights_report not in message
Are you by any chance using the latest beta firmware?
I'm having the same issue here however it can be fixed easily. Once Dutch has the mqtt dump.
(the latest beta changed some mqtt stuff slightly altho not massively so might not be a issue depending on how the code is written)
That really depends what's changed, we filter out everything apart from HMS, stg_cur, gcode_state and light_report.
Sofar with his logs I might have a clue to what and potentially a fix for this
@CreasaBE Please three backticks and your code/dump will be well formatted.
Sofar with his logs I might have a clue to what and potentially a fix for this
Hm... he already posted the exact same two weeks ago. 🤔
@CreasaBE Please three backticks and your code/dump will be well formatted.
@phranck yeah I did it through the gui, but sometimes it doesn't work too well..
@CreasaBE
yeah I did it through the gui, but sometimes it doesn't work too well..
I never use that GUI. I always write Markdown by myself. That it works as expected. 😃
@DutchDevelop got an update please?
unfortunately not yet. i've been focused on other common issues and replacing wifi.h with improv.h
@DutchDevelop any update please? Since you know what the issue is, I think it should be an easy/quick fix?
Unfortunately not, my guess was something to do with the mqtt connection but I don't see anything which could cause this so i have no idea what causes this nor how to solve it at this point in time
Well, so I spent money for a non functional BLLED. Hm... okay...
As i said earlier feel free to return it for a full refund, im sorry that it's not functioning as it should for you
@DutchDevelop I would like to. Unfortunately, I no longer have the original case because I wanted to install the PCB in my AMS riser.
Thats ok, message me on etsy with your order number so we can make the return happen.
@CreasaBE feel free to contact me on etsy for an replacement which will solve the issue
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