create a random number for MoveTo commands.
This feature does not exist yet, but we have gotten some requests for it.
Is there a chance to implement this maybe as a farmware?
Yes, it is possible to implement this as a Farmware. Please avoid adding too much logic to Farmware, as the system is going to change drasticly in the next 18 months (details below).
It would be so helpful if one could save … information or … state in one sequence … and read this in another sequence for some logic.
This is on the road map. We are planning on making big changes to the “MARK AS…” step to increase its usefulness. We have not started work on this yet.
Any ideas how to do this at the moment?
If you are comfortable with software development and have a very specific set of requirements, the best way to solve the problem is to write an external “remote control” server. I made an example of that here.
As a side note, users are highly discouraged from authoring new Farmware, or relying on Farmware as their main means of device control. Farmware adoption has been extremely low (< 10 users), while also suffering from many legacy support issues. We’ve made the decision that the next version of the Farmware system will be a complete re-write and there will most likely not be a migration path, since so few people have used the system.
This was not an easy decision for us. For the 8 people that currently write Farmware, it was tough news to bear. I explain my logic a bit more in this Github thread:
The reality with [farmware] is that it has eaten up huge chunks of our developer hours (sometimes entire work weeks). I only have evidence of 8 other people actually authoring farmware … we’ve spent countless weeks implementing these features, hunting bugs and making compromises elsewhere in the system to allow for on-device scripting support. I can’t say it makes sense from a business perspective to continue encouraging people to write on-device software, at least with the way it is currently architected.