H
HASS.Agent•5mo ago
zuldero

Doesn't open

i download the new version from "https://www.hass-agent.io/latest/getting-started/installation/" but it doesnt open the istaller. i tried it as admin and also closed the old version.
Solution:
can you launch cmd/powershell as administrator and then run
HASS.Agent.Installer.exe /LOG="install.log"...
Jump to solution
24 Replies
HASS.Agent Helper
HASS.Agent Helper•5mo ago
Help us Help Others!
To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution
From An unknown user
HASS.Agent Helper
HASS.Agent Helper•5mo ago
Help us Help You!
Please don't delete messages or posts because it makes it impossible to understand what happened. If you don't want your messages to be seen then don't post here. Please provide us with the version number of your client.
You can find it in the HA device info page after 'Firmware'.
Make sure to provide detailed reports of bugs.
Please include error log uploads and info about the bug.
HASS.Agent Helper
HASS.Agent Helper•5mo ago
@Amadeo
Amadeo
Amadeo•5mo ago
So you've downloaded the installer exe and after double clicking it nothing happens?
zuldero
zuldero•5mo ago
just the liddle loading icon beside the mouse. but this also vanishes in a few seconds. i also dont see anyting in taskmanager afterwards if it helps in any sens. i had to autostart the old version via task sceduler with admin rights. otherwise also nothing happend
Amadeo
Amadeo•5mo ago
That's not normal Do you have any custom/strange settings related to widows UAC/administrative rights?
zuldero
zuldero•5mo ago
no nothing that i know of
Amadeo
Amadeo•5mo ago
After double clicking the installer a UAC popup should be shown by windows asking for administrative privileges to perform the installation The thing that worries me is that you had to launch original hass.agent (not it's installer) as admin
zuldero
zuldero•5mo ago
evan if i launch it manualy it asks me for admin rights. if i go to properties the checkmark for "lanch as admin" is checked and grayd of. so i cant evan change it
Solution
Amadeo
Amadeo•5mo ago
can you launch cmd/powershell as administrator and then run
HASS.Agent.Installer.exe /LOG="install.log"
Amadeo
Amadeo•5mo ago
it should generate a log file
zuldero
zuldero•5mo ago
i need to this in the folder right?
Amadeo
Amadeo•5mo ago
?
zuldero
zuldero•5mo ago
cd to the folder of the istall file
Amadeo
Amadeo•5mo ago
yeah if the install.log won't be there try also with
/LOG=".\install.log"
if that also won't work we'll try full path
zuldero
zuldero•5mo ago
ok now it started ???
zuldero
zuldero•5mo ago
Amadeo
Amadeo•5mo ago
I think your UAC setup has some quirk/issue if starting it from already elevated context (administrative console) worked
zuldero
zuldero•5mo ago
yes now it worked. i evan have already deleted the old version. i just needed to new bind the ports for the local api with the button in the settings. thx for your guys work. i dont evan need to task scedule your version. it justs starts like it schould with the setting.
Amadeo
Amadeo•5mo ago
good that it worked 😄
zuldero
zuldero•5mo ago
thx for the help. but a bit offtopic. i still get the prefix warning in home assistant do i need to change some things manually to now?
Amadeo
Amadeo•5mo ago
yes, HA complains about "device name" being part for the "entity name" (I'll need to put that in a FAQ somewhere :D) you can either run (while HASS.Agent is turned off)
HASS.Agent.exe compat_names
from an elevated cmd/powershell (notce: not the installer, the exe of HASS.Agent itself in the "appdata/local" folder where it was installed) which will try to automatically remove the device name from entity names (there are sanity checks so it won't blatantly break your config) wherever possible or you can manually remove the device name from entity name by editing sensor/command, so instead of
SUMPC_cpuload
you'll need to set
cpuload
I'll ping you in a topic that this was also discussed 😄
zuldero
zuldero•5mo ago
perfect thx.
DrR0x
DrR0x•5mo ago
@zuldero There is also now guide available here: #entity-names