Kevin Hartley
Kevin Hartley
See, for me, switching it to https for the facebook URL and then switching the local URL to http worked. The problem then was that the login timed out and...
Correction, I was confusing this with the npm fbcli tool. Oops. I CAN switch it to https for the facebook URL and then switch the local back to http, and...
It looks like I got it working...it's a pain in the neck, but here's the workaround: `https://graph.facebook.com/v2.12/oauth/access_token?client_id={yourappid}&redirect_uri={your redirect URL with port AND TRAILING SLASH}&client_secret={yoursecretid}&code={the part after the code= in the...
G;ad I could help with the workaround until someone more knowledgeable can help with changing the http to https.
> You are to replace the stuff in `` with your entries. Yes, I know that. I was redacting the actual device names.
 No, it's in scripts, not automations.
As in the name of the script? I only have the one manual_notify script. It can be seen in the logs I pasted above. Here is a snippet showing it:...
What should it look like?
This is what was setup back when I added the integration a year or so ago: ```` alias: keymaster_ Lock Notifications triggers: - event_type: keymaster_lock_state_changed event_data: lockname: trigger: event conditions:...
Any ideas on how to fix it?