| [20:28:36] | * younes__auto[m] has quit (Ping timeout: 246 seconds) |
| [20:28:38] | * samrose[m] has quit (Ping timeout: 246 seconds) |
| [20:28:38] | * symbioquine[m] has quit (Ping timeout: 246 seconds) |
| [20:28:57] | * zedrckr[m] has quit (Ping timeout: 246 seconds) |
| [20:28:57] | * mindcls has quit (Ping timeout: 246 seconds) |
| [20:30:13] | * younes__auto[m] has joined #farmos |
| [20:31:16] | * symbioquine[m] has joined #farmos |
| [20:31:22] | * samrose[m] has joined #farmos |
| [20:32:06] | * zedrckr[m] has joined #farmos |
| [20:36:46] | * mindcls has joined #farmos |
| [05:15:14] | * JustTB has quit (Quit: Leaving.) |
| [06:15:57] | * JustTB has joined #farmos |
| [13:28:23] | <paul121[m]> | canadrian: cool!! |
| [13:29:13] | <paul121[m]> | the sensor listener data gets saved in a separate DB table, so its not actually saved as farmOS logs |
| [13:29:39] | * canadrian[m] has joined #farmos |
| [13:29:39] | <canadrian[m]> | Howdy! I'm just testing a sensor listener with IFTTT, and I was wondering: how can I delete the test sensor data once I'm happy with how it works? There don't seem to be log entries or something to delete. |
| [13:29:43] | <paul121[m]> | if you are self-hosting you could go into the db and manually delete those entries |
| [13:30:15] | <paul121[m]> | but what I've done for my testing is just delete that sensor asset, and create a new one |
| [13:30:35] | <paul121[m]> | (I usually name that first sensor `testing sensor`) |
| [13:31:42] | <paul121[m]> | I'm not sure if the sensor's data is deleted when you delete a farmOS sensor `asset` - mstenta might know? |
| [13:31:50] | <canadrian[m]> | And yeah... I should be testing on a testing site, but.... 🙂 |
| [13:32:53] | <paul121[m]> | haha well this is a low-risk test :D |
| [13:33:42] | <paul121[m]> | I'm curious - does IFTTT have a tool for sending HTTP POSTs ? And you can configure the body, params, etc? |
| [13:35:52] | <canadrian[m]> | Yeah they have a "Webhook" thing (formerly called "Maker") that can be a trigger or an action. Basically I don't have any weather sensors (I'm just using FarmOS for my home garden) but I want to log daily weather information. So I'm going to build a recipe with Weather Underground as a trigger, sending the daily weather info as a Webhook action to my sensor listener. |
| [13:36:31] | <canadrian[m]> | Daily high, low, precipitation, etc. |
| [13:38:57] | <skipper_is[m]> | Ah that's cool! I've got a python script doing cumulative counts on my server with data from my weather station and posting that to FarmOS |
| [13:42:23] | <paul121[m]> | very cool! connecting that with Weather Underground makes it easy! |
| [13:42:52] | <paul121[m]> | skipper_is: you're posting that to a farmOS sensor? |
| [13:44:24] | <paul121[m]> | the next step would be auto-creating Observation Logs... probably not for hourly data, but weekly rainfall totals? that would be kinda interesting |
| [13:45:00] | <paul121[m]> | I guess you could have the farmOS server parse the sensor data to create those on a regular interval. hmm... 🤔 |
| [13:47:00] | <canadrian[m]> | I used to do a lot of Drupal site building, but it's been a while. But I seem to recall there was a Views module that could present data as a spreadsheet with calculations, so you could make a View that includes numerical data (like sensor readings) and have it summed for a column. There's actually a lot of stuff I could see doing with Views and FarmOS, but I'm a bit worried how sensitive it is to such stuff without |
| [13:47:01] | <canadrian[m]> | breaking. |
| [13:49:33] | <paul121[m]> | oh thats interesting |
| [13:50:12] | <paul121[m]> | this views module would auto-populate a spreadsheet in JS? |
| [13:50:32] | <paul121[m]> | the graphing of sensor data is very basic right now - it just loads the last 100 values |
| [13:50:37] | <canadrian[m]> | Yeah if I'm remembering correctly |
| [13:51:14] | <paul121[m]> | we need a views "module" "plugin" or "display type" (I forget the right term?) that graphs such data |
| [13:51:26] | <paul121[m]> | and could have some configurable options |
| [13:55:24] | <canadrian[m]> | Well the Sensor asset already graphs readings. Do you mean you want to be able to sum up totals, and then graph the totals? |
| [13:56:44] | <paul121[m]> | it does graph readings, but it only shows the past 100 values |
| [13:57:35] | <paul121[m]> | it seems like a View would make it easy to add filters (date range, only certain values, etc) "out of the box" |
| [14:04:18] | <canadrian[m]> | The module I'm thinking of is called Views Calc |
| [14:13:59] | <canadrian[m]> | The Computed Field module might also be useful |
| [14:15:39] | <canadrian[m]> | Views Aggregator looks good too |
| [14:15:59] | <canadrian[m]> | But now that I think of it, all this is moot if those sensor readings aren't stored as nodes |
| [14:15:59] | <paul121[m]> | ahhh computed field is interesting |
| [14:17:25] | <paul121[m]> | this is what I looked at for graphing: https://www.drupal.org/project/charts |
| [14:18:37] | <paul121[m]> | but the D7 module isn't too great. D8 supports more graphing libs & has more configuration options |
| [14:20:04] | <paul121[m]> | oh you think so? The table that is rendered with Sensor data right now is configured with Views (only the graphs are separate) |
| [14:20:22] | <paul121[m]> | so however the sensor data is stored, seems to be semi-compatible with views! |
| [14:22:38] | <canadrian[m]> | Oh, ok. Like I said, it's been a long time since I did much Drupal work. I mostly used Drupal 6 as well. |
| [14:24:41] | <paul121[m]> | Haha I'm on the opposite end - I've only been learning Drupal over the past year |
| [14:25:04] | <paul121[m]> | maybe you get back into it with farmOS! |
| [14:25:31] | <paul121[m]> | * maybe you can get back into it with farmOS! |
| [15:11:13] | <canadrian[m]> | I was banging my head against this IFTTT webhook, but I think I just realized something... does the sensor listener only accept numerical data? Like does it choke on a value like "Cloudy"? |
| [15:35:56] | * calbasi has quit (Quit: Leaving) |
| [15:41:29] | <paul121[m]> | mmmm it might |
| [15:43:59] | <paul121[m]> | ACTION sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/DTpvgANVXmavvejU... > |
| [15:44:30] | <paul121[m]> | so your request probably isn't failing - the data just isn't showing up. that could be confusing! |
| [18:39:50] | <canadrian[m]> | Sadly I can only get high temp, low temp, humidity and UV index from that IFTTT recipe. It's a start. So now I'm trying to figure out how - as a basically non-programmer - I subscribe to the 24h rainfall totals from Edmonton's Open Data portal: https://dev.socrata.com/foundry/data.edmonton.ca/x4rm-mppc |
| [18:42:21] | * stefanie[m] has joined #farmos |
| [18:42:29] | <canadrian[m]> | I suspect Open Pipe Kit may be the answer, but it's going to take some learning. |