HASS.Agent: Windows client to receive notifications, use commands, sensors, quick actions and more!

Share your Projects!
, , , ,
265

Hi and thanks. I’ve set this up on two different laptops and I can see the sensors on both. What I’d like to do is to be able to send notifications to either laptop but I can only see one option. I pasted the code into my configuration.yaml and it works fine for one laptop. But I can’t fathom out how to add a notify for a second laptop. It seems that whatever do, only one laptop appears in the list of call services. I’ve tried adding another (indented) name, platform and resource to the existing notify: and I’ve tried creating a second notify: with a second name, platform and resource but neither one will show both laptops as notify services. What am I doing wrong?

EDIT. Just seen the above post - I’ll try that.

EDIT2. Just tried the above and now both end point do show up. However, I’m not receiving the notification I send to the second laptop. I’ve double checked and tripple checked the IP address which is correct.

EDIT3. The test notification doesn’t show up locally on this second PC - must be something I need to configure locally…

EDIT 4 - Notifications were turned off on that laptop - all good now !

1 Like
266

I love how your post reads - it’s like a tiny novel :stuck_out_tongue: Thanks for the updates

1 Like
267

Difficult to debug then. You might need to run sfc multiple times, otherwise, check the logs to see what’s going wrong.

Does it keep running when you don’t open the gui?

268

Yep see if messages are going ok. Did you change the base mqtt topic (default is homeassistant)? And perhaps disabled mqtt auto discovery (default is enabled, but depends on how old your HA instance is). Any errors in HA’s logs?

269

With logs you mean the Event viewer application logs?

That doesn’t give me much besides the logs I already shared. The application also crashed if I don’t use the GUI. If I open the HASS agent application to basically view my HomeAssistant setup via that, it works the first time. Second time it crashes with the mentioned errors.

270

Ran sfc also several times, it doesn’t find any issues.

271

That’s going to be hard to debug than. I’ll update the used packages on the next beta, see if that helps

272

What’s the current advice for installing on a machine with multiple users? Currently only the user that installs the agent can run the agent as it’s installed in their roaming profile folder. Other logged in users don’t have file access to that folder without some permission modifications.

273

When is that going to be available?

274

You can use the zip package: https://github.com/LAB02-Research/HASS.Agent/releases/download/2022.12.0/HASS.Agent.zip

Place it somewhere the user has read/write rights (so not program files).

275

Pretty much ‘when it’s ready’, but should be in two weeks or so.

276

Did the PrintQueue sensor ever get added ??

The printer driver updated recently and the text for print dialogue changed so the NamedWindow sensor stopped working.

277

Nothing got added yet (vacation) but I’ll try to add it to the next beta as well.

278

Hello,

everything goes quite well and is easy to configure. Very nice.

But now a problem: Notify on the PC does not work. My constellation is:
The Home Assistant computer is in the DMZ (IP 192.168.1.x), the Windows computer is in a network behind it (IP 192.168.2.x) for safety’s sake. I have opened port 5115 and can call up the sensors of the PC in HA. But messages with notify do not arrive. (The test with local messages works.)
There is no trace of the attempt in the log. Do I have to set more or different settings in the firewall than for all computers in a network segment?

Greetings, Eckart

279

HA needs to be able to reach the PC for notifications to work (so that’s the reverse from how MQTT works). You may need to configure the correct forwarding/routing to be able to reach the 2.0/24 network.

Try this manual:

https://hassagent.readthedocs.io/en/latest/notifications/notification-debugging-ha-side/

Does the HA logs give anything? Chances are HA isn’t able to reach your PC, if it doesn’t know a route to get to the 2.0/24 network.

280

Just found out about this and started using it and love it so far but I had a question I am having a hard time trying to find the answer too.

I use IOTLink and have a specific automation I run for a server I have to do remote downloads through mega based on a url I update for an input helper I have.

Here is what the MQTT publish action looks like:

service: mqtt.publish
data:
  topic: iotlink/workgroup/server/commands/run
  payload: ' {"command": "C:\\Users\\mysystemuser\\AppData\\Local\\MEGAcmd\\MEGAclient.exe", "path": "C:\\Users\\mysystemuser\\AppData\\Local\\MEGAcmd\\", "args": "get {{ states(''input_text.mega_download'') }} B:\\Downloads\\files\\", "user": "", "visible": "true", "fallback": "true"}'

Would I be able to send a similar command like this with HASS.Agent? I would really like to remove IOTLik completely if possible and this is the one thing holding me back.

281

Yup auto discovery was disabled. Enabled it and everything is showing up great. Thanks!

1 Like
282

Hey @Deathbot64,

Yep, you can do that using command actions: Actions Usage and Examples - HASS.Agent

283

Hey @SamKr.

Thank you for that but how do I get this to work. With iotlink I could just send a command right from ha without making anything on the system side. How do I do this for Hass agent

284

That’s explained in the doc I linked. More info about commands in general can be found here: Command Basics - HASS.Agent