how to get started - migration?
hello!
I've read the docs but not sure about a couple of things. At the moment, I have the old HASS.agent service and satellite running with Win10 computer and HA(HAOS). Do I have to uninstall the Windows program and use the new beta? do I have to remove the HA integration also and replace that, also? thanks...
Solution:
From a simple point of view, to test the 2.0.1 version:
1. backup your current "config" folder (there's never enough backups)
2. run the installer, select "migrate" option at the end
3. done...
Problem installing Windows App Runtime
Hello there. While trying to install the 2023.11.1-ubeta of Hass.Agent and following the manual installation steps provided here
https://github.com/amadeo-alex/HASS.Agent/blob/main/README.md, I am running into the Issue, that I get the Error Message, that Windows App Runtime Version 1.3 is required.
What I've tried so far:
- Installing Windows App SDK 1.4.3, 1.4,2, 1.3.3 and 1.3.0...
Solution:
This will be fixed with "2.0.0" release as the app sdk will be bundled with the app itself

Satellite service crash when adding gpuload sensor
When I add the gpuload sensor, the service crashes. On restart, the gpuload sensor is not included as a sensor. Attached is the satellite log. Interestingly, it states "Processing 10 received sensor(s)", but only 9 sensors are written to the log before the crash.
Also attached is two events from the Windows Event Log that correlate with the crash....
Solution:
Error adding custom command
Specs
Version:
2023.11.1-ubeta
The friendly name of commands is copied from the actual name always, therefore it is not modifiable.
...Solution:
ok, I have a fix for this and in the meantime found 2 more bugs 😄
Command friendly name not working
Specs
Version:
2023.11.1-ubeta
The friendly name of commands is copied from the actual name always, therefore it is not modifiable.
...Solution:
Fixed in 2.0.0+

Access to Global path is denied in the app during startup
Specs
Version:
2023.11.1-ubeta
During startup of HASS.Agent immediately after the [INTERNALSENSORS]
are ready HASS.Agent spits out an error to the extended logs. Full log file is attached, the main error code is below
```...Solution:
Not a bug then, FTLs are also exceptions which are cought and handled down the line by code
Device/entity shows as unavailable
Tried deleting and readding in HASS, but still shows as unavailable despite detecting the HASS.Agent. Configuration also shows everything connected and running.
Solution:
yeah, it's behind docker reverse proxy; found and fixed, it all works now, thanks!
Welcome to discussions! 💬 Please follow the guidelines 🙌
Discussions are the main way you can get help with anything Hass.agent related. It's easy to get started, just click new post and make sure to follow the guidelines and add a tag to categorise your post. If it's unrelated to hass.agent then use #🛰・general.