Stuck at "Logging In..."

[waseltzer]

I bought a new phone (Google Pixel 3) and I can't get HomeP (v 2.5) to work now.
The watch app is stuck at "Logging in..."
I'm sure I've entered the correct MyQ username/password in the HomeP settings.

The Chamberlain MyQ app is working fine on this phone.

Ideas?

Thanks,
Wayne

[kostopman]

Hello.
Thank you very much for your homep pebble app. I've been using it everyday.
It has been working wonderful until a month ago. I am stuck at loggin in just like waseltzer above.
I bet myq site changed their logging process. Could you please update? Thank you so much again!

[SeaPea]

Unfortunately I have not used my Pebble in over a year so I have not kept up with the changes after the Pebble servers were shutdown and was using CloudPebble for development. HomeP uses your Pebble account token as part of the encryption key for storing your MyQ password locally since the MyQ service does not appear to have a long lived token access. It is possible something has happened with that Pebble account token since the shutdown. Have you changed your Pebble phone app over to the Rebble services?

[kostopman]

Thank you very much for your reply! I have not transfered my Pebble app to rebble. I'll try to use rebble and will try homep app and let you know. Again, really appreciate your response!

…

On Mar 22, 2019 10:13 PM, "Colin" ***@***.***> wrote: Unfortunately I have not used my Pebble in over a year so I have not kept up with the changes after the Pebble servers were shutdown and was using CloudPebble for development. HomeP uses your Pebble account token as part of the encryption key for storing your MyQ password locally since the MyQ service does not appear to have a long lived token access. It is possible something has happened with that Pebble account token since the shutdown. Have you changed your Pebble phone app over to the Rebble services? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Auk8BCUsks6FZLB1jeF-LTLzkbwRfuPbks5vZZvggaJpZM4b3eJp> .

[SeaPea]

Just a FYI, I wasn't recommending switching over to Rebble. I'm not sure what status their services are in and things look a little quiet on a lot of Pebble projects.

[kostopman]

I got it. So homep is not going to work, right? On Mar 22, 2019 10:22 PM, "Colin" <notifications@github.com> wrote: Just a FYI, I wasn't recommending switching over to Rebble. I'm not sure what status their services are in and things look a little quiet on a lot of Pebble projects. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Auk8BG0Oqe-v6IqnDhhw6EYRG5c58J2Yks5vZZ36gaJpZM4b3eJp> .

[kostopman]

Now I see what you meant in the previous email. I backed up all the watchface and apps, so I don't need rebble service at all actually. Thank you!

…

On Mar 22, 2019 10:23 PM, "Jaehyuk Ha" ***@***.***> wrote: I got it. So homep is not going to work, right? On Mar 22, 2019 10:22 PM, "Colin" ***@***.***> wrote: Just a FYI, I wasn't recommending switching over to Rebble. I'm not sure what status their services are in and things look a little quiet on a lot of Pebble projects. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Auk8BG0Oqe-v6IqnDhhw6EYRG5c58J2Yks5vZZ36gaJpZM4b3eJp> .

[SeaPea]

If I have time I'll see if I can get a Dev environment setup and emulator running and see what is going on. I don't think they have changed the API on the MyQ end. I defected to the Apple side a while ago, but have been contemplating writing my own MyQ for Apple Watch since they may a change to the official app that made it depend on a connection to the app on the phone yet a prior version didn't have this dependency.

[kostopman]

I already really appreciate you replied back to me. I really did not expect that. Only if you have some spare time, it will be wonderful you look at what's going on. Thanks again!

…

On Mar 22, 2019 10:35 PM, "Colin" ***@***.***> wrote: If I have time I'll see if I can get a Dev environment setup and emulator running and see what is going on. I don't think they have changed the API on the MyQ end. I defected to the Apple side a while ago, but have been contemplating writing my own MyQ for Apple Watch since they may a change to the official app that made it depend on a connection to the app on the phone yet a prior version didn't have this dependency. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Auk8BLaAbHBJmvCR-wF1bhakM_zbCoS8ks5vZaEIgaJpZM4b3eJp> .

[waseltzer]

I changed to Rebble a while ago and HomeP continued to work on my Galaxy S7.
After I dropped my phone and a bus ran it over (!), I replaced it with a Pixel 3.
Now, I can't get HomeP to login.

Maybe the Pebble account token didn't get transferred to the new phone?
Any ideas on how to recreate it?

Thanks,
Wayne