A gee it would be nice request.... on the free form grid under the grid layout a way to delete a row and have everything move up or to insert a row would be amazingly handy. Or even to move row X to Y.
1 Like
Yeah, a nice "to have".
I created a Presence grid and it sorted it in alpha as expected.
My tiny brain didn't like it as the Guest line was between the wife and me so from a distance it was hard to make out who was here.
I solved it by a maintenance issue where I had to delete the Guest and re-add. The grid then popped it to the top so now my wife and I are together.
How nice. 
Morning G! - I updated today to .148 - this began showing in my logs.
It includes 2 of the tiles from the storage unit, both at temp sensor tables that have been working perfectly for ... months?
As I undertand it from the tidbits in HE notes there was changes in network stuff today. It looked mundane, but now I'm skeptical.
I've set both these tiles to refresh in larger periods (2-3 minutes) but the message in the logs was unaffected.
Thoughts? and you taking 2 months away. NOT ALLOWED! kidding of course.
Having just said that, I think I'll roll off .148 back to .147. Come to think about it, I just changed a driver last night on a temp sensor (one tile in this storage is a MAM, the other a Grid - and both revolve around temp reporting). Going to roll back off that new driver first...
Shu
Just updated. Lots of TB tiles so I'm watching....
Okay G. Mea Culpa. Unrelated to Tile Builder in anyway. Went away when I put the sonoff temp/humidity driver back.
Yes, I've seen others report something similar. I wonder what the Limit number is for Limit Exceeded Exception to occur. Seems like it a new threshold.
I introduced the Republish Delay quite a while ago for this very type of thing where you have one or more sensors updating may more frequently that you would like. This lets you set a minimum time between subsequent publishings.
If your Republish Delay is 5 minutes (seems about right for temperatures) then it will ignore any events and not update the tile until the next event after the 5 minute delay.
Event Timeout groups together events into a single update. So, 10 lights get turned on at sunset, you don't need to draw the tile 10 times. The Event Timeout waits until the delay period is over and immediately publishes whatever it has.
1 Like
I have no logs so far. 
Getting this error all of a sudden. The tile is still working but I will disable it for now I guess. I wasn’t working with the app for days so it’s sudden and new. Logs don’t go back far enough to know when it started.
The log is telling us that there is some unknown Limit that has been exceeded. Unfortunately nobody seems to know what the Limit is, how is is calculated, what the measurement is or what period it is averaged over.
Some have said a reboot works for them but my guess is that it just resets the counters and the interval.
I'd recommend that you take a look at the tile and see if you really need it to update as frequently as it does. For example, if it were reporting temperatures perhaps you have a very chatty temp sensor that is reporting way too often or perhaps reporting 1/10th of a degree changes. But is that really needed?
There are a couple of controls in the Publish section which relate to reducing the number of times createTile() is called. I'll let you read about them in the post above.
2 Likes
Well it’s a bunch of motion sensors but I’ll change the time…
1 Like
Not surprised, they generate a lot of events.
