-
-
Notifications
You must be signed in to change notification settings - Fork 231
Description
We now have numerous OpenHASP devices installed for our demonstration and testing. Each of them has different pages, and the pages are in different orders. For example, in one room the order might be:
- Room Controls
- Room Climate
- Outside Weather
- Emergency Services
The next room might be:
- Room Controls
- Emergency Services
- Music Controls
- Outside Weather
- Water Controls
In the current design, we have to keep track of the order of the pages to update the Weather Page - for example - across numerous devices.
If the Weather Page had a "guid" associated with it, and commands could be sent using that guid, then page updates could be done regardless of the page order.
For example, if I used:
{"page":2, "guid":"00B0D063C226", "comment":"---------- Page 2 ----------"}
{"id":14,"obj":"gauge","x":10,"y":65,"w":150,"h":150,"label_count":7,"line_count":25,"text_font":16,"val":10}
Then I could update the gauge maybe using the command:
p[00B0D063C226]b14.val=100
And this command would work on any device to update the gauge on the page with that guid, no matter what the order of pages was.
If my Weather Page in the example above had that same guid on both devices, then I can update the Weather Page on either device without having to keep track of the page order.
In addition, if in my management portal I assign the guids to pages, then whether they were my pages or shared pages they could be updated regardless of which devices had them and in what page order.
This also would not be a breaking change ... unless I missed something.
And maybe there is another way to do this that I missed?