I decided to get more hardware support for different Sensors going.\u00a0 In the process, I’m cleaning up and enhancing the sensor and database code.\u00a0 This will allow recording of ONLY what sensors are present, so there’s no big list of “N\/A” for things not there, just null columns.\u00a0\u00a0<\/p>\n\n\n\n
I think I have added \/ modified all the compatible sensors that I have, which include the Raspberry Pi Sense hat, and the following, that are all Pimoroni brand Sensors;\u00a0 bh1745 (Light), BME680 (Temp, Pressure, Humidity and gas resistance), Enviro hat (temp, pressure, light, magnetometer,\u00a0accelerometer), LSM303D (magnetometer,\u00a0accelerometer),\u00a0VL53L1X (Distance sensor \/w lasers).\u00a0<\/p>\n\n\n\n
Now to modify the SQL writer to work with them.\u00a0 Although, I’m going to take a little time to rethink how it determines which sensors are available, as I would like to cut down on the amount of code needed to identify said available sensors… Not to mention make it simpler to understand and modify.\u00a0<\/p>\n\n\n\n
30 min later ….\u00a0<\/p>\n\n\n\n
I think I got it!\u00a0 create a new line per sensor in the “Sensors installed” file, have a number as the first char, such as 0 = not installed, 1 = installed.\u00a0 Then after that, put the name of the sensor, as it would only look at the line’s first char to check.<\/p>\n\n\n\n
Example.
This way, it’s easy to modify if you open the config up, as the names right there with simple instructions.\u00a0 hmm… yeah I think that will do nicely. Time to work that into the installer script.<\/p>\n","protected":false},"excerpt":{"rendered":"
I decided to get more hardware support for different Sensors going.\u00a0 In the process, I’m cleaning up and enhancing the sensor and database code.\u00a0 This will allow recording of ONLY what sensors are present, so there’s no big list of …<\/p>\n