I have round ones in it but they don’t go below 20%
Luxury! I have mine in a garage, its 40% on a good day 
That photo is from some time ago, but having those desiccant containers in there really works, my P1S is also in the garage, ambient humidity there is 74% (!) at the moment:
1 Like
Yes i did the same as Robert! Works perfect and you have extra space for silica gel!
Just want to say thanks for this app. Installed it and it’s working perfectly right away!
(And for those turning this into a dessicant thread. I’ve done the same and stay at a stable 20 (device seem to bottom out there unless extremely dry when it shows 10) and works perfectly when ambient humidity is upwards of 60.)
1 Like
Thanks for the positive feedback, always nice to hear that something you spend time on help others.
Hello @BufferOverflow,
I had to factory reset my P1S.
Since then your BambuLab.App keeps crashing … unfortunately.
Due to the reset, the "Access Code "of my P1S changes.
It seems to me, that a invalide/old “Access Code” causes the BambuLab.App crashing.
Entering the new Access Code into the BambuLab.App it stopped crashing.
I sent you the crash report: a5edf135-dd98-4505-b4e9-a94d08fb9bef
Maybe it is something which can be fixed in the program code.
Are you planning to publish your BambuLab.App code under your GitHub Account?
Thanks for your effort.
Best, Andy
You tried reinstalling app and device?
Same ip as before?
Did you upgrade the firmware on the p1s sfter factory reset?
If nothing else works you could try connecting via an mqtt test tool perhaps. I used one called MQTTX but there are others.
I will take a look at the diag report.
Hi @BufferOverflow,
- have not reinstalled the app.
- P1S and Homey have the same IP Adress.
- No update of P1S Firmware
My Solution: After entering the new Access-Code into your App, it works again.
The issue was, that the Access-Code of the P1S was changed, because of the factory reset of the P1S.
It seems that: When the Access-Code of a known printer changes (/is wrong), your App struggles and crashes.
Maybe you can check it by changing the Access-Code in your printer.
Best, Andy
Nice to hear that you are up and running again 
Yes, having the wrong access code an already added device do result in strange behavior. I will add it in the “known issues” in post #2 and mention the factory reset.
Thanks for reporting.
1 Like
App crashes for me… Worked for 2 days, and now crashes after every restart.
I have a A1 printer.
Diagnostics code: 9f7dcbde-32b2-4596-9278-6f3f8597f454
Could it be that you got a new ip? The error i see in the diagnostic report can match with that.
Restart printer also. And maybe remove device and try to add as that gives a better error message.
Silly me… The printer had gotten a new IP and access code.
But I still have to restart the app and rush into the device setting to change them before the app crashes again…
Thanks for the help!
First of all, I would like to express my appreciation to you for the time and effort you put into this!
I have now installed the App on my Pro and have entered the correct data to connect my X1 to the App. A tile for the printer also appears neatly in my devices, but unfortunately there is no communication between the Homey and the printer, I think, because all values remain set to unknown. I have attached a screenshot of the status displayed by Homey and the status of the printer itself while I am printing.
Is it possible that the printer is added to my devices in Homey, even if I have made a typo in the data to be entered? Or if the printer is added, is the data entered correct by definition?
I also made a report: d006cf7a-3e61-4f15-b926-f636e6d482b6
Can you figure out what I’m doing wrong?
I can’t seem to add my P1S. I always get the following error:
pair.error The error is: Failed to connect to printer via MQTT: connack timeout. Please check your connection settings and try again.
I was able to add it to Home Assistant. Does it need to be in cloud mode? Because I’ve put mine in LAN only mode.
I’m using version 1.0.10 and the firmware of my P1S is 01.06.01.02
Here the same. But i mansion that the printer (x1) is not always on. To prevent this unnecessary power consumption.
I have the same for X1C. Not sure if need to be on the same subnet to work.
I am experiencing app crashes when my printer(s) are offline.
It seems to occur when the devices are unavailable. A fix for this would be highly appriciated.
I have multiple printers connected and every time one is powered off (by smart plug, to save power), the app crashes after a short while.
It should not require that, at least that was the intention as it does not use the Cloud API at all. But maybe something else changes when in LAN Only mode.
I have added it to the fix/next-version list. 
Thanks for reporting.
Did you solve this? Otherwise please verify that you have entered all using the upper/lower casing.
