Deleted firebase. Turns out I required it in my authenticate.js file. I won't really use the authenticate.js file, but I'll clean that up later.
Determining if error is in routing, authentication, or both.
Pointless change to try to trick nest API request limit.
Trying to figure out why my side keeps responding with status 403
Trying to figure out why my side keeps responding with status 403
Trying to figure out why the devices aren't showing up.
commit again?
I think that the forbidden 403 status is caused by not originating with the Ooma.herokuapp.com/auth/nest url
I'm pretty sure that I need to begin at /auth/nest to avoid the 403 error. Still trying to figure out why it doesn't show any devices.
I'm pretty sure that I need to begin at /auth/nest to avoid the 403 error. Still trying to figure out why it doesn't show any devices. I changed the firebase url from wss to https
I'm pretty sure that I need to begin at /auth/nest to avoid the 403 error. Still trying to figure out why it doesn't show any devices. Adding error handling to authentication.
Incorporated error handling incase the authentication is messing up for access to firebase. If so then we'll know more what's up.
changed https protocol to wss
Trying to connect to /devices.
Trying to connect to /devices.
trying to connect to devices.
Incorporating code someone posted in stackOverflow
Removing the error-handler dependency and updating the firebase dependency.
Updated firebase.
I think I figured out the issue. The permissions Dennis set up were only for away/home status so that's all it would let me see.