I’ve done a bit a searching but can’t seem to find a solution. HASS.Agent is installed and working, I can see all of my configured sensors sending data in MQTTExplorer and I have an automation checking a sensor, which works so all looks good?
However, I’m getting this error in mosquitto broker every 5 seconds:
...
2022-09-10 16:16:21: New connection from 192.168.1.228:50413 on port 1883.
error: received null username or password for unpwd check
2022-09-10 16:16:21: Client <unknown> disconnected, not authorised.
2022-09-10 16:16:26: New connection from 192.168.1.228:50416 on port 1883.
error: received null username or password for unpwd check
2022-09-10 16:16:26: Client <unknown> disconnected, not authorised.
...
My device name in HASS.Agent does not have spaces, dots, etc, and is just a string “PAVILLION”. The topic is unchanged, “homeassistant” and I can see this working in MQTTExplorer. The device is seen in Devices and added to a dashboard. I’ve created an automation from the device and it works successfully turning on/off a smart plug based on battery change. These are only issues I’ve picked up on reading through this thread, have I missed something?
LOVE THIS thanks so much for creating it. So I am not the most tech savvy person, I have HASS Agent up and running and all is good I want to use the Wake on Lan, I configured NirSoft in the external tools, ensured WoL was set up correct on the windows box but am lost on how to get a button into HA in order to make it work. I did go through the doc’s and remember seeing some kind of example, do I just need to put that YAML into HA to make this work? Sorry for what is probably obvious but I am just not tracking. Thanks!
Can’t say I understand it all though. looking at the HA WoL info not sure if all the above is needed?
EDIT2- So I tried but failed. End result I am going for is to have the computer off, tap a switch on my phone (Android) in the HA App and have the computer start up.
Final Edit- Holy Crap- I figured it out. LOL Scared money can’t win so I decided to pull up my big boy pants and give it a shot, I mean what could go wrong right? Got lucky- but it works like a champ now!
Hi all!
'm trying now to test the Poweshell Screenshoot script example in the documentation, but I’m having problems since PowerShell complains that the network path is not found. I assume that thet script as written in the documentation assumes that Windows has a network folder from the Home Assistant instance mapped into windows, which is the one in this variable: "$Path = “\HOMEASSISTANT\config\www”. the Path in that variable has to be local in the Windows machine, right?
Hey @NachoMas, haven’t used that one myself, but I think it refers to the SMB share of your HA instance. So for example: \\192.168.0.50\config\www. You need the Samba share addon for this to work.
@SamKr Ah! I just assumed that it was HASS.Agent as it’s the only MQTT “thing” that I’ve (knowingly) installed on my laptop. However, the error persists when HASS.Agent is shutdown, the MQTTExplorer entries for PAVILION do not persist, so I guess it’s not HASS.Agent.
Sorry to bother you, I’ll start digging… Thanks for your guidance!
@ChrisThomas@SamKr i m running into the same issue the only thing i can come up with is HASS.Agent. mqtt is a struggle for me… can someone tell me where i could find the incomming messages / topics in HA i want to check if its really HASS.Agent. i did subscribe on the topic home/# with my ios device cant see very much there. I think i need another topic.
Hey @Sp0nsje, is HASS.Agent currently working? If you kept the default config, it’s publishing in homeassistant/ . You need to have at least one sensor/command configured before your device shows up in HA. Also, make sure you have autodiscover enabled in HA’s mqtt integration (not the addon) - though that should be enabled by default, some users reported it being disabled.
thanks,
I will take a look. I see sensors of my pc and they are updated in HA thats not the problem. also using pause / Break key to switch on lights in this room works like a charm. its just annoying that i get errors in the mqtt broker just like @ChrisThomas
@SamKr, I never checked my broker logs till seeing this post and @ChrisThomas .
Now that I’ve checked it, I too see these messages in my logs. Everything has been working fine for me since day 1. Just an fyi.
Closing out Hass Agent does not stop the log entries so it’s not likely being generated from there. The originating ip on my logs is from within docker with an ip of 172.30.32.1
This isnt the ip of any of my addon containers so my guess is that it’s from the docker host “itself” or it’s just the ip of the docker “gateway” (probably wrong terminology but I’m not docker expert. Know enough to be dangerous).
@SamKr …the plot thickens. As a test I disconnected the network cable from the pc that is using HassAgent and the logs stopped. reconnected and the logs started again after a short while.
Investigating…
EDIT:
So this was inaccurate. I closed hassagent from the tray icon but the service was still running. If I shutdown the service the error stops. The errors start again once I re-enable the service…so it’s defintely coming from HassAgent.
I’m not sure if this has been requested before but is it possible include sensors for disk usage that display as a percentage? I previously used IOT Link which had that sensor but made the switch to the HASS agent and would like to get it back.
Ah @stephack, @ChrisThomas and @Sp0nsje - did you by chance not (completely) configure the service’s mqtt? If not, and your broker is reachable by the default address, it would try to login anonymously.
In a next version, that’ll be fixed - it’ll just use hass.agent’s credentials by default to avoid this.
@SamKr Do you mean are the credentials used in HASS.Agent? If so, the credentials I used was for the MQTT user I’d previously created.
I am poking around confirming credentials used everywhere. I have confirmed that it is my laptop that’s the cause of these errors though, when disconnected the errors stop. Today, I’ll do more digging.
No the service specifically - you can set them by going to satellite service in the main window, then the MQTT tab. You can use the copy from hass.agent to easily duplicate the settings (it’ll use another client id) and then send and activate config:
Thanks for sharing, happy it’s working!
