| [20:39:03] | * L1l has joined #farmos |
| [20:41:30] | * Lil has quit (Ping timeout: 276 seconds) |
| [21:23:07] | * mstenta has quit (Ping timeout: 276 seconds) |
| [21:27:37] | * Lil has joined #farmos |
| [21:28:33] | * L1l has quit (Ping timeout: 240 seconds) |
| [04:22:56] | * ykir has joined #farmos |
| [04:23:16] | <ykir> | hello |
| [04:23:16] | <farmBOT> | what's up |
| [04:23:16] | <farmBOT> | ykir: 2 days 19 hours ago <mstenta> tell ykir Thanks! I would appreciate any advice and knowledge you can contribute! That's the beauty of this open software development model: work together for everyone's benefit! :-) |
| [04:23:16] | <farmBOT> | ykir: 2 days 19 hours ago <mstenta> tell ykir Regarding sensors: farmOS comes with a module called Farm Sensor - and within that is a sub-module called Farm Sensor: Listener. The Listener module adds a "sensor type" called "Listener", which is essentially just an HTTP endpoint that your sensor devices can push data to. |
| [04:23:16] | <farmBOT> | ykir: 2 days 19 hours ago <mstenta> tell ykir That is one generalized option. The other option is to write a more sensor-specific sub-module of your own, that connects directly to your sensor (or vice versa). You can make it work however you want. |
| [04:23:16] | <farmBOT> | ykir: 2 days 19 hours ago <mstenta> tell ykir They both require some development work to set up. For the listener, you need to set up some software on your sensor to connect to the internet and push data to the endpoint. And of course for the custom sensor-type sub-module approach, you need to write the module. |
| [04:23:16] | <farmBOT> | ykir: 2 days 19 hours ago <mstenta> tell ykir As an example, I have written a very simple module that provides a new sensor type called "Farm Sensor: Atmospi": http://github.com/mstenta/farm_sensor_atmospi |
| [04:23:16] | <farmBOT> | ykir: 2 days 19 hours ago <mstenta> tell ykir That module is designed specifically for connecting to the custom Atmospi software that I wrote for temperature/humidity sensing on a Raspberry Pi: http://github.com/mstenta/atmospi |
| [04:23:16] | <farmBOT> | ykir: 2 days 19 hours ago <mstenta> tell ykir But the general principals and frameworks are in place in farmOS to start building all kinds of sensor connections! |
| [04:23:16] | <farmBOT> | ykir: 2 days 19 hours ago <mstenta> tell ykir I am even considering making the upcoming Weather module into a type of sensor itself... makes sense don't you think? It would download weather data from public sources over the internet - which is a form of "sensing" in a way. :-) |
| [04:45:00] | * ykir has quit (Ping timeout: 250 seconds) |
| [05:02:56] | * L1l has joined #farmos |
| [05:04:44] | * Lil has quit (Ping timeout: 260 seconds) |
| [05:10:43] | * ykir has joined #farmos |
| [05:10:57] | <ykir> | hello |
| [05:10:57] | <farmBOT> | salut |
| [05:11:02] | <ykir> | farmBOT: tell mstenta The weather module is interesting for macro-data precisely by connecting to public sources |
| [05:11:02] | <farmBOT> | ykir: I'll pass that on when mstenta is around. |
| [05:11:10] | <ykir> | farmBOT: tell mstenta It would be very useful to have a procedure in which it can associate the received data of some sensors to specific areas, such as I speak for my work it would be nice to have a page where you can create "groups" of associated sensors, |
| [05:11:10] | <farmBOT> | ykir: I'll pass that on when mstenta is around. |
| [05:11:17] | <ykir> | farmBOT: tell mstenta such as the greenhouse sensors group will be very different than in open fields as well as for the different types of crops (personally I speak for my company rice, but I guess those nurseries, farms, etc) and just choose which sensors to associate. |
| [05:11:17] | <farmBOT> | ykir: I'll pass that on when mstenta is around. |
| [05:11:24] | <ykir> | farmBOT: tell mstenta I understand how complicated the fact that open source sensors are simple to position and calibrate and commercial products do not result in the same data formats, but it would be very beautiful and useful as an idea how about you? |
| [05:11:24] | <farmBOT> | ykir: I'll pass that on when mstenta is around. |
| [05:11:33] | <ykir> | farmBOT: tell mstenta Once done, another thing that I would really like would be to recreate graphics crossing all possible data, such as estimating evapotranspiration ET0 by Hargreaves, have some already made by the most usual values and the ability to export pdf is that values already intabellati. |
| [05:11:33] | <farmBOT> | ykir: I'll pass that on when mstenta is around. |
| [05:12:00] | <ykir> | farmBOT: tell mstenta Besides having the opportunity to cross the sensor data with the inserted log, for example, to see in all the times that you sow a certain crop with T ° under to 10 °, in how many days has completed the cycle. |
| [05:12:00] | <farmBOT> | ykir: I'll pass that on when mstenta is around. |
| [05:12:07] | <ykir> | farmBOT: tell mstentaI know I talk a lot and I digress, but conscendo specifically the difficulty in recreating the thing and the fact that it is under construction, I try to export everything that comes to mind and I'd like :) |
| [05:12:07] | <farmBOT> | ykir: I'll pass that on when mstentaI is around. |
| [05:12:16] | <ykir> | farmBOT: tell mstenta You talked about the Farm Sensor Module - Listener that is able to receive data at this time, I'd know I mean if I can do this by placing the historical weather data that I have? |
| [05:12:16] | <farmBOT> | ykir: I'll pass that on when mstenta is around. |
| [05:12:22] | <ykir> | farmBOT: tell mstenta On Farmos also including crops of past data, to increase the historicity and having available also weather data, I would like to associate; They are in tabular format with openoffice calc |
| [05:12:22] | <farmBOT> | ykir: I'll pass that on when mstenta is around. |
| [05:13:13] | <ykir> | farmBOT: tell mstenta Always forgive me for my bad english:) |
| [05:13:13] | <farmBOT> | ykir: I'll pass that on when mstenta is around. |
| [05:13:39] | * ykir has quit (Client Quit) |
| [09:08:30] | * mstenta has joined #farmos |
| [09:17:13] | * Lil has joined #farmos |
| [09:17:25] | * L1l has quit (Ping timeout: 260 seconds) |
| [09:19:37] | <mstenta> | . |
| [09:23:16] | <mstenta> | farmBOT: tell ykir Yes! I'm thinking many of the same things! Let's start formalizing some feature requests so that we can figure out the necessary details! |
| [09:23:16] | <farmBOT> | mstenta: I'll pass that on when ykir is around. |
| [09:58:07] | * L1l has joined #farmos |
| [09:59:01] | * Lil has quit (Ping timeout: 240 seconds) |
| [10:39:21] | * L1l has quit (Ping timeout: 276 seconds) |
| [10:42:05] | * Lil has joined #farmos |
| [10:45:46] | * L1l has joined #farmos |
| [10:46:40] | * Lil has quit (Ping timeout: 260 seconds) |
| [11:37:50] | * Lil has joined #farmos |
| [11:38:30] | * L1l has quit (Ping timeout: 276 seconds) |