Kootnet Sensors Beta.34.145

Kootnet Sensors version Beta.34.145 is out! I have updated all the channels and links to reflect the new version. I have also created Raspberry Pi images so you can flash it directly to an SD card and boot up with it pre-installed (like you would flash a normal Raspbian OS image). I’m just in the process of uploading the images to my web server, after that I’ll create links on my main pages to them. This should resolve any installation issues that might arise due to unresponsive servers or stale apt-get cache.

In other Kootnet Sensors news, I have created deb installers for older versions of Kootnet Sensors and posted them in the “Releases” section on GitHub. This was done mostly for nostalgia since you wouldn’t want to start with an older version … especially the much older ones. Still, it’s neat to see how the program has progressed over the months/years. The older versions I have created installers for include Alpha.24.x up to Alpha.28.x. I also added a missing one for Beta.31.x.

That’s it for now. I’ll post again when I get the Raspberry Pi images online.

Still working on Beta.34.x

So a bit more delay, I had family over and didn’t get as much work as I wanted to be done on the project. That being said, it’s coming along nicely. I’m just tweaking a little bit more and going through different sections double checking code.

Thanks to checking code all over, I re-worked the web portal notification system and added notifications for things like updates being run. I also enhanced the TCT (Terminal Configuration Tool) by adding the running version to the top of the menu, changing the operations a bit to have nicer output (easier to read and or more informational output during operations) and adding small changes like auto restarting the service after changes are done that require it (except for a few where you might want to check things before re-initializing).

So long story short, I want this release to be checked through a bit more before release. So it will be a bit longer. I’m still hoping to have it out by the end of this week, but I seem to keep finding sections I want to refine … so … we’ll see ^_^

Kootnet Sensors delayed-release

I found a few bugs while going through Kootnet Sensors code, so I’m taking a bit more time before a release. Things are coming along nicely, if all goes well, the new version should land in stable by the end of the week.

Kootnet Sensors – 3 new HW Sensors added!

I’m getting very close to releasing a new version of Kootnet Sensors. Besides tweaking more around the web portal, I have added new hardware sensor support! Here are the sensors.

  • Pimoroni RV3028 (Real Time Clock)
  • Pimoroni PA1010D (GPS)
  • Pimoroni MICS6814 (gas)

The RV3028 allows your Pi to keep current time when there’s no power, very handy for time-sensitive data recording.

The PA1010D GPS sensor required me to add the new sensor types into the different program sections. I’m still not done adding it to all aspects of Kootnet Sensors, but it works under “Live Sensor Readings”, Interval Recording and MQTT.

The MICS6814 sensor is a GAS sensor, but unfortunately, I don’t actually have one, so I can’t test it. On the subject of testing, I was able to move the Pimoroni SGP30 & MSA301 out of the “Un-Tested” section as I have ordered a few in to try out. I’m happy to say they are working well (now).

Yesterday I finished up a few updates to the documentation, and although not done, it at least reflects the new Web Portal changes.

There have also been updates and changes to the installers. I have updated the required Python modules (most of them) and added a few new ones that are required for the updated modules. I also fixed a bug that prevented the installer from using the local Python modules, so install time should be much faster than the previous release.

There are still a few things I kinda wanted to do… but I also want to get the new version out … So we’ll see. I’m hoping to have the new version out sometime next week. The developmental release is in good shape, so you can upgrade to it without issues if you don’t want to wait.

Until next time!

I’m Back! Updates made to Kootnet Sensors

I have been a bit absent lately but I have come back with improvements to Kootnet Sensors. I will be releasing Beta.34.x soon with the following improvements so far.

  • Adjusted Web Portal visuals to better match the light/dark themes
  • Adjusted Web Portal visuals for more consistency across pages
  • Added many Icons to menus, button and sections to improve overal look
  • Added Icon on top Web Portal bar to instantly return to the top of the page
  • Re-worked layout of Web Portal upgrades and power commands page
  • Web Portal fixes and improvements for smaller displayed devices (mobile)
  • Sensor Checkin enhancements
    • Added additional options for what to send
    • Improved Sensor Checkin view pages
      • Added setting for how many checkins to show on main page
  • MQTT Subscriber Web Portal Improvements
    • Added setting for how many Sensor Posts to show on main page
  • Re-wrote Sensor Reports
    • Improved responce times
    • Simplify the back end
    • Changed visuals
    • Combo report top menu now remains visable at the top of the page
      • Added link to change Theme and return to top of the page
    • Added additional System & Configuration settings
    • Reports now show sensors that are in the list but Offline
  • Added Automatic Upgrades (Disabled by default)
  • Updated some sensor python modules (drivers)
  • Misc. Minor bugfixes

A lot of the updates revolve around improving the Web Portal user experience. This is especially true for mobile devices. For one, you can now scroll the left main menu if your screen can’t show all the items.

The report generation has also gone through a major overhaul. The HTML code for each sensor entry is now generated on the remote sensor instead of the sensor generating the report. There are obvious speed enhancements with the new approach since the report generating sensor no longer has to get every configuration and multiple other sensor variables through HTTPS requests, and after that, still make the single sensors section and the actual report. It just takes one request to get the sensors section and add it into the main report (and a few other requests to test login/latency). The back-end has also been greatly simplified with this approach, as it’s a normal flask render_template() for each sensor report section.

The next neat addition is the new automatic software upgrade function. It’s pretty much exactly what you think it would be, you set an interval to check for updates, choose what version level you want to auto-update to, and save. You can set the auto-upgrade level to the following.

  • Stable Major Upgrades
    • Upgrades to new Major stable versions (Ex. Beta.32.xx –> Beta.33.xx)
  • Stable Minor Upgrades
    • Upgrades to new Minor stable versions (Ex. Beta.32.12 –> Beta.32.14)
  • Developmental Upgrades
    • Upgrades to any new Developmental versions (Ex. Beta.32.12 –> Beta.32.14 or Beta.32.xx –> Beta.33.xx or Beta.32.12 –> 1.0.1)

That covers most of the changes. I’ll try and remember to update this more often.

Until next time!

Kootnet Network Testers

Now that Kootnet Sensors has its new interface I have turned my attention to the Network Testers and added the ability to run SpeedTest.net to find your Internet speeds courtesy of SpeedTest-CLI. I don’t have options in place yet, so it auto picks a server with the best ping times and runs. It works on the E-Ink display and the web interface. Upgrade to the latest developmental version to try it out. I’ll tweak it more as time goes on.

I’m also considering upgrading the web interface of Kootnet Network Testers as I did with Kootnet Sensors… It’s just so time-consuming… took me 2 months to get Kootnet Sensors’ new interface ‘done’. Maybe I will make a poll on the Raspberry Pi forums.

That’s it for today’s update.

New Kootnet Sensors Version in Stable

I have now poked around and tested most of the program, and it’s been working smoothly.
So Kootnet Sensors Beta.33.69 is out! Please note that this upgrade will reset your MQTT Publisher configuration.

As mentioned in previous posts, this version is 90% about overhauling the Web Interface.
Other modifcations include MQTT Publisher improvements, updated security options under email SMTP settings and the ability to view a list of all sensors in the MQTT Subscriber database.

I’m going to wait a bit before I start on Beta.34.x to fix any lingering bugs and re-do the help documentation and program tests. I’m also going to shift over to my Network Testers and add a bit more functionality to it.

So please, upgrade, try it out and report any bugs to the GitHub page or you can also post it here or on my Raspberry Pi form post.

I hope everyone enjoys the new interface!

Interface progress update

I’m getting close to releasing a new version of Kootnet Sensors! 90% of the changes in this release are around the new Web Interface. As of today, it has been 2 months since I started creating the new Interface. Everything is done but I want to do some more testing before releasing it. So hopefully in the next few days, it will be put into the stable channel.

Soon! … soon…

New Interface progress

So I’m making decent progress on the new interface, but it’s definitely taking longer than a month, at least 2 I’m guessing.

I have now finished the Remote Management, Graphing and most of the notification system. Right now I’m working on re-doing the reports generation to match the new look. I have also removed most of the old Interface from the program.

I suppose I should update documentation before a release as well… which will take a bit of time too.

That’s it for todays update. Still working on it, it’s just taking a bit longer then I thought.

Kootnet Sensors Interface Progress

I now have all the pages working on the new interface except for Graphing and Remote Management.

The next step, after finishing Graphing, Remote Management and the notification system, will be to look over the interface as a whole and tweak things to be more consistent and adjust a few minor things, like the size of text and number fields.

I’m also thinking I’ll remove the old interface altogether, as it’s adding a decent amount of bulk to the overall program.

I have not had as much time as I would have liked to work on it, but progress is continuing! Very little back-end work has been done since the last stable release, so it’s safe to upgrade to dev and check out the interface progress.