be careful with the meta data to save: this can interfere with other farmwares. I have to test if some builtin farmware does not delete the information.
this farmware does not remove meta data but always adds to existing ones if you use unique keys (this should be the rule)
report issues in gitHub
I look forward to the input variables in command ‘run farmware’ into sequences
Oh lord, this one looks great!
We can use this to plant seeds or water existing plants with such a low effort. Now that we can use the meta data, we could even group plants by adding the same meta data.
Code looks great and really clean. Keep up the work, can’t wait to see more ideas and farmwares
This would help to run these tasks automatically. I think someone recently made a feature request about that.
it appears that the ‘run farmware’ command in the sequences use the parameters created in the 'Farmwares tab page.
at this point I do not know where the parameters are stored, but if my analysis is good it is stored in the environment variables of farmbot_os and I do not know if it is persistent after reboot (if someone can validate ???)
I copied some farmware with a suffix 01, 02, 03 …
and so now it’s possible to run this farmware with different parameters and use them in the sequences.
this duplicates the farmware but it’s a workaround and it does the job …
after reflecting for the ‘run farmware’ command in the sequences, i think the simplest and best way to implement is to create a farmware configuration manager with multiple configurations for a single farmware and in the sequences: have 2 drop-down menus in the ‘run farmware’ command: 1 with the farmware reference, 1 with the config reference
And if everything is stored in the database it’s even better …
user_env are used to store input value for farmware
because user_env are not persistent after farmbot_os update or factory reset.
i writed theses 2 farmware for Backup And Restore user_env :
variables are stored in an active tool named BACKUP_USERENV by default.
!!! you must to create this tool and add it to a slot prior to backup/restore !!!
it’s a workaround waiting user_env stored in database…
I’ve just completed a full planting using the Loop-Plants-With-Filters. I planted the entire bed: carrots, leeks, corriander, pak choy, lettuce.
Thanks again for creating this. Soooo easy!
I did notice it didn’t change the status of the plants to “planted” in the Farm Designer. I tried SAVE IN META DATA : KEY = “status” and SAVE IN META DATA : VALUE = “planted” but they still say “planned”. After looking at the debug json, I also tried SAVE IN META DATA : KEY = “plant_stage” but it didn’t work either. Do you know the correct meta data key and values for the Status field (planned, planted, harvested) in the Farm Designer?
Hi steve,
happy to read this
it’s currently in test with more functionaly, i release a new version very soon.
(it s not a meta data, it’s a plant property)
Oh okay great. It’d be good to be able to set the plant status because then, if the routine is interrupted half way, it can restart by filtering only those that haven’t been planted.
I’ve set up the next Loop-Plants-With-Filters to do all the watering so I’ll kick that off now and see how it goes! …
i just released a new version v1.0.2 of this farmware with new functionnalities :
filter by coordinates, filter by plant stage, metadata filters operators , list of sequences instead of unique sequence, set plant stage, add offset X,Y when moving
Has anyone else found that this farmware has stopped working in the past 7 days or so? My farmbot picks up the watering tool, then when it goes to run the LPWF farmware… it E-stops?
