I’m currently working on the finer details of my external integration with the display of departure points. I’m currently configuring this via the widget. The advantage here is that I can (with regard to the API provider) display multiple simultaneous widgets with different geolocations.
Example story:
Every Saturday, Grandma comes to visit. A bit shaky, but her will is unbroken, and every Saturday she calls beforehand: « I’m on my way, I’ll be there soon… » and every time they think -Hopefully it works, does she catch the right train this time and doesn’t go in the wrong direction again-
Solution: Widget 2x with 2 geolocations on a « Grandma » dashboard. Result:
A click and they can tell Grandma: « Grandma, this time but correctly, you go to your stop XY, the bus leaves in 10 minutes there. It’s line 12 and it says « Endhaltestelle » as the destination at the front. At the ferry station, you change to ABC to ferry number 33 and go. » I’ll leave with the S-Bahn in 20 minutes and pick you up at the train station in Mannheim."
So much for the purely fictional story (or how about the departure point of your son at school?)
Now, however, the specialists come into play here: I wanted to create a scene that offers that when the time on one of the value tiles is reached, an action is triggered.
This is possible, but only devices can transmit/record states. In my example above (2 widgets, 6 tiles), I would therefore have to offer 12 virtual devices so that the user can create the scene.
Question 1: Is there another solution
Question 2: Why shouldn’t/shouldn’t widgets also be used as scene triggers?
Greetings
Tom