Is there a way to trigger a token refresh for maker API if they are ever compromised? Or are they updated if I uninstall and reinstall the Maker API app at least?
Each instance has its own maker API token.
I see no area for a refresh, but if you install another instance it will use a new token.
There will be an option to refresh the access token in the next release.
@bravenel any chance you could add a QR code image of the token also? Just a suggestion 
I could use it in the app I am writing.
We will put this on our list to look into.
So in the platform 2.2.2.123 update it says there is now a Maker API refresh capability. Where is it located?
What's the difference in this and just removing Maker and then adding it back? It just keeps the previous devices selected?
Yes. And the application id # doesn't change.
Thanks
This is great, now I can update the token, and create a new QR code to scan into my app to provide the token (and my account which doesn't refresh) to the app. I ciphered those so the QR code information is useless without the app which knows how to decipher. So now I can "change the lock" any time I want and just generate a new qr code to give the keys to anyone with the app.
is there a way to write a refresh API with time delay ?
example ,I have a Shelly relay with power metering. when relay turn on it send this URL to Hubitat to refresh the status on Dashboard. but i want it to delay 5 seconds .. before hit Hubitat.
http://192.168.66.50/apps/api/200/devices/191/refresh?access_token=6ff1de4c-8b63-4297-9426-0fd81c04cbf9
how can i add timer for this?
thanks in advanced
If I am understanding you correctly, then you'd have to program the delay at the sending side (i.e. at the Shelly relay).
yes ,correct. at sending side in Shelly URL ,but i dont know how to add the a time delay to this below..
thanks
You can only add a delay on the hubitat side by modifying the Refresh command in the driver, or maybe make some kind of intermediate device that triggers a 2nd refresh 5s after the 1st one.
In other words, there is no "in box" way to delay a MakerAPI command itself, you would have to cobble together some other workaround.
ok thanks a lot for the info ,much appreciated 
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.




