IRC logs for #farmOS, 2020-08-09 (GMT)

2020-08-08
2020-08-10
TimeNickMessage
[23:08:54]* JustTB has quit (Ping timeout: 256 seconds)
[23:23:12]* JustTB has joined #farmos
[03:33:43]* JustTB has quit (Quit: Leaving.)
[04:41:16]* JustTB has joined #farmos
[05:28:59]* JustTB has quit (Ping timeout: 240 seconds)
[05:43:29]* JustTB has joined #farmos
[05:48:18]* JustTB has quit (Client Quit)
[09:38:48]<jgaehring[m]>Hey paul121, I was telling donblair about your plan to make a field module for reading sensor data... It'd be cool to talk here about what that looks like and how it could maybe work with your sensor deployments at WNC and in CO
[10:33:08]* donblair[m] has joined #farmos
[10:49:55]<donblair[m]>Hey there! Would love to chat about this
[11:29:40]* JustTB has joined #farmos
[13:03:12]* JustTB has quit (Quit: Leaving.)
[13:19:52]<paul121[m]>Oh yea! Would be great to learn what you've been doing donblair !
[13:22:36]<paul121[m]>I've been working with a farm to integrate some of their sensors from third parties into farmOS
[13:23:28]<paul121[m]>One of the sensors in particular we've integrated in farmOS as a listener sensor asset
[13:24:17]<paul121[m]>We get CSV files of data and have a script that imports it to farmOS daily
[13:25:23]<paul121[m]>The sensors are particularly related to irrigation & used by the irrigation team. Soil moisture & soil temp at 12" and 6" are recorded
[13:26:04]<paul121[m]>Viewing data in the farmOS desktop is a first step... But the irrigation team really needs to see it out in the field
[13:26:15]<paul121[m]>So... Sensor Field Module!
[13:28:11]<paul121[m]>Talking with Jamie it seems like a MVP should be fairly easy... Simply select a Sensor asset in the mobile app and load data from farmOS using the public/private key
[13:29:37]<paul121[m]>For this particular use case there are 100+ sensors though, sometimes 2-3 in the same field. So a drop-down or even a textfield to load a sensor asset might not work well
[13:30:35]<paul121[m]>Having a feature to display sensors in certain area(s) would be good
[13:31:32]<paul121[m]>Caching sensor data would be nice too...
[13:31:46]<paul121[m]>So you could load before going out in the field
[13:33:03]<paul121[m]>After all that, it would interesting to explore different ways to view different types of data. Eg: Temperature as a line graph, precipitation as a bar chart, etc...
[13:35:53]<paul121[m]>Ideally we could create a single sensor Field Module to rule them all :P but that might be hard with more specific use cases
[13:37:16]<paul121[m]>jgaehring and I chatted about how FMs could maybe be "configurable" on the server side. So for all Field Kits that connect to that farmOS server, the sensor module could behave in a particular way
[13:39:51]<paul121[m]>But thinking more about it now, I think we could expand the `sensor_settings` variable to include more info about the sensor too. Things like what type of visualization to use (bar chart vs line chart), default caching behavior, additional notification options... Etc
[13:40:36]<paul121[m]>That's something I've been meaning to ask: notifications in Field kit? There's probably an issue for that already!
[13:54:06]<and712[m]>Sounds really interesting! Now i just needs some sensors on the field 😉
[14:10:27]<donblair[m]>Wow, thanks for all this, paul121 -- really useful to hear all of this laid out so nicely
[14:12:34]<jgaehring[m]><paul121[m] "That's something I've been meani"> Our oldest open issue actually https://github.com/farmOS/farmOS-client/issues/10
[14:12:59]<donblair[m]>(I don't think it's necessary for this discussion, really, but as an aside: would love to know more about the particular sensors you're integrating -- soil moisture, soil temp -- how is data getting to the cloud? is it a lorawan system?)
[14:13:01]<jgaehring[m]>I'm.... ambivalent about notifications, but it's definitely possible
[14:14:24]<donblair[m]><paul121[m] "After all that, it would interes"> When it comes to these ideas ...
[14:14:46]<donblair[m]><paul121[m] "Ideally we could create a single"> ... and this insight,
[14:16:35]<donblair[m]>... it makes me wonder whether it's possible to prototype the various views / aggregations / interfaces / displays as a very simple NodeJS web app at first; and somehow do it in a way (modular? using libraries in a certain way?) that makes it easy to incorporate in FMs / FarmOS afterwards ...
[14:17:30]<donblair[m]>I say "NodeJS" app just because that's what I've been tinkering with ...
[14:22:19]<donblair[m]>I've simply been using https://www.chartjs.org/ (based on D3) to produce extremely simple temperature / humidity graphs, based on data from a few sensors on various farms
[14:37:16]<jgaehring[m]><donblair[m] "I say "NodeJS" app just because "> Are you still serving web sites over LAN from sensor gateways? I do still wonder if we could deliver FM's from sources other than a farmOS server
[15:20:14]<paul121[m]>> ... it makes me wonder whether it's possible to prototype the various views / aggregations / interfaces / displays as a very simple NodeJS web app at first; and somehow do it in a way (modular? using libraries in a certain way?) that makes it easy to incorporate in FMs / FarmOS afterwards ...
[15:20:14]<paul121[m]>Oh interesting! Similar to how we pull in Field Modules as a Vue component, could the farmOS sensor type module provide another (simpler) Vue component for graphing?
[15:20:47]<paul121[m]>(might be incorrect to say Field Modules are Vue components ... I forget the status of that)
[15:21:24]<and712[m]><donblair[m] "... it makes me wonder whether i"> That would be really great!
[15:22:10]<paul121[m]>Ah yes chart.js! I've worked with that some too. Personally I really like it
[15:23:04]<paul121[m]>We'll have to talk more about this throughout the week maybe.. about to embark on a 6hr drive! Talk later!
[15:39:36]* JustTB has joined #farmos