Should be able to send a project_file command from a local http server if the endpoint is a 3mf file. But if you print directly from Makerworld as well (from the site, not downloading to slicer and sending) it will also print using an HTTP address. You could use makerworld to verify the outbound connection.
Additionally, P1 series used to (and in some cases still does if cloud connected) unpack in the cloud and print via http as well.
Tried with http and https⌠printer didnt make any outbound connection⌠can you please share more details? Perhaps an example mqtt message?
Changed this to http://myip/blah.3mf and nothing happened on printer⌠no error either
I donât have an example handy but you can easily generate one by printing directly from makerworld and looking at the project_file command. But it doesnât do any checks on the origin IP, sometime back in Oct/Nov last year I had tested with a local python-flask server hosting a 3mf file I had sliced in orcaslicer - worked like a charm. I also believe others have had it working since then on current firmware.
Wanted to let other folks here know - with X1Plus, my bed-mesh visualization flows are updated and now work again!
My other flows are updated with some extra sensors, but are already compatible as is, but Iâve done quite a few optimizations and cleanup as well as part of my v2.1.0 release.
This site has been tremendous in helping me create my own app for connecting to bambu printers. Im not using ha to connect at all but the info has helped me a lot. I cant seem to figure out how to view the network debug logs in orca slicer though. Is there a certain way to view the .enc files? I have WireShark from many years pass and it tries to open it but it says its invalid file. Im not sure how the files are encoded so any help would be much appreciated.
Working with X1Plus confirmed, including bed-mesh. sweet!
I rebuilt almost everything using the guide.
the only issue i have now, is both my AMS sensor attributes report to one device. for example, sensor.ams_0_x1_carbon_ams and sensor.ams_1_x1_carbon_ams both belong to AMS_1_X1_Carbon device, and AMS_0_X1_Carbon device has no entities.
Thatâs strange, might be some desync with device identifiers. Could you try connecting to the mqtt broker via mqtt explorer or other and deleting all AMS_0 and AMS_1 topics - with the printer off. Then restart HA and when itâs settled, turn on the printer?
I did 2-3 updates ago adjust the uniqueness of device identifiers, and in âmostâ cases it should pick up the new ones but sometimes mqtt doesnât apply that immediately, or if it does, HA doesnât pick up on moving entities around quite yet.
EDIT: I also might see one minor logic bug in the code for that actually, so I just pushed a potential fix (not changing version). Just redo the basic flow (configurator updates automatically) and hopefully it fixes it, but still do the steps above perhaps just to clean things up?
didnât fix it.
in HA, i disabled mqtt, deleted all sensor.ams* entities. restarted HA.
in node-red, replaced new basic flow and deployed.
in mqtt, there were AMS_0_X1_Carbon and AMS_1_X1_Carbon topics. deleted them both.
started x1plus x1c, enabled mqtt, and restarted flows.
AMS_0_X1_Carbon and AMS_1_X1_Carbon topics recreated.
HA shows AMS_1_X1_Carbon having all sensor.ams_0_x1* and sensor.ams_1_x1* sensors.
Was thinking more to delete it from MQTT before any HA stuff - deleting from HA wonât do anything as itâll just remake or potentially mess up when they get back to working.
I tried simulating this (I only have one AMS) by duplicating an AMS entry with a fake S/N and id of 1 (compared to my only with id of 0) and did not encounter the issue. However, I did push another change just now that might fix it still in the basic_flow if you want to retry that.
I would say this time just import the new basic flow and delete only from mqtt in mqtt explorer the AMS_1* and AMS_0* topics in sensor.
Give it about 5-10min after importing the new one. I think potentially the nodered flow array I had for storing AMS serial numbers could be half-broken in your case, which means itâll need to be remade (as recent nodered versions persist flow variables between deployments now), so youâll have to wait for the âfetch versionsâ node to run once or twice, or manually run it a few times after it initially connects to the printer.
all good now! updated basic. but it took a few attempts to get it all working right. first, there was a ghost ams device i had to clean up (deleted mqtt in HA, mqtt topics, node red restart). then the 2nd ams didnt report the same entities. cleaned up again and it finally is all good. thanks!!!
Just wanted to mention that Iâve once again updated my flows + dashboard yamls. Dashboard yamls are now much more modular and friendly, intended to be deployed with HAâs new âSectionsâ view layout.
As for new features, Iâve added a custom speed percentage slider. Lets you set a custom speed setting from 30%-180% in 2% increments. Iâve also added a home-axis button with a preview setting of what axes are currently homed.
I finally got around to updating mine but the advanced setup is still eluding me. One day Iâll figure it out.
Awesome work @WolfwithSword !
Pretty sure I have bigger problems since I get nothing in Grafana but how do I create a hard-code value in a template sensor?
For Grafana you would need to look up on connecting to the postgres DB as a datasource and select it when importing the dashboards.
For the hardcoded value for the template sensor, you should be able to do that through the UI. Go to devices and services â Helpers tab in the top, create new helper and go to Template sensor (not binary). Then in the state template you could just type in the value.
Thank you. I was trying to create the template sensor the old way and screwing it up. That worked much easier 
For the Grafana, Iâm connected correctly to the DB anc can pull the table but no data in there seemingly so I mush have something wrong going into Postgres. Iâll review that further.
Also, in NodeRed I keep getting this error:
Advanced Flow cannot be used without the Basic Flow group in the same flow.
I have the standard flow in one tab and the advanced in a separate. Doe this error mean they need to be on the same tab?
Yes they need to be in the same tab. The idea is that each âTabâ is for one whole printer ideally, and the advanced flow is pulling variables and sharing data with the basic flow, which can only safely be done in the same tab.
This is also likely why your grafana data is not working - thereâs nothing in the DB yet and it hasnât even made the tables since the advanced flow has not been working.
Yep, that made all the difference!
Ok, that gives me somethings to play with. One more item that just has me scratching my head. I canât get the start time. I didnât change anything but it hasnât worked since I loaded the new/updated config.
It should start working if you start a new print - sometimes on the first round of setting up it wonât immediately work especially if done during a print. This was the behaviour with P1 series stuff most of the time but recent patch firmwares for X1 also âremovedâ start timestamps from the payload (hence now I have to pull it a different way). But yeah once you âstartâ a new print I believe it should populate from then onward.
Though if it continues after starting more then there might be something I missed.
I will keep an eye on the âstart timeâ. Iâve been printing this little coin holder over and over trying to test this out.
Amazing what you have developed! Always impressed!
Hm if itâs been a few prints and still hasnât shown up itâs a bit weird. I donât have time for a bit to try debugging that (assuming youâre on newest FW?) though it seems you did get the start epoch at least, so worst case you could try to look into how to replace it in the yaml with the epoch and have it format visually into a timestamp.
Also notice the Aux fan controls isnât showing up for you there, unless you manually removed that?
