SmartTiles v5.8: Deployed to Blue & Green Editions. Release notes, etc. (follow this Topic for updates...)

So, on ios when you select the preview option, although it’s embedded, safari by default allows a share option by default on the bottom bar. If you tap it you can copy the url.

It still works, just tested on my work ipad.

Whenever I try to use the auto refresh on idle inside Fully, it refreshes back to the launch screen (with the rocket in the green button) and prompts me to log in. Can I ask how you got this to work please?

Thanks,

Jon

That’s a great question, I have not touched it in a long time. Let me look when I get time this morning or tonight and get back to you. It is possible that it is still using the old access token? and that stays active after I did the log in on screen in Fully. I remember logging in. and I have had to do it a few times but very rarely.

Last night I set up a Tasker profile to do the wake screen hack every hour. And I didn’t have to log back in this morning! Perhaps it was a fluke. But there might be enough activity on the ST page to keep the session alive.

I’m going to try the same on a couple of other test devices and keep watching the main ST tablet. I’ll report back. It’s probably too good to be true.

I went and looked quick and the start URL was the old one with the access token. Gaaah I didn’t realize that. Guess I owe ALOT of apologies since I was saying it worked?

Let me tinker with it some so I can give you more accurate information. Right now I am fighting it cause it keeps shutting down on me? Something is killing it?

So old maintenance man saying holds true, don’t touch it if it’s working.

Well, this “feature” comes and goes, seemingly with every update.

I have been working on this off and on all day. Update is I have figured out a way to have Tasker do the login on the smarttiles screen with the rocket. I just can’t seem to nail the Tasker profile triggers to detect I’m on the login screen. I’m close, back to the lab (desk) later to tinker some more.

I’ll update what I find.

While I love the enthusiasm and community sharing, I feel it’s important to remind everyone that SmartTiles “V6” completely resolves the uncontrolled login timeout issue, so take care not to invest too much time in workarounds.

Our Beta testing is going very well. We’re identifying and classifing critical loose ends that need to be addressed before we can set a release date.

2 Likes

I have a custom device type for a switch working fine with the SmartThings app and the status reflects fine in SmartTiles… but SmartTiles sends the opposite on/off commands from SmartThings. In the SmartThings app, when off, the switch calls the off method (which seems backwards to me). In the SmartTiles app, when off, the switch calls the on method. Any ideas how to fix this to work properly with both apps?

If you share the code of your custom DTH, I can perhaps take a glance and see if there is an “obvious” problem. Please share via a GitHub link, Gist, or be sure to use the format option (<\>) if pasting directly response.

Meanwhile, you can test your Dashboard on Desktop Chrome or Firebox debugger, using Ctrl-Shift-I; the “Network” tab of the debugger will show the exact command being sent to our SmartApp from the web page.

Basically … if SmartTiles “thinks” the switch is Off (which it will display as dimmed bulb or slider in the left-position), then it will always only issue an On when clicked; unless you’ve encountered a really odd bug. Using your debugger will confirm the command that is being sent.

Not sure if this has been answered, but is there a way to make a SmartTiles dashboard that does NOT need login credentials?

For example, I have someone I want to be able to control certain lights and switches in my house, but do NOT want him to have full access to my SmartThings. How can I accomplish that??

Not anymore, due to changes we were required to implement by the request of SmartThings.

SmartTiles “V6” will restore and enhance “dashboard sharing features” (with limited permissions, etc.) at some point after public release.

Hi @tgauchat, thanks for the response. I uploaded the device type to GitHub:

I haven’t had a chance to test with Chrome or Firebox as mentioned, will try that when home from work this evening. But I did add a few debug lines in the on/off methods and see that each is called by both SmartThings and SmartTiles. The currently committed code works for SmartTiles, as it calls the “on” method when in an off state. SmartThings does the opposite so even though the icon still represents the state correctly (showing its off), it calls the “off” method.

Hope you can see what I am missing… thanks a lot!

Thanks… well… there’s one obvious atypical coding, though it shouldn’t directly affect SmartTiles:

###The “state” to “actions” settings of the standardTile are backwards.

If state = on then the action when tapping the SmartThings Tile should be to call action: switch.off.

If you’ve coded this standardTile the “wrong way” for a reason, then that “reason” is likely why SmartTiles is not consistent with SmartThings for this DTH.

###In other words: Don’t DO THIS…

According to the definition of Capability “Switch”, the on() command must always turn a device ON, not “so turn it off”; and similarly for the off() command.

1 Like

I’m an idiot, that was it… thanks for spotting that. So SmartThings uses these “actions” on button click while SmartTiles I assume just sends the logical command :). Thanks so much, appreciate your time (and great work with SmartTiles)!

1 Like

@tgauchat - in V6 are you planning to have the ability to wake up a tablet display based on motion sensed by the tablet’s camera?

1 Like

We give users the ability to run in their favorite browser; and we don’t have access to the camera or other hardware functions.

So… try Tasker or similar, or use a browser like Fully Kiosk which includes this ability!

###Many, many good discussions on these configurations at Topic:

V6 is a Web App, just like the current version. Technically, it’s not possible to wake a device from a browser.

Not to contradict my esteemed partner, but, a bit more accurately, Fully Kiosk Browser and other value-add Android Apps (and perhaps some for iOS?) absolutely can “wake the device”.

It is just not within the direct ability of the web pages / web “apps” that run inside the browser and maintain compatibility across many browsers … yet.

Chrome (etc.) are actually exposing more and more “hardware access” abilities to their browsers! The browser can report GPS location to web-apps, for example, and Chrome has “USB port” access controls in their Settings menu – but I haven’t seen web pages directly access USB yet. So … the future is bright! :sunny:

2 Likes

Thanks. I was hoping to get by with not using Fully & Tasker, but I will now dig in to them.

1 Like