Logs are FLOODED with information -Fixed!

[S-F]

I updated yesterday and now my logs are flooded with information every time a sensor is opened or closed. It's spamming my log. The updater says I'm on .17 but I see here that you posted .18. Am I on .18 and the updater is showing the wrong version, similar to the issue I'm seeing with the Kinect plugin. It doesn't show that .18 is available and I don't recall which I was on before the update.

I tried changing the log level to warning to no avail.

[spud]

hmm, changing the log level to warning should work as the new log lines are logged at the INFO level. Could you try it again?

the version in the updater 3.0.0.17

the latest beta version (posted in this forum) is 3.0.0.18, it has some settings at the device level to prevent logs for device status change.

[S-F]

Changing the log level to warning doesn't work. It doesn't persist after I leave the config page. I've had this issue all along. I forgot.

[spud]

Changing the log level to warning doesn't work. It doesn't persist after I leave the config page. I've had this issue all along. I forgot.

it works for me with HS version 3.0.0.142. What HS version do you run?

as a workaround you can change it manually in the EnvisaLink.ini file

[GENERAL]
log_level=Warning

then restart the plugin

[S-F]

it works for me with HS version 3.0.0.142. What HS version do you run?

as a workaround you can change it manually in the EnvisaLink.ini file

[GENERAL]
log_level=Warning

then restart the plugin

Right. Will do. But. Could you try to get to the bottom of why changing it doesn't from the config page doesn't work?

[spud]

Right. Will do. But. Could you try to get to the bottom of why changing it doesn't from the config page doesn't work?

yes, that's why I asked you what version of HS you are running, because I know there had been some version in which the function to write to ini files was buggy.

also, could you try
to change another setting and see if it is written to ini
to test the same thing with another of my plugin.

[S-F]

Woops. Sorry. I'm running around like a chicken with its head cut off this morning. I'm on .149. I'll get back to you on the .ini settings in a bit.

[S-F]

I can change things with the Kinect plugin and they stick. I'm not sure what I can change on the Envisalink config page without screwing things up though.

[spud]

I can change things with the Kinect plugin and they stick. I'm not sure what I can change on the Envisalink config page without screwing things up though.

very weird that the same thing works with the kinect plugin, it is basically the same code.

you can backup your current EnvisaLink.ini to come back to a working config if something goes wrong.

any error in the log, when changing the log level?
do you run HS as Administrator?

[S-F]

I successfully changed the number of zones. So it seems like it's only the log level.

There is no error when trying to change the log level.

I am not running HS3 as admin. I tried that recently and I don't think it works on the newer versions.

[spud]

FYI, I fixed the log level not being saved correctly in version 3.0.0.22 available here

[S-F]

Ahhhhh. Thank you Sir!