Closed flesh420x closed 10 months ago
I was able to get this figured out. Turns out you HAVE to use the ipAddress variable when using bridge mode in docker. You also need to use the cloud.hubitat.com/api line for the callback URL or it will not work. For some weird reason I also had to delete and re-add the port mappings for it to show up. I now have it deployed and working as quick as it did when using Heroku
Verify the following before opening an trouble issue
Go over all the following points, and put an
x
in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!About Your Setup
Hub Platform (SmartThings or Hubitat): Hubitat
How many devices are detected?: 0
iOS or Android?: iOS
Mobile App Version(Not required):
App/SmartApp Version: 4.2.3.0
Device Handler/Driver Version
Heroku Server Version: N/A - running in docker. I am happy to screen share for troubleshooting
Expected Behavior
When I click the login button to get the amazon cookie for the server it should get my login and say "authentication good."
Current Behavior
When signing in it refreshed back to the server page as it's supposed to but does not show a login cookie nor does it show in the Hubitat settings that I've been logged in.
Steps to Reproduce (for bugs)
Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant
Context
**How has this issue affected you? What are you trying to accomplish? I cannot use echo speaks atm. It used to work until my Heroku was shutdown (I'm not paying them). It worked a little when I first set it up on Docker but was slow to respond after the first attempt to send commands.
Providing context helps us come up with a solution that is most useful in the real world Help me understand what the problem may be, if it's me, the code, or hubitat. Get signed in and continue using EchoSpeaks
Please include a copy of any relevant log output to assist in tracking down the bug