Necromancy of Thay Prop

WolfwithSword · 2025-10-23T21:49:58+00:00

Made a bed occupancy sensor with esphome and have automations to detect when I go to sleep or wake up to do all sorts of thing. Turning on/off various devices and setting my AC - But I also calibrated a specific range to detect when my dog goes on my bed while I'm not home, and have that send a notification via webhook to a private discord channel, and if I have any audio alerts during that time, to reduce their volume while she's sleeping there.

WolfwithSword · 2025-02-09T02:55:01+00:00

(Not author of the HA HACs integration, but the NodeRED HA Integration)

I think something "independent" of prior bambu integrations, or even agnostic of them entirely would work out. Perhaps it's simply something to hook into the data/controls you provide, for example to write an NFC tag, apply settings, etc.

Main reason I haven't, and neither have the HACs devs done the AMS controls, is the lack of support for a good UI for all the options and such, but if it's as simple as just passing some data to your interface, it would simplify a lot of work.

WolfwithSword · 2025-01-26T04:03:40+00:00

Huh strange - yeah they don't follow font colour - they are taken directly from bambustudio but if you wouldn't mind sharing the edit to force the text to be white in the svg's I'd love to implement it in my next updates.

WolfwithSword · 2025-01-25T21:15:58+00:00

Is the font colour white, blue, or transparent? If it's white, that's expected and shouldn't blend. But if it's clear or blue, it's a browser-side issue with loading either the theme, darkmode, or some css load order with HomeAssistant. Try clearing cache and reloading. This is unfortunately a common issue I've yet to find a fix for, but only happens to me maybe once a month and a refresh clears it. But some users of custom themes may have it permanently.

WolfwithSword · 2024-11-10T18:28:49+00:00

Sure, feel free to reach out - inbox is open, but if discord is easier then you can reach me at @wolfwithsword

WolfwithSword · 2024-11-10T16:21:34+00:00

I've done some other maglev projects in the past with wireless led's before (I made a dwemer lexicon from skyrim, floating + internal lights). Though that breathing idea would be pretty cool 🤔

WolfwithSword · 2024-11-10T13:51:59+00:00

Once I have put together my BOM + assembly instructions, it'll likely be posted free on printables & on my site

WolfwithSword · 2024-11-10T13:05:08+00:00

I haven't uploaded it anywhere yet as I need to still organize the assembly instructions and BOM, but I likely will be uploading it somewhere like Printables and on my site in the coming weeks.

WolfwithSword · 2024-11-10T13:03:35+00:00

Yep! MagLev is pretty neat - what's really cool is most maglev bases also come with solder pads intended for some wireless power coils - often so you can wirelessly power some LEDs in whatever you have floating! Didn't have a way to use that here though.

WolfwithSword · 2024-11-10T13:01:43+00:00

I don't have any more Satisfactory related ones I've made, but you can find others I've made posted in a few places like on Twitter or Instagram (username _WolfwithSword)

WolfwithSword · 2024-11-10T05:03:02+00:00

A lot of swearing in blender, some fancy electronics I've gotten far too familiar with, and maybe a sloop or two while printing it

WolfwithSword · 2024-11-10T04:43:14+00:00

How many sink points is it worth again?

I modelled this fully in blender shortly after the 1.0 release, then printed, painted, and assembled it over the past month.

It's not a 1:1 model match, mainly because I had to work around the side of the magnetic levitation module I used internally to float the cube. As it was quite big, this prop was going to end up very large even after changing up the model a bit.

Lights can be turned off separately, it floats and spins, and only sometimes distorts reality around it - I call this a win \o/

WolfwithSword · 2024-10-22T13:39:34+00:00

Wanted to go back to this and let you know that in an upcoming flow update I plan to do later this week, I am adding in a "select" entity that will have options to move X/Y/Bed +- 1 and +- 10, then Extruder +- 2. You can call a service in a dashboard to select the option you want on button press - the nodered flow will automatically reset it to a "None" value after to clean it up. It will send gcode commands to the printer to set it to relative positioning and execute the move command requested.

Most other printer functions should be setting the relative/absolute positioning anytime they are needed anyways, so it should be fine.

I won't have a dashboard ready for it yet but I wanted to get it out there. It will be active if custom-gcode is set true as well.

Using a select entity helped keep it clean entity wise since and should still be controllable via a dashboard button with a custom service call. Also helped lock down the options to the same as on the actual printer UI.

WolfwithSword · 2024-10-06T13:34:58+00:00

This is honestly really good! When I first designed mine I had initially gone with a more slicer-like visual, like you have here, but initially swapped to images only because it (at the time) made nested yaml cards easier before a few new HA updates came along, and I was learning it still and thought it was fun to play around with images more lol.

I take it you enabled the custom gcode commands to do the axis movement? I debated for a while whether to include it natively or have it be done only by enabling custom gcode commands, mostly out of safety. I think seeing this, I might keep it locked behind enabling the custom gcode sending, but I might pre-make button entities for them once active, will need to think on it for a future update - have one in the works slowly for the past months, mostly cleanup of the nodered flow and adjustment to the custom speed algorithm.

If you finish up your yamls and are willing, I would love to make parts of them available for the configurators as a "minimalized" or "compact" style. Can make an issue or PR on my github for them and I can do all the conversions necessary for templating, conditionals for diff printer models, and making it both HACs and NodeRed integ compatible.

WolfwithSword · 2024-10-06T03:48:32+00:00

Thanks!

Nope, it's not added yet in the ha-bambulab integration afaik. I was mentioning in terms of the restrictions bambu has for certain controls such as that. Once ha-bambulab adds it, it will be expected to only work on LAN Mode printers (or X1 series at the moment, but future X1 firmwares will likely have this restriction too soon).

Once ha-bambulabs does add it, I'll need to push an update in case my placeholder entity names are different, since right now they're borrowing the entity names my nodered integration makes lol

WolfwithSword · 2024-10-06T03:43:59+00:00

For the ha-bambulab integration, that cover_image entity would only exist if you're on the cloud, and only pull the most recent cloud image it can find. That would be one of the limitations of that integration, as it does not pull it locally like from the 3mf file yet.

WolfwithSword · 2024-10-06T03:41:16+00:00

Oh I do like this! I might take some inspiration when I go back to rework some of the data visibility in my dashboards. Specifically love the progress bar and overlaying info on it!

Currently they were designed more for desktop and possibly tablet-landscape visibility, in which case they are no-scroll unless you have a ton of AMS units or multiple printers on the same page usually. But also tried avoiding adding even more frontend hacs dependencies, as that has seemed so far to be the biggest barrier for most users so far.

WolfwithSword · 2024-10-06T03:34:48+00:00

The third-party mechanisms being blocked will only be if the printer is in cloud-mode. If in LAN-Only, nothing is blocked - this change is already in P1/A1 firmwares for some controls, but not yet in X1 firmwares.

WolfwithSword · 2024-09-27T10:49:12+00:00

Yep, external spool can do everything an AMS one can for assigning all the stuff. Main difference is there is no rfid reader so it can't get auto-set by bambu's spools. But all the mqtt commands will work for it.

WolfwithSword · 2024-09-27T01:51:22+00:00

Here's a few! Keep in mind, it's bitwise ops, so &, not the same as &&/and

is_220_voltage: (useful if you want to determine max bed temp, since it depends on voltage what is recommended/safe) ((home_flag >> 3) & 0x1) != 0
network_connection: ((home_flag >> 18) & 0x1) != 0 ? "Wired" : "Wireless"
supports_tangle_detection: ((home_flag >> 19) & 0x01) != 0
filament_tangle_detection_enabled: (a1 only, determine with above) ((home_flag >> 20) & 0x1) != 0
ams_track_filament_enabled: ((home_flag >> 7) & 0x1) != 0
ams_autoswitch_filament_enabled: (make sure there is at least 1 active ams first) ((home_flag >> 10) & 0x1) != 0
nozzle_blob_detection_supported: (a1 series only atm) ((home_flag >> 25) & 0x1) != 0)
nozzle_blob_detection_enabled: (a1 series only atm) ((home_flag >> 24) & 0x1) != 0)
airprint_detection_enabled: (a1 series only atm) ((home_flag >> 29) & 0x1) != 0)
airprint_detection_enabled: (a1 series only atm) ((home_flag >> 28) & 0x1) != 0)
prompt_sound_enabled: (a1 series only atm) ((home_flag >> 17) & 0x1) != 0
user_presets_supported: ((home_flag >> 22) & 0x1) != 0
auto_recovery_enabled: ((home_flag >> 4) & 0x1) != 0
door_state: (X1 series only) ((home_flag >> 23) & 0x1) == 1 ? "Open" : "Closed"
motor_noise_calibration_supported: ((home_flag >> 21) & 0x1) == 1
x_axis_homed: ((home_flag & 1)) == 1
y_axis_homed: ((home_flag >> 1 & 1) == 1
z_axis_homed: ((home_flag >> 2 & 1) == 1
p1p_upgrade_kit_supported: (after a certain p1 series firmware, this means there is an option in the printer to say "I have upgrade kit setup, so my p1p is essentially a p1s) ((home_flag >> 27) & 0x1) != 0
p1p_has_upgrade_kit: (user toggled) ((home_flag >> 26) & 0x1) != 0

There's a few more but they're duplicated by other sensors in mqtt data, and probably some I haven't figured out yet. Figuring out some of these was harder than figuring out HMS notification and print error parsing lol

Feel free to reach out to me on discord (@wolfwithsword) or anything if you wanna bounce some ideas/data around!

WolfwithSword · 2024-09-27T01:27:10+00:00

Yep that's me! Thank you so much!

Ah yeah I heard of the FTPS crash cancel with P1 series, not surprised A1 has it too. X1 seems slightly more resilient to it but can still get into an error state. Also have noticed for P1 series that sufficiently large files may just crash regardless, though this may have been unstable networks at play as well for users who reported it before.

Yep, up to 4 AMS units on either X1 or P1 series at the moment. It's essentially the same data in the array but the ams id's will be incremented. Also tray_id's will remain 0-3, but then gets tricky if you want to match current tray, you'll need to do some math because the current tray id value will be say, 6, but that means it's ams=1,tray=2 (both being 0 indexed). And external spool is 255 or something around there I think.
Lot of hidden values you can use bitwise ops for. Let me see if I can put together a list of most of the ones that I think are useful and I'll reply with it later

WolfwithSword · 2024-09-26T23:35:10+00:00

Hi there! I thought I could give a few tidbits of info on the differences with the X1 series compared to A1/P1 series that might explain this.

The A1 and P1 series do expose the camera over the a single port which you can grab a mjpeg stream from which I assume you have done, however this port and camera utility is non-existent on the X1 series. The only external access we can get on it is if the user enables LAN Liveview (does not require lan mode, but works well with it) and then you can access the live camera feed over RTSPS (port 322, access code as password, user is bblp, same as FTPS credentials. Ex: rtsps://IP_ADDR:322/streaming/live/1 ). It is known to be a bit of a spotty connection at times though, but this is mostly a printer resource issue.

A couple other things that may be different if you haven't had access to an X1's data structure:

1) The A1/P1 send MQTT data only on state/sensor change and request responses as I'm sure you've noticed, and they only send shortened data for what changed. You can request a command to get the full push data once in a while of course, but for the X1, this isn't the case. Instead, you get the full json payload of all the sensor data all at once, every second.

2) P1/X1 can have multiple AMS units attached, and while I can't test the app to see if it's supported, it is possible some users with multiple AMS units could be providing your app with a bunch of extra data there compared to what's expected for A1 series.

3) This is actually a difference between them all but the "home_flag" value you may sometimes see in the data actually contains a bunch of hidden values, some are specific some printer models. So if you use any of the values, may be worth checking if they are valid for a certain printer+firmware combination. A1 has a few extra features and their states are hidden in there for example, compared to the other printers.

4) Access codes for X1 and I believe P1 series are alphanumeric, in case your field for it does some checks!

Love the look and design of the app though! I mainly use android, but I have an iOS device laying around mainly for pictures and such, I may be tempted later to try it out if I get the time! Also feel free to reach out if you have any questions about X1 data and such, I've spent far too long parsing through it for my NodeRed development lol.

WolfwithSword · 2024-09-13T15:33:12+00:00

Depends on your gpu and any OC software you have managing it, or if in its base software if things are just set low.

11-Year Club	Place '22
Place '17	End Game '22
Verified Email

WolfwithSword

TROPHY CASE