Bug: Satellite Service shows wrong LoggedUser value
Describe the bug
I've activated loggeduser sensor in the satellite service (I'm particularly interested in knowing who's using the PC...) but I get a weird value.
So I activated loggedusers and local loggeduser to compare:
- satellite
loggeduser:HSHOME$<-- What? HSHOME is the PC name... - satellite
loggedusers:["Henrik"]<-- that's correct, it's me. - local
loggeduser:Henrik<-- that's correct, it's me.
To Reproduce
I suppose that's enough to enable loggeduser on the satellite service to see that.
Expected behavior
The sensor should have the same value as the local loggeduser sensor!
Screenshots
Here a screenshot of MQTT values taken from MQTT explorer:

Misc info (please complete the following information):
- Windows build:
- Windows' UI language: Italian
- HASS.Agent version: 2022.13.0-beta2
Please check what's applicable (multiple answers possible):
- [x] Installed via installer
- [ ] Installed manually
- [ ] Problem occurs in HASS.Agent
- [x] Problem occurs in Satellite Service
Additional context I'm the only one logged at the moment, using a regular desktop (not remote) so it's the nominal situation, I'm not expecting to get wrong value.
Logs satellite:
2022-09-01 00:19:40.397 +02:00 [INF] [MAIN] Version: 2022.15.0.0
2022-09-01 00:19:40.416 +02:00 [INF] [MAIN] Service started, initializing ..
2022-09-01 00:19:41.660 +02:00 [INF] [MAIN] Running as a service, initializing lifetime manager
2022-09-01 00:19:41.704 +02:00 [INF] [LIFETIMEMANAGER] Initialized
2022-09-01 00:19:41.731 +02:00 [INF] [WORKER] Startup completed, commencing execution ..
2022-09-01 00:19:41.734 +02:00 [INF] [SETTINGS] Config storage path: C:\Program Files (x86)\LAB02 Research\HASS.Agent Satellite Service\config
2022-09-01 00:19:42.011 +02:00 [INF] [SETTINGS] Configuration loaded
2022-09-01 00:19:42.019 +02:00 [INF] [SETTINGS] MQTT configuration loaded
2022-09-01 00:19:42.020 +02:00 [INF] [SETTINGS_COMMANDS] Config not found, no entities loaded
2022-09-01 00:19:42.036 +02:00 [INF] Application started. Hosting environment: Production; Content root path: C:\Program Files (x86)\LAB02 Research\HASS.Agent Satellite Service\
2022-09-01 00:19:42.037 +02:00 [INF] [SETTINGS_SENSORS] Loaded 0 entities
2022-09-01 00:19:42.102 +02:00 [INF] [MQTT] Identifying as device: HSHOME-satellite
2022-09-01 00:19:42.207 +02:00 [INF] [MQTT] Connecting ..
2022-09-01 00:19:42.227 +02:00 [INF] [RPCMANAGER] Listening
2022-09-01 00:19:42.267 +02:00 [INF] [MQTT] Connected
2022-09-01 00:19:44.220 +02:00 [INF] [MQTT] Initial registration completed
2022-09-01 00:20:40.473 +02:00 [INF] [SENSORSMANAGER] Processing 1 received sensor(s), deleting 0 sensor(s) ..
2022-09-01 00:20:40.569 +02:00 [INF] [SENSORS] Added single-value sensor: HSHOME_satellite_loggeduser
2022-09-01 00:20:40.602 +02:00 [INF] [SETTINGS_SENSORS] Stored 1 entities
2022-09-01 00:21:36.182 +02:00 [INF] [SENSORSMANAGER] Processing 1 received sensor(s), deleting 0 sensor(s) ..
2022-09-01 00:21:36.183 +02:00 [INF] [SENSORS] Single-value sensor changed name, re-registering as new entity: HSHOME_satellite_loggeduser to HSHOME_satellite_loggedusers
2022-09-01 00:21:36.193 +02:00 [INF] [SENSORS] Modified single-value sensor: HSHOME_satellite_loggedusers
2022-09-01 00:21:36.194 +02:00 [INF] [SETTINGS_SENSORS] Stored 1 entities
2022-09-01 00:22:47.184 +02:00 [INF] [SENSORSMANAGER] Processing 2 received sensor(s), deleting 0 sensor(s) ..
2022-09-01 00:22:47.195 +02:00 [INF] [SENSORS] Modified single-value sensor: HSHOME_satellite_loggedusers
2022-09-01 00:22:47.201 +02:00 [INF] [SENSORS] Added single-value sensor: HSHOME_satellite_loggeduser
2022-09-01 00:22:47.202 +02:00 [INF] [SETTINGS_SENSORS] Stored 2 entities
The following row seems relevant to the issue to me... 2022-09-01 00:21:36.183 +02:00 [INF] [SENSORS] Single-value sensor changed name, re-registering as new entity: HSHOME_satellite_loggeduser to HSHOME_satellite_loggedusers
Hi @energywave,
Good catch, thanks! I'll look into it
You can try the latest beta, should be fixed: https://github.com/LAB02-Research/HASS.Agent/releases/tag/2022.14.0-beta1
Fixed in https://github.com/LAB02-Research/HASS.Agent/releases/tag/2022.14.0