I need to write a proper dev documentation but I’m focusing on 1.2 which will bring some useful features (hint: https://i.imgur.com/r7uyD1c.png).
Creating a TTS Service addon is great, I think there is no problem with.
However the MQTT Monitor currently I believe that will be a issue because all addons are limited to their user-space for subscribing and publishing messages so all topics will start with {prefix}/{domain}/{machineName}/{addonId}. I made that way so addons can’t mess with others and create difficult to maintain and support 3rd party addons.
@theDiver
Yes, the interval is in seconds. If you have cache enabled, they won’t send again unless the value changes.
Strange, I have set all ‘cacheable’ to false to force it to update, and it only sends information when i boot the server, og restart the service not every 10 seconds
I also tried to uninstall, remove the iotlink folder, and reinstall it.
Setting it up again without just copying the old config files.
It transmits data once, when starting, and then only some of it if i touch the config files.
I am working on the server, so the chances that CPU load does not change is quite small.
Anyway i could debug it? The logfiles, don’t really show anything, i have set the log level to ‘5’
It’s time for IOTLink v1.2.0 release as it brings a lot of new useful features for all of us.
The first and most anticipated feature is using IOTLink to display Windows 10+ notifications using MQTT from HA or directly with possibility of customizing the icon, title and text and also, when the user click on it, it is possible to open an URL or Application.
Other feature reworked on is the current user and idle time monitoring. Now it only shows the value for the current physically logged in user so you can work with your automations easier than before. Last but not least, I’ve added new network LAN monitoring (IPv4, IPv6, Port Speed), a command to force refresh all your sensors information and option to change which size (MB, GB and TB) is used for HDD monitoring.
You guys have any kind of different permissions on yours hard-drives? Can you guys descrive what kind of drives you have? eg:
C = SDD
D = HDD
E = BD-ROM, Floppy (it still exists?), Network Drive, etc
I’m trying to find which drive and why (permissions maybe?) it happens, because I have 1 SSD + 2 SSD in RAID0 + 1TB HDD and never got this error.
Also are you guys willing to help me get to this error by joining discord (https://discord.me/iotlink) so I can try to get to the error with you guys? I’ll be off today but tomorrow I’ll be around most of the time.
I had same issue with it not detecting hard drive and user info. My machine is on a domain unsure if anyone else with the issue is. Anyway I changed the account that the service uses to logon from local system to a domain account and all ok now.
I read that this System.IO.IOException: The parameter is incorrect. error occurs when the HDD is not ready or have corrupt meta-information. I’ve added a check for IsRead state and added a catch for the other error but it will still be seen in logs. Let’s see how this thing behave now. Unfortunately I’m unable to replicate the error here so bear with me.
@theDiver
I can help you compile later in Discord, just drop me a pm.
[WORKGROUP\WINDOWS_10_VM][2019-06-28 04:50:43 +03:00][INFO][MQTTnet.Client.MqttClient]: Connection established successfully.
[WORKGROUP\WINDOWS_10_VM][2019-06-28 04:50:46 +03:00][WARNING][System.Dynamic.UpdateDelegates]: WebSocketServer - Agent from system not found.
[WORKGROUP\WINDOWS_10_VM][2019-06-28 04:50:56 +03:00][WARNING][System.Dynamic.UpdateDelegates]: WebSocketServer - Agent from system not found.
[WORKGROUP\WINDOWS_10_VM][2019-06-28 04:51:06 +03:00][WARNING][IOTLinkService.Service.Engine.ServiceAddonManager]: WebSocketServer - Agent from system not found.
[WORKGROUP\WINDOWS_10_VM][2019-06-28 04:51:16 +03:00][WARNING][IOTLinkService.Service.Engine.ServiceAddonManager]: WebSocketServer - Agent from system not found.
[WORKGROUP\WINDOWS_10_VM][2019-06-28 04:51:26 +03:00][WARNING][IOTLinkService.Service.Engine.ServiceAddonManager]: WebSocketServer - Agent from system not found.
[WORKGROUP\WINDOWS_10_VM][2019-06-28 04:51:36 +03:00][WARNING][IOTLinkService.Service.Engine.ServiceAddonManager]: WebSocketServer - Agent from system not found.
[WORKGROUP\WINDOWS_10_VM][2019-06-28 04:51:46 +03:00][WARNING][IOTLinkService.Service.Engine.ServiceAddonManager]: WebSocketServer - Agent from system not found.
I just finished installing the new version and I get the posts below.
Please note that despite the message, everything works.
If you can add the system time - how long the computer is working
It seems like the beta is not throwing that exception anymore.
One detail i noticed the ‘windowsmonitor’ config.yaml file is overwritten when i install a new version.
I think you should ask nicely, just as you do with the ‘configuration.yaml’ file
I’ve released the same beta above as the final v1.2.1 as it seems to have fixed the issue. Therefore, if you have installed the beta v1.2.1 you don’t need to reinstall it.
Thanks a lot.
