You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
That’s not complaining- I like this change to follow real naming :)
In case someone also automated AMS filament tracking and is parsing attributes per AMS / External slot:
Currently it’s no longer i.e “AMS Slot 1” but “AMS 1 Tray 1”. External spool was also “AMS Slot 1 previously” not checked what it’s now.
Luckily for me it’s just timeslot of 6 possible hours for fixing missing print weights (few prints) but if someone have it used in farm in HA - you might miss it (personally I forgot to make a check in automation if print_weight == sum of all parsed weights).
The text was updated successfully, but these errors were encountered:
And in created file “!sensor.yaml” on the same folder level: ams_a1_printweight: friendly_name: "AMS A1 PrintWeight" value_template: "{{ (state_attr('sensor.replicator_print_weight', 'AMS 1 Tray 1')) |float(0) }}" unit_of_measurement: 'g'
After that reboot HA (perform Developer Tools -> “check configuration”) or just click
after checking configuration on “All yaml configuration” in “YAML configuration reloading part”
Hello,
That’s not complaining- I like this change to follow real naming :)
In case someone also automated AMS filament tracking and is parsing attributes per AMS / External slot:
Currently it’s no longer i.e “AMS Slot 1” but “AMS 1 Tray 1”. External spool was also “AMS Slot 1 previously” not checked what it’s now.
Luckily for me it’s just timeslot of 6 possible hours for fixing missing print weights (few prints) but if someone have it used in farm in HA - you might miss it (personally I forgot to make a check in automation if print_weight == sum of all parsed weights).
The text was updated successfully, but these errors were encountered: