When designing a table the onscreen table only updates whenever you do a refresh of the Table. It should update the dashboard when any monitored attribute changes, subject to your Publishing controls. The other Tile Builder child apps work this same way.
I think your variables must contain the word "variable" in order for them to show like that. Here are mine: Look specifically at myVariable in each.
My intention was that the dashboard tile (not the onscreen table) does not get updated even when the variable gets updated and it has new values. I can also see the new events in the variable device connector page.
For example:
Hub variables page:
My screen looks different and I think this is because I am using the device group option. Any way my variables do not include the word "variable" in their name and the device page for the variable connector looks like this:
I added some logic so that a null value on a non-populated attribute would default to 0.0 until it gets populated. It's in an update I just pushed out for Attribute Monitor and Activity Monitor.
I was starting to think along similar lines but you have to be careful with any tiles that regenerate frequently. A motion sensor that fired 300 times a day could cause the "Summary" tile to also regenerate at least 300 times a day and together might use more CPU than you would like.
FYI I found a typo on line 969 of Grid this AM that cause a crash. I've already released version 1.0.2 to address this. That is the only change in this version.
I have some devices where the battery goes from 100% to not reporting with no stops in between so monitoring Inactive battery devices helps me find those.
Thanks, I figured it out. The word "variable" is the name of the last event (what changed) which I was concatenating with the value. What I did was break out %lastEvent% to be the name of the last event and %lastEventValue% (new) to be the associated value.
Would naming the storage device "." (just a single dot) cause issues? It seemed to work fine when I renamed it, but sometime during the last several days two problems developed.
Problem 1 is where trying to edit the storage device yields a blank page, yet there is nothing related in the log (I did enable info, trace and debug logging in the parent app:
Yes, the names of the storage devices are hard coded in there. The good news is the storage device only contains the published tables.
If you delete the storage device and then recreate it with the original name, reconnect it in the app you should be able to just republish each of your tiles without any redo.
I see the issue with this. I forgot to comment out a line with yesterday's update. I will push out an update tonight that will fix it and the MAM issue too.
I pushed out an update tonight. If you change your Template Column 2 to say %lastEventValue% you will get what you want. The inline "Text Fields" help is updated but I have to add to the online doc.
Thanks for the update! Activity vs Multi-Attribute tiles are back to normal.
Editing the storage device, however, is still an issue.
I need to edit it in order to delete it (unless there is another way to delete a device?)
I found that the page isn't really blank - it has a source, but the actual browser page is blank, and in the dev console there is the following message:
You can force a device deletion using this technique:
The message "The new child element contains the parent" sounds like it has a circular reference.
A period (.) in some operating systems means the current working directory and (..) means the parent directory. So that might be confusing it.
I just created an empty Storage Device and it came up as expected. Sometimes CSS\HTML elements can be transient in memory so a reboot might clear it.
Hi @garyjmilne ,
Thanks a lot. Much appriciated and I can confirm that this is now fixed and using the %lastEventValue% fixed this issue.
As for the other issue I am seeing, this is not yet working as expected. The dashboard table does not update when the variable value has changed. It keeps the old values till you go back to the child app page and click Publish and Subscribe.
I tries using the 'more options' to try and see the logs and see what is going on but I have to admit that this is beyond me. If you could instruct me which logging option to turn ON I could attach the relevant lof file.
