Alright, let’s see if we can find out why. In Home Assistant, please go to Configuration → Devices & Services → Devices, then type the name of your PC. Click on your device, and there should be a list of entities under Sensors. If nothing drive-related is showing here, they’re not arriving in HA properly.
In that case, could you look through HASS.Agent’s logs to see if there are any errors or exceptions? If you’ve used the installer, they’re located in %appdata%\LAB02 Research\HASS.Agent\Logs.
If there are no exceptions or errors showing in the logs, could you also check Home Assistant’s logs? You can find them by going to Configuration → Settings → Logs.
I do receive MQTT disconnect notifications and failed to connect to MQTT. Surprised by this as my MQTT broker is rock solid and configuration is correct.
What topics does HASS.Agent use and does it create these or does the HA part do that? Is this likely a never able to connect to MQTT or a connect but often disconnect later issue. I get a notification about every hour.
That is weird. HASS.Agent uses homeassistant/sensor/{device_name}, you can use a MQTT client to subscribe and see what gets sent.
What broker do you use? Are the sensors working (did they get added in HA) or not at all? Are there any additional messages in HASS.Agent’s logs? Is your PC on the same network as your broker?
This is everything in %appdata%\LAB02 Research\HASS.Agent\Logs. Configuration → Settings → Logs shows nothing specially related to MQTT or HASS.agent
The mosquitto broker integration shows 1 device with 3 entities: cpu load, last boot and memory usage. No storage sensors.
Oops! I somehow misread the documentation of the command section and was under the impression it would allow me to trigger the execution of commands on the HA server, not the other way around.
It took me a while to figure out that commands are exposed as switches in HA, but I got it working now
Hi @amplitur, for starters thanks you for your donation! Very kind, should keep me fueled for coding
You can already name your sensors when creating them, HASS.Agent pre-fills the field with the sensor’s name. But it’s a good idea to prepend the machine name as well (and give the option to define your own value), will add in the next version!
I didn’t realize that one can change the name of the sensors, the dark grey background of the input field tricked my mind into assuming that this value cannot be changed. Perhaps change the background of the input fields for name and seconds to the same light grey as the “type” field? At least for me, that would be a more intuitive way of indicating that these three fields are input fields where the value can be changed by the user (as opposed to the sensor description field).
Having a configurable pre-fix (default set to the machine name) which would be inserted automatically if defined will be an extra bonus.
Regarding the sensor names: Manually changing the sensor name e.g. to LL2020_sensorname works for all sensors with one exception: the multi-value Network sensor. Even when changing the name to “LL2020_Network” the actual names assigned for the values still all start with "NIC ".
About the naming; you’re right, will fix. I only see network sensors in your screenshots, no storage sensors, what parsing is going wrong? Or do you mean the addresses? Because those seem ok, they’re sent as a string array which you can in turn parse in Home Assistant.
Sorry, I meant the network sensor values. Agreed, the attribute “dns_addresses” can have multiple values/addresses. Couple of observations:
I don’t see a sensor name for sensor.nic_bluetooth_network_connection_dns_addresses displayed in the example above. I am not sure why it’s not being displayed, as the sensor has a name. Most (but not all) of my other NIC dns_addresses and ip_addresses sensors have a similar behaviour, e.g. sensor.nic_bluetooth_network_connection_ip_addresses.
Having the name of the attribute as part of the value of the attribute is somewhat redundant, so perhaps instead of assigning the value {“dns_addresses”:[“fec0:0:0:ffff::1%1”,“fec0:0:0:ffff::2%1”,“fec0:0:0:ffff::3%1”]} you could just use [“fec0:0:0:ffff::1%1”,“fec0:0:0:ffff::2%1”,“fec0:0:0:ffff::3%1”] instead?
Hi. Thank you for the great app that works out of box.
Could someone provide an example of WMI query or some manual how it should look? I was trying to make Intel NUC’ LED work with HASS notifications without any luck. And I noticed from the doc that WMI sensor could be a pain. Thank you.
Hi @IvanUA, thanks! Always glad to hear it works on other people’s PC as well as mine
The WMI querys you refer to are for sensors, so they are designed to fetch values, not set them. In your case, you want to set a value. The easiest way to do this is to make a custom command to launch a powershell script, in which you execute the WMI query.
If you want, I can write an example powershell script you can use. But since I’m away, you’ll have to wait a bit. If you want to try yourself, here’s an example WMI script in C# for your NUC (so it has to be converted to Powershell).
In case you also want to fetch values from your NUC, this site contains some more info.
And I noticed from the doc that WMI sensor could be a pain.
It can, but it can be useful. Just keep an eye on how much CPU HASS.Agent uses, and also Windows’ WMI executable (wmiprvse.exe I think). In some cases WMI can start using lots of CPU, but that can be fixed, so if it does let me know.
