Brightness getting set to long decimal value

[FiveElementNinja]

Thanks for adding the brightness control in the latest firmware. I've been testing it out and found a couple things.

First, for some reason the brightness value is getting set to a decimal (float?) value after being changed. In the screenshot below I set the brightness to 15 and then it automatically gets set to 15 with a long decimal. I'm not sure what causes this, but it doesn't seem to be affecting anything as far as I can tell. Just thought I'd call it out.

The only downside is that in the app the decimal is so long that it causes a horizontal scrollbar.

The only other thing I noticed is that the brightness value isn't saved, so in the event of power loss it reverts to a default value and needs to be set again. I assume it wasn't built to preserve that value, but it would be nice if it did.

---

Installation method	Home Assistant OS
Core	2026.4.2
Supervisor	2026.04.0
Operating System	17.2
Frontend	20260325.7
AirCube Firmware	1.4.0
AirCube HA Integration	ZHA

[StuckAtPrototype]

Thanks for pointing this out! I will change this. As for the device behavior, that is correct, it does not save the brightness to eeprom. However, if you use the button on the back, that will set the "default". I did this as the brightness can change very often. the eeprom is based on flash memory and it has a limited (10k) write cycles. But, again if you want to set a default, use the button on the back. Single tap it. Hope this helps!

[FiveElementNinja]

@StuckAtPrototype Ah, I didn't know you could use the button to set a default. That's exactly what I needed. Thanks!

[Odietech]

I have experienced this as well. If you change the brightness setting, it reverts back to two digits. But when you load into HA again the long digit format will be back. What I mean is when I log in from another machine.