Widely customizable: More systems and informations can be monitored and controlled via development of future Addons.
Easy to use: Easy Installer provided and Minimal initial configuration required.
Fully Integrated: Working as a Windows Service to provide reliable data as soon as the windows boot up, without having to wait for a windows user logon.
Open source software: Both IOT Link API and Engine are open-source. Developers are welcome to send Merge Requests or develop their own addons.
Are you using Windows 10? Can you check the logs? Any errors will be displayed there. You can check it using the shortcut placed under your start menu.
Also there is a page dedicated to try to troubleshoot the problems:
If there is nothing under the logs, It might be something in your Home Assistant configuration? You can post it here if you need help.
@Rasser
It is not possible to track temperatures yet, specially because there is no standard APIs
I don’t have MacOS hardware but its open-source so if someone want to join and extend functions to MacOS they are more than welcome to do so!
Are you using Windows 10? Can you check the logs? Any errors will be displayed there. You can check it using the shortcut placed under your start menu.
Also there is a page dedicated to try to troubleshoot the problems:
Yes, Windows 10.
I checked the troubleshooting, reinstalled everything with admin privileges, the service is running and the commands work.
The HA config it’s copied from the docs, and I double checked everything.
I can also confirm the same issue here with Windows Monitor and have performed all the suggestions. This is a clean first time install on Windows 10. I went ahead and disabled System Commands to keep output clean and here’s my log when I start the service:
[IA-VMS02][2019-06-12 15:18:09 -04:00][INFO][IOTLink.IOTLinkService]: Windows Service is started.
[IA-VMS02][2019-06-12 15:18:09 -04:00][INFO][IOTLink.Engine.MQTT.MQTTClient]: Trying to connect to broker: tcp://192.168.100.63:1883 (Try: 1)
[IA-VMS02][2019-06-12 15:18:10 -04:00][INFO][IOTLink.Engine.MQTT.MQTTClient]: MQTT Connected
[IA-VMS02][2019-06-12 15:18:10 -04:00][DEBUG][IOTLink.Engine.AddonManager]: Loading 2 external addons
[IA-VMS02][2019-06-12 15:18:10 -04:00][DEBUG][IOTLink.Engine.AddonManager]: Addon configuration loaded: System Commands
[IA-VMS02][2019-06-12 15:18:10 -04:00][DEBUG][IOTLink.Engine.AddonManager]: Addon configuration loaded: Windows Monitor
[IA-VMS02][2019-06-12 15:18:10 -04:00][DEBUG][IOTLink.Loaders.AssemblyLoader]: Found AddonScript!
[IA-VMS02][2019-06-12 15:18:11 -04:00][INFO][IOTLink.Engine.AddonManager]: System monitor is disabled.
[IA-VMS02][2019-06-12 15:18:11 -04:00][INFO][IOTLink.Engine.AddonManager]: Loading addon: windowsmonitor
[IA-VMS02][2019-06-12 15:18:11 -04:00][DEBUG][IOTLink.Engine.MQTT.MQTTClient]: Subscribing to iotlink/ia-vms02/#
[IA-VMS02][2019-06-12 15:18:11 -04:00][INFO][MQTTnet.Client.MqttClient]: Connection successful
[IA-VMS02][2019-06-12 15:18:11 -04:00][DEBUG][IOTLink.Engine.MQTT.MQTTClient]: MQTT Message Received - Topic: iotlink/ia-vms02/lwt
All I am getting in MQTT is: iotlink/ia-vms02/lwt: ON
As other wrote… Successfully connected to Mosquitto MQTT Server running on Hass.io. Both addons are enabled, but log states Monitor is disabled. I can mute/un-mute, so commands works. Monitor doesn’t send anything.
[WORKGROUP\XXX-PC][2019-06-12 22:40:39 +02:00][INFO][IOTLink.Engine.MQTT.MQTTClient]: Trying to connect to broker: tcp://192.168.XX.XX:1883 (Try: 1)
[WORKGROUP\XXX-PC][2019-06-12 22:40:40 +02:00][INFO][IOTLink.Engine.MQTT.MQTTClient]: MQTT Connected
[WORKGROUP\XXX-PC][2019-06-12 22:40:44 +02:00][INFO][IOTLink.Engine.AddonManager]: System monitor is disabled.
[WORKGROUP\XXX-PC][2019-06-12 22:40:44 +02:00][INFO][IOTLink.Engine.AddonManager]: Loading addon: windowsmonitor
[WORKGROUP\XXX-PC][2019-06-12 22:40:44 +02:00][INFO][MQTTnet.Client.MqttClient]: Connection successful
While looking at the addon source code I notice the reference to config.yaml which does not exist for Windows Monitor. I was about to log on GitLab project but found it already referenced --> https://gitlab.com/iotlink/iotlink/issues/19. After creating the config.yaml it works! Awesome project!
I was also seeing the Socket error when trying to run the Windows Monitor. Since I added the config.yaml the error went away. Have you added the config.yaml? See the previous post.
