UI Improvements for A1 Mini

[informagico]

Hello, as anticipated here I made some changes to the A1 Mini cards for the HACS integration.

Files changed:

• Changed A1 Mini ON/OFF images for improved quality, focus and changed light direction (the lighton should work file for both dark and light themes)
• Changed AMS Lite image with more quality but from a different angle

individual_ams_lite.yaml:

• Changed the spools labels and icons to adapt them to the new image
• Fixed issue where empty spool icon (mdi:tray) was not showing due to the sensor returning a color with alpha-channel = 0 when empty
• Improved readability of the values (basically removed shadow and adder solid borders)
• Sorted AMS trays in the list

individual_control.yaml:

• Fix issue with smart plug button placement (aspect_radio: 2 -> 1)
• Reduced gap-card heights
• Add "Firmware update" entity to the list

individual_printer_image_a1mini.yaml:

• Changed heat sensors positions to adapt them to the new image
• Changed state-badge elements color

---

I also added the individual_ams_lite_details.yaml card template which includes the following entities:

• sensor.{HA_PRINTER_DEVICE_NAME}_ams_1_humidity_index
• sensor.{HA_PRINTER_DEVICE_NAME}_active_tray
• sensor.{HA_PRINTER_DEVICE_NAME}_ams_1_tray_1
• sensor.{HA_PRINTER_DEVICE_NAME}_ams_1_tray_2
• sensor.{HA_PRINTER_DEVICE_NAME}_ams_1_tray_3
• sensor.{HA_PRINTER_DEVICE_NAME}_ams_1_tray_4

---

Preview

---

Things I cannot verify:

• In the individual_ams_lite.yaml the initial conditions cannot be met because in the HACS integration there is no sensor.{HA_AMS_DEVICE_NAME}_id entity
• Model preview positioning in the image because I don't have the image.{HA_PRINTER_DEVICE_NAME}_cover_image entity (see NOTE)
• There is still something weird in the fan_temps_control.yaml card, in my case I am not able to understand how the aux_fan entity is controlled (if it is actually controllabel) and seems to have only the possibility to control the cooling_fan, also with some strange behaviours. Possibly related to the HACS integration (???)

Please let me know if anything is messed up and/or if you need me to make some changes 😄

NOTE: I tested and verified these changes only with the HACS Integration in Lan Mode Configuration (I have 2FA on my account and cannot use Bambu Cloud).

[WolfwithSword]

Great work! Been meaning to get a cleaner ams-lite image at some point but had trouble finding one.

Going to take a deeper look later and test it out locally (I don't have an A1 but that's mostly just cosmetic. Will load in my X1's data into it).

Couple things to note:

• Can you provide an image with one of the AMS trays in use? The border colour change to remove blur makes sense for AMS-Lite as it is an "open" image more or less, but I want to make sure the yellow in-use indicator still work. I checked it, looks fine but left a comment for removing it from the labels.
• Sorted AMS trays in the list Not quite sure what this means, do you mean the order/placement of the trays in the image? Just want to verify that it lines up properly to what is actually tray 1/2/3/4 (0/1/2/3) and in the image.
• Fix issue with smart plug button placement (aspect_radio: 2 -> 1) Can you do a comparison of the before and after?
• Add "Firmware update" entity to the list Good catch, didn't know HACs had this as a sensor so I'll keep it
• I also added the individual_ams_lite_details.yaml I'm 50/50 on adding this since it's something that can also apply to original AMs units, but also it's quite simple as it's just a list of entities, all of which you can get by the AMS image card. Anyone can easily add this on their own.

Addressing questions:

• In the individual_ams_lite.yaml the initial conditions cannot be met This is fine. These elements only appear if they exist due to the conditionals. This was added to all the hacs yamls in case they ever added the sensor but also to help with maintainability for me between the hacs yamls and my nodered yamls (which are the primary ones I develop for). It's just for the ID Number display which is helpful for multi-AMS systems, and who knows when A1 will eventually get that support.
• Model preview positioning in the image I'll test this with my nodered data, since I get the image direct from the 3mf file, no cloud needed.
• There is still something weird in the fan_temps_control.yaml This might be hacs integration related. Each fan entity in there only shows if the fan entity exists, but as for control goes they don't do anything different. In this case I am thinking - The A1 does not have an aux fan, but the mqtt data the integration uses to generate the entities probably still says it's there. If you see the Aux fan in your Device in the integration, but doesn't do anything because non exists, I suggest making an issue on the hacs repo that A1/A1Mini's don't have an Aux fan so it should be disabled. I'll probably do the same in my nodered integration as I've never thought it would still report the data for it.

Also - feel free to keep your work to just the HACs version of the yamls. I will attempt to port them to my NodeRed versions for the approved changes for parity :)

[informagico]

Sure! Tomorrow I'll take a look to all your comments 😊

[WolfwithSword]

FYI I also changed the target branch to https://github.com/WolfwithSword/Bambu-HomeAssistant-Flows/tree/a1_mini_update such that I can sync equivalent nodered version changes before pushing to main branch all at once.

[informagico]

• Sorted AMS trays in the list WolfwithSword: Not quite sure what this means, do you mean the order/placement of the trays in the image? Just want to verify that it lines up properly to what is actually tray 1/2/3/4 (0/1/2/3) and in the image. informagico: see here

• Fix issue with smart plug button placement (aspect_radio: 2 -> 1) WolfwithSword: Can you do a comparison of the before and after? informagico: this is aspect_ratio: 2 this is aspect_ratio: 1 it actually needs some more polish on positioning, I'll open an issue for this (don't know if maybe is just on my side, how do you see it?)

• There is still something weird in the fan_temps_control.yaml WolfwithSword: This might be hacs integration related. Each fan entity in there only shows if the fan entity exists, but as for control goes they don't do anything different. In this case I am thinking - The A1 does not have an aux fan, but the mqtt data the integration uses to generate the entities probably still says it's there. If you see the Aux fan in your Device in the integration, but doesn't do anything because non exists, I suggest making an issue on the hacs repo that A1/A1Mini's don't have an Aux fan so it should be disabled. I'll probably do the same in my nodered integration as I've never thought it would still report the data for it. informagico: yes, I'll open an issue on the HACS integration because it's behaving in a really strange way. It seems that AUX fan can be commanded but, as you said, there is no AUX fan in the A1 Mini and in reality it do nothing on the printer. When I command the COOLING fan, the AUX value follows the commanded value (actually with an higher responsiveness, strange): This is the fan speed graph so there is for sure something odd happening

[WolfwithSword]

Ah okay good, just wanted to make sure the AMS tray order is matching the new angle you have, so that's all good

For the button aspect ration, I think that depends on the text you have for the title. Mine without your changes (aspect_ratio:2):

With aspect ratio 1:

Hmm, if that's the case I might be inclined to push that out for a different investigation to modify, best to leave it at 2 for now.

And finally for the fan temp control, I wonder if for the A1 Mini the HACs integration is using the mqtt name for aux fan as the name for cooling fan instead. But regardless, they are all still present as fan entities so it is a bit weird.

Once you address some of the comment questions then I'll check again, merge to the a1mini branch and then work on the nodered versions. After that I will start process for the update version / release / merge to main.

[informagico]

For the aspect-ratio thing I have fiddled around trying to find a suitable solution (layout-card / grids / ...) but apparently there is no pratical solution I am aware of. Will think about it later, maybe it is even not that necessary to have that title and just show the button (with custom description?) if user has the switch available, otherwise just show nothing. What's your opinion?

[informagico]

Ok, finished on my side just take your time to review changes and let me know 😃

Also, opened issue here for the fans

[WolfwithSword]

maybe it is even not that necessary to have that title and just show the button (with custom description?) if user has the switch available, otherwise just show nothing. What's your opinion?

Eh some people liked having the title there and treat it like some "labelled remote". Personally I'm indifferent but it is handy visually to weigh out the power button too. I think then it might be a case of "user can try tweaking the value if it's off in their screen res / ratio".

Will review the new changes today and test them out!

[WolfwithSword]

Everything looks good - just one comment on aspect_ratio. Hoping to tackle merging the changes to the nodered versions as well this weekend and then next week merge to main (which auto updates the configurators on the site - they just pull from the raw files from main branch and do string replacement on everything in {TEXT}'s FYI).