I’ve create a few notifications to get notified of statuses as they change state on my 3d printer, i.e., print errors, HMS errors, filament run-out, print finished etc. They do work and I can deliver a custom message based on that state. But this feels clunky, and it feels like I shouldn’t be constantly monitoring all of these states unless the 3d printer is actively running.
How this current seems to work is I create an automation > when (monitor some entity for state/change) > then send custom notification containing a static message and the state of that particular issue/change. The other side of this is if I create 15 or so of these for various issues that could happen this seems like a lot of automated constant state monitoring load and a lot of automation noise in HA.
My question is: Am I doing this the hard way or is there a more elegant way? I feel like this should be hierarchical. I thought about doing - when (look for state change to printing or not off something like that) > then add some (and if, if then) statements and nest all my conditions and messages under that. But I don’t think it will continuously monitor the (and if, if then) statements and fire them since I’m past that initial pass from the first (when). So thinking this isn’t going to work.
We know you’re creating automations tk manage each printer but without seeing those we have no clue.
Theres.
Is this the most efficient way to make this call
Is this the most efficient way to collect this x(a billion printers) without rewriting everything.
Is this the best way to handle 3d print
Is this the balest way to automate
Is this…
(see my point?) you just said I have a bunch of printers and I’m writing automations…
We need the actual automations (or a good representative sample) and some idea on what s important to you.
Me I just summarize the states and tell my ai to highlight when it’s borked but thats the long way around right now.
Hmm apologies, does this help? These are a few of what I’m trying to do. Basically I want to monitor/trigger certain states and send notifications including details on what state changed/needs attention. This isn’t always an error or something I need to run and look at. Print finished for example, would be nice to know but doesn’t need attention.
Also wanted to clarify this is only one printer, I don’t think I said I have multiple printers, just multiple values/states I want to monitor and send notifications on.
I just want the most efficient way to monitor these states and report on them, I don’t want 30+ automatons constantly checking states and using up CPU cycles when my printer is idle 90% of the time.
Also just from a manageability perspective want this in the HA UI as cleanly as I can make it. Right now each state/notification gets its own independent automation, starting to get noisy.
Maybe the answer is to leverage LLM AI in some way to monitor during a print I dunno.
I found this video, https://www.youtube.com/watch?v=lgikDHr6DE4, and I kinda like how it’s nested under a single automation at least. But still doesn’t address if it’s an issue or not with the constant polling of these states while the printer isn’t running.
There is the Bambu Integration in GitHub that can be loaded thru HACS. You then have an entity that polls for the event inside the Custom Integration instead of you doing it, if that is better for you…