YaleApp Token Update

[mordorf]

Thanks for porting over the YaleApp from smartthings to Hubitat. Without this I doubt I would have migrated to this platform as it is integral to my smart home automation.

When I had smartthings I used tasker and the autoinput plugin to automatically navigate to the app and update the token after my phone had restarted. This kept the token valid. However now I secure my Hubitat hub with a user and password as otherwise anyone with access to my home network could access the hub without needing to login. This makes it so that I cannot update the token using this method. If the Hubitat mobile app could remember the login credentials once entered tthis obviously wouldn't be a problem but unfortunately there doesn't seem to be a way to do this.
I was wondering if there is any way to automate the process of generating a new token?

Thanks

[Mark-C-uk]

It should update the token itself if it fails it should send a push and get a new token, all you need to do is arm the system from hubitat

…

On Wed, 19 Aug 2020, 10:31 mordorf, ***@***.***> wrote: Thanks for porting over the YaleApp from smartthings to Hubitat. Without this I doubt I would have migrated to this platform as it is integral to my smart home automation. When I had smartthings I used tasker and the autoinput plugin to automatically navigate to the app and update the token after my phone had restarted. This kept the token valid. However now I secure my Hubitat hub with a user and password as otherwise anyone with access to my home network could access the hub without needing to login. This makes it so that I cannot update the token using this method. If the Hubitat mobile app could remember the login credentials once entered tthis obviously wouldn't be a problem but unfortunately there doesn't seem to be a way to do this. I was wondering if there is any way to automate the process of generating a new token? Thanks — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD4YEZKZSDGO6XFLUVMNIFTSBOLW3ANCNFSM4QEXN74A> .

[mordorf]

Doesn't seem to work for me. Just had the notification stating the error so tried arming the alarm but it failed. Had to go into the app to manually update the token to get it to work.

[Mark-C-uk]

ok ive made sure these reflect my version on HE, looking at the code, give it 5 min then try again arming, there is an error handler which runs every 5. if that works i can code it to run straight away

[mordorf]

I'll have to wait a few days now before I get the error again. I don't think I can force it any way.
So once I get the error should I try and arm and then if it fails wait 5 minutes and try again?

[Mark-C-uk]

Try and re arm if not wait 5 then try again, what message is it sending back to you about the error?

On Tue, 25 Aug 2020, 17:14 mordorf, ***@***.***> wrote: I'll have to wait a few days now before I get the error again. I don't think I can force it any way. So once I get the error should I try and arm and then if it fails wait 5 minutes and try again?

it should last like a month, i cant remember last time a got an error

…

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD4YEZPOU7OLYALBCS3V3JDSCPPNJANCNFSM4QEXN74A> .

[mordorf]

OK as soon as I get the error again and I can test I'll let you know. It'll probably be a few days as I just have to wait, don't think I can force the error on demand. Thanks for all your help, much appreciated. :-)

…

On Tue, 25 Aug 2020, 17:24 Mark-C-uk, ***@***.***> wrote: Try and re arm if not wait 5 then try again, what message is it sending back to you about the error? On Tue, 25 Aug 2020, 17:14 mordorf, ***@***.***> wrote: > I'll have to wait a few days now before I get the error again. I don't > think I can force it any way. > So once I get the error should I try and arm and then if it fails wait 5 > minutes and try again? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#1 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AD4YEZPOU7OLYALBCS3V3JDSCPPNJANCNFSM4QEXN74A > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANKO2HZ5QEGKJ33HJMUSCI3SCPQUXANCNFSM4QEXN74A> .

[mordorf]

Not had the error since so still waiting for it to happen. It seemed to do it every two or three days when I first reported it. As soon as it happens again I'll let you know.

[Catley666]

Had this working perfectly in ST but cant seem to get this to work in HE. Error code: java.lang.NullPointerException: Cannot invoke method ArmDisRef() on null object on line 193 (method on)

[Mark-C-uk]

Drop me a message on Hubitat Community, what we're you trying to do at the time?

…

On Sun, 2 Jan 2022, 19:02 Catley666, ***@***.***> wrote: Had this working perfectly in ST but cant seem to get this to work in HE. Error code: java.lang.NullPointerException: Cannot invoke method ArmDisRef() on null object on line 193 (method on) — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD4YEZNFV26J66SWJ5FKKALUUCONBANCNFSM4QEXN74A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[Mark-C-uk]

ive added a dev folder, id done some code cleaning, but never tried it on a fresh install