mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #713] [Feature]: Multiple Switches for a single Printer #474
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#474
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ManuelW77 on GitHub (Mar 15, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/713
Originally assigned to: @maziggy on GitHub.
Problem or Use Case
If i have multiple switches for a single printer, a heater as example, i only have the second switch as a script link. It would be nice, to have the row as the first switch is.
Proposed Solution
A second row for a second switch with options for auto off.
For a heater as example set off as soon as the print is done.
Alternatives Considered
No response
Feature Category
Smart Plugs
Priority
Critical for my use case
Mockups or Examples
No response
Contribution
Checklist
@maziggy commented on GitHub (Mar 15, 2026):
Since we are talking about HA switch entities, why don't you automate it on the HA side?
@ManuelW77 commented on GitHub (Mar 15, 2026):
Because i don't want automations here and there and it is critical function to disable a heater. So it's more safe to have it at one place.
One of ,my reasons to switch to bambuddy is, to have all at one place.
@maziggy commented on GitHub (Mar 15, 2026):
Got it. This would require a complete refactoring of the power plugs implementation. Not sure if it's woth the work.
Anyway, I leave it in the queue to pick it up on a later point in time again.
@ManuelW77 commented on GitHub (Mar 22, 2026):
Ok, can i do this?
@maziggy commented on GitHub (Mar 22, 2026):
Yes...sure, already assigned the issue to you. But please follow our rules. Thanks!
@ManuelW77 commented on GitHub (Mar 22, 2026):
i give my best, hope its fine now :)
@maziggy commented on GitHub (Mar 23, 2026):
Had to revert and clode your PR. See commment in PR.