spaceapid: adjustments to 3d printer state sensors #8

Merged

june merged 1 commit from dx/nix-infra:3d-printer-state-part-2 into main

2024-10-27 17:06:05 +01:00

dx commented

2024-08-17 23:20:29 +02:00

Member

Prefix sensor names with ext_ as the spec says we should use that for
extensions (this also improves attribute access for tools that don't
like fields starting with a number)
Rename printer state to printer busy state, to make it clearer.
Add ext_3d_printer_minutes_remaining sensors

Talked to @bendodroid and got some feedback to refine this

This is marked as WIP because it requires changes in home assistant:

The last two steps that hit the REST endpoint to update 3d_printer_state should now hit ext_3d_printer_busy_state
ext_3d_printer_minutes_remaining needs a new automation that triggers every minute when a printer is printing. The tricky part of this one is that we get the finish time in absolute time from the entity, and we want to turn that into relative time in minutes. I don't know how difficult this is, likely involves writing some pseudopython in the jinja value template.

The first change is a breaking change (of an unannounced feature that only i am using currently), but it is easy enough. If someone wants to do that for me, this can be merged and deployed.

The second one can stay as 0 until the next time I visit club and implement that. (Unless, of course, someone else wants to take that challenge)

- Prefix sensor names with ext_ as the spec says we should use that for extensions (this also improves attribute access for tools that don't like fields starting with a number) - Rename printer state to printer busy state, to make it clearer. - Add ext_3d_printer_minutes_remaining sensors ---- Talked to @bendodroid and got some feedback to refine this This is marked as WIP because it requires changes in home assistant: 1. The last two steps that hit the REST endpoint to update `3d_printer_state` should now hit `ext_3d_printer_busy_state` 2. `ext_3d_printer_minutes_remaining` needs a new automation that triggers every minute when a printer is printing. The tricky part of this one is that we get the finish time in absolute time from the entity, and we want to turn that into relative time in minutes. I don't know how difficult this is, likely involves writing some pseudopython in the jinja value template. The first change is a breaking change (of an unannounced feature that only i am using currently), but it is easy enough. If someone wants to do that for me, this can be merged and deployed. The second one can stay as 0 until the next time I visit club and implement that. (Unless, of course, someone else wants to take that challenge)