The interface can look like this quick draft:
Ideal interface should also parse substrings using (multiple) delimiters defined by user, for example Space and “:” to simplify parsing further. (I’m not very good at JSONs, so it might be an unnecessary feature)
It would be even more nice to assign a type to it. E.g. when I want a time, it could make me a time variable which I can use. In the above case it requires me to construct everything back to a time variable. It might not be needed for this kind of project, but when I’m working with multiple dates for scheduling, let’s say, parking time or walking my non-existing dog, it may come in handy to standardize everything to Unix time and have the user in the interface decide how to display it, e.g. AM, PM or 24-hour clock.
or have i got this upside down? (I’m just checking before i get too deep into this!)
im going to try and write code so my house knows what the day might be like and configure the ventilation accordingly (e.g. hot day predicted, get the cool air circulating early on, if cool day, no need to move any cool air…)
That should be basically it yes. You could write your own parser to proces the information, like I did, but the Blynk-guys obviously can improve on that and make life more easy for everyone. JSON is pretty much the standard.