Worked like a charm. THANK YOU!
Okay, so Iām struggling and feeling really stupid about now. Iām sure Iām doing something wrong, but canāt for the life of me figure out what it is.
Iāve followed the instructions to a tee: installed the Maker API app, chosen my devices, allowed access via Remote/Cloud, added the sharptools URL, and copied the endpoint example.
I then created the custom tile, filled in the settings using my device ID and attribute, saved, hit Preview andā¦ I get the following message every time:
Iām sure Iām missing something obviousā¦ anyone have any ideas?
Can you share a screenshot of what your tile settings look like? Youāll want to redact the API Key for privacy purposes of course. Or feel free to PM me the screenshot.
Hi Josh, sure thingā¦ here you go:
It looks like you may have edited the settings in the Developer Console just above where the Custom Tile code is defined. Those settings should only be adjusted if youāre a developer looking to tweak the tile.
Youāll want to revert that change and edit the settings directly in the tile instance on your dashboard. Thereās some description and screenshots in the following post that should apply here as well:
Doh! Okay, got itā¦ works perfectly now! Thanks, Josh.
So this was working great until a few days ago, now Iām starting to get the following error. I didnāt change anythingā¦ any ideas?
I would check the Hubitat Maker API (app). Looks like the custom tile is having trouble communicating with that.
Thanks, Josh. I checked everything and couldnāt make sense of it, but today it just started working on its own again. Mustāve been a temporary glitch.
That definitely helps! I think I see where I was going off the rails.
Iām releasing a new version of this which uses the new Custom Tiles: Access to Things and Variables feature.
This means you no longer need to setup the Hubitat Maker API. Just pick from the list of devices you already have in SharpTools! Best yet, the updates all happen in real-time rather than relying on polling like the API approach does.
I donāt have any devices with HTML attributes that are still updating in realtime, so my testing of this was fairly limited, but if everythingās working well with it, Iāll update the main post with a link to this as an option. The original API driven version will remain as well if you prefer that.