I installed yesterday's update and hass agent stopped working properly

[ars4l4n]

honestly if the update is that unstable that it instantly breaks something, then maybe don't shove it in my face via an annoying popup

anyway, the issue is:
right after the update hass agent couldnt establish a connection to HA anymore. I then headed inside the hass agent settings and changed the internal URL of my HA to the external one, because I thought maybe that could fix the issue

It actually did, but I'm noticing HA can't read HassAgent's LastActive sensors anymore, meaning that automations that are based on it don't fire at all anymore. On top of that, I'm not even seeing the LastActive entity in HA anymore. I am, however seeing an entity that is named differently in HA than in Hass agent that reports a last active value. the value displayed in HA does, however not correspond with the value shown on my hass agent. it seems like it stopped reporting from the time I installed the update onward.
On top of that, the last known value for this sensor shows 1h ago in HA agent, even though I'm actively using the PC right now and the report interval is set to 5m.

on top of that, it says local api: stopped on the hass agent screen, although I forgot if it did so before

[2025-02-07] HASS.Agent_20250208.log

hass agent 2.1.1

Home Assistant
Core
2024.7.2
Supervisor
2025.02.0
Operating System
12.4
Frontend
20240710.0

[ars4l4n]

update: I rebooted HA and it's receiving sensor values again. The problem is, the sensors got renamed from ARS_COMPUTER_lastactive to ARS_COMPUTER ARS_COMPUTER_lastactive etc.
Do I just fix this by renaming them under HA entities or do I have to expect further issues then?