Wooting 80HE no response to volume level change

[brave relic]

So as the title says after i did the updates todaz to the v5.3.0 wootility update and the firmware update to v2.13 on my 80HE the volume level effect for the light indicator stopped working other effects i tried like caps lock indicator or key depth worked fine tho so as i looked at more effects all effects related to wooting background services stopped working i tried to reinstall it do system restart but nothing i didn't paz that much attention to 100% be sure when these effects stopped working but i know that a few days ago everything worked fine and since than i have just done todays wootility and firmware update to the 80he and no windows update as far as i remember

[empty inlet]

Thanks for posting your support request!

Note: #community_support is only for answering general questions and for troubleshooting.
All order-specific and shipment-specific support must be handled via the Wooting Support Wizard*
(You need to create an account on the Wooting Hub, using the same email address as your purchase. The account is not created for you automatically!)

Troubleshooting your Wooting Keyboard? Try these steps first!
Basic Troubleshooting

Questions about shipping, or what to do if your shipment has a problem?
Possible Problems During Shipping (with Solutions)

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, update your shipping address, and much more.

Is your order about to ship and you need to pause it for any reason?
Place it on hold via the Wooting Hub!

Do you need to...

• Cancel an order?
• Return/Refund an order?
• Get assistance with placing an order?
• Change the items in your order?
• Change your shipping address to a different country?
• Return a recent purchase?
• Get warranty support?

All of these types of requests need to be made via the Wooting Support Wizard!

[tall elk]

i have the same issue with the ram usage under lighting indicator

[slim swift]

@brave relic @tall elk Hey, we released update 0.4.8 for Background Service which should resolve this issue

[brave relic]

Thanks for the fast response when i get home i will try it out

[brave relic]

just got home and tried it out yeah it's fixed thanks again for the fast response also if it's not something that you can't disclose what kind of issue caused this to happen or was it some kind of implementation change in the new firmware for the keyboard that needed a change in the background services as well (i understand if you can't answer, this is just my curiosity as an aspiring software engineer)