I haven't seen any official comment on the status of the BLRadar.xml corruption that many of us seem to be facing at one point or another. Has the cause of this issue come to light yet? In getting ready to perform some maintenance work on my HomeSeer system today, and I've discovered that the file is currently 0 bytes again. I'm so tired of this that I will likely move off this plugin permanently if it cannot be fixed. This is probably the 8th or 9th time in the last two years that I have lost the contents of the .xml file. Yes, I know I can restore from backup. I'm just getting tired of having to do it.
March 27, 2020 14:56 - last reboot
March 29, 2020 14:01 - file overwritten, now 0 bytes
Unfortunately, this is all I know. My HomeSeer logs only go back 30 days. I'm on the current release of the plugin, 2.0.140.0. I am running HS3 3.0.0.548 on Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-91-generic x86_64). The config must remain loaded in memory, because it will work until I reboot it. Once I reboot, all my sensors will be gone again. Is there a way to re-write that file with the contents in RAM, should it become corrupted? Can you add a backup/restore for the .xml from within the plugin's config area? Is there anything you can share as to why this happens?
Should there be an entry for every sensor in my .ini file? It looks like my .ini has remained unchanged for a long time, but I've definitely added more sensors since then. Could there be some mis-match between the .ini and .xml that could be causing this to happen so frequently?
March 27, 2020 14:56 - last reboot
March 29, 2020 14:01 - file overwritten, now 0 bytes
Unfortunately, this is all I know. My HomeSeer logs only go back 30 days. I'm on the current release of the plugin, 2.0.140.0. I am running HS3 3.0.0.548 on Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-91-generic x86_64). The config must remain loaded in memory, because it will work until I reboot it. Once I reboot, all my sensors will be gone again. Is there a way to re-write that file with the contents in RAM, should it become corrupted? Can you add a backup/restore for the .xml from within the plugin's config area? Is there anything you can share as to why this happens?
Should there be an entry for every sensor in my .ini file? It looks like my .ini has remained unchanged for a long time, but I've definitely added more sensors since then. Could there be some mis-match between the .ini and .xml that could be causing this to happen so frequently?
Comment