Ok... how about a countdown timer?
Either 'stand alone' or...
Superimposed on top of an existing tile?
This is just a 5 second timer to show how it works
On the left is a stand alone countdown tile.
On the right, a tile I created to show my current mode (active in this case) with the countdown (once activated) superimposed on the top
Any number of seconds (configurable)
Once the timer gets to 0 it goes back to the previous display
You will be able to trigger the timer from a device (like a contact or a switch) and also HSM or a mode change
I'm quite proud of this one..took a while to work out... going through beta now.. released soon.
Looking forward to using this one by the door (on a tablet), when the mode changes, and HSM is disarmed. Allows people to know whether they need to reach for the secret button, before the alarm goes off
Guys,
I have uploaded a virtual device container for use with this
My thanks to @stephack for being able to use his virtual container code
Driver is with the other one on GitHub
Just create a new virtual device and assign this driver
Then you can create as many display devices as you need and keep them all together.
Ok, that explains the issue i was having last night, I just checked and I see the data now. One of the examples had what looked like icons for on/off instead of words, how was that accomplished?
I take that back, the examples above had a mix of Super Tiles and normal tiles so I saw one of the normal tiles and thought it was possible to get icons.
This is really going to help clean up my Dashboard once I get this figured out, Andy, thanks for the great app!
That's great, icons will really make it stand out! One of the add-ins looked like it might count and display the number of open contacts its monitoring, is that the case? I'd love to be able to see at a glance
Doors 0/7 Windows 2/19 or something like that, Iris had that for Door contacts and it came in handy when going to turn on the AC. Thanks!
Actually, this came from a joke I had with @bravenel about any time I released an app, they released the same sort of thing as a built-in app
I just complained that they were copying me
No, the reason for the change of licensing terms is that I just get cheesed off when some people release 'new' versions of my apps under their own name claiming that they wrote it all
Or release 'new' apps containing 80% of one of my apps.
I'm happy to help anyone with their code if I can, but I spend a LOT of time working out code and releasing what I think are quite useful apps, so I like to get the credit for the code
All my future apps will be released under this license which gives me a legal challenge, should I wish to pursue it.
I definitely understand your reasoning for changing it. I won't act like I don't re-use other's code (although never 80%. lol), but I try to be very diligent in citing source and giving credit.
Curious question, why APIXU 's attribute mytile could be displayed right away, but other attributes (including other devices) need to be changed first to display. Any logical difference for the initialization?
Also, is it possible to support tile background color change based on the attributes' value?
I am not consistent in how I approach this. It depends on how much code I am using.
If it is just a few lines, I probably won't contact them (but will give credit), if it is core functionality I usually try to contact the original author.
I didn't write the Apixu driver but I suspect it's because the author uses the 'isStateChange: true' statement on that attribute but doesn't on others
This means that the 'mytile' will update when refreshed but other attributes will not update until something changes.
Currently no.
HE does not expose that setting as something we can programatically change.
