I have been working on a few things as of late.\u00a0 For one, notes can be saved into the sensor Database at whatever time you choose.\u00a0 This is meant to aid in putting notes beside the actual sensor data.\u00a0 I’ll be adding the notes into the graphs later, so that they will show up with the graphed sensor data, using the time you enter!\u00a0 AKA, you notice the sensor malfunctioning at a certain time, you enter a note with the same or close Date & Time saying “Malfunction, ignore this” or “Very important data represents time travel”.\u00a0 Whatever helps identify what the data represents.\u00a0 It can also be used to bookmark or tag certain times with things, like manual settings for temperature offset or other important information not being captured by the sensors, etc.\u00a0 Later on, I’ll try to get it so you can “Graph by notes”, and it will graph say, 1 hour on either side of every note’s time frame, making it easy to instantly populate graphs with important data without having to search every time. I’ll be giving it more thought for sure.\u00a0<\/p>\n\n\n\n
Since I seem to like ordering my options in the config and sensor files, in a way that’s not great for compatibility (AKA I don’t add every new option to the bottom, I reorder the whole list).\u00a0 This is a pain, as I manually have to log in through SSH and re-adjust the sensor configuration files for the new options.\u00a0 So I had a few ideas on solving it.\u00a0
1) Add the ability to change installed sensors from the control center
and or
2) Create some updated functionality to automatically make needed changes after the upgrade.\u00a0
I went with the 2nd option first and made an upgrade module that adjusts any needed files and related settings, then re-saves them.\u00a0 It also uses the versioning system, so it can incrementally update from this version onwards, even if you miss a few versions along the way!\u00a0 This will make my future upgrade tests go a bit smoother!<\/p>\n\n\n\n
My other major upgrade was to the environmental temperature adjustments.\u00a0 Before it was a manually set option in the graph window, but this makes it annoying to swap between different sensors with different offset needs.\u00a0 So I moved the offset into the sensor itself and created different offsets for different setup combinations.\u00a0 This way it’s all automatically set by how you set your installed sensors configuration file!\u00a0 AKA it will give recommended offsets depending on what hardware is being used.\u00a0 So now you can check a “Use Default” temperature offset checkbox, and the graphs will use the offset\u00a0provided by the sensor.\u00a0 A custom offset is also available in the sensor configuration file, in case a sensor doesn’t follow standards.\u00a0 And of course you can uncheck the use default and set your own setting during graphs.\u00a0 Whatever is set on the sensor, will also be saved into the SQL database when the environmental temperature readings are saved.\u00a0\u00a0<\/p>\n\n\n\n
Those are the 3 main things I have been working on.\u00a0\u00a0<\/p>\n\n\n\n
I think I’ll re-work my re-configuration of the sensors.\u00a0 I think I can make a decent live update by pulling and pushing the text files into and out of a textbox, similar to my Log viewer and Notes window.\u00a0 If I do that, I think the program can do everything remotely!\u00a0 Between the log viewer, update module and soon to be installed sensors and config adjuster, keeping my demo and test sensors running smoothly through upgrades is starting to sound like an easier task \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
I have been working on a few things as of late.\u00a0 For one, notes can be saved into the sensor Database at whatever time you choose.\u00a0 This is meant to aid in putting notes beside the actual sensor data.\u00a0 I’ll …<\/p>\n