Hey guys, reading and reading, and been experimenting with different configurations for weeks and can’t get joy. New AT&T Fiber 1Gb (awesome), but modem will not allow port forward for port 443 to anything. I have HTTPS working with DuckDNS, but I have to enter xxx.duckdns.org:8123. Not the end of the world at first…
Well the whole reason for wanting HA was for integrations. Now, curl commands error out due to certificate issues, and getting above my head for how to correct. Don’t know enough to know how concerned I should be for security, but know that I want https outside of my local network, and http inside. I can’t make http work. NGINX needs port 443. I’m lost…
No, a friend on the SecuritySpy (SS) website helped me use my security cameras as motion detectors and sending curl commands to HA. Right now HTTPS is down, as I had to # out the ssl commands to make the functionality work.
If you can not make the motion detection work securely then you need to set up a reverse proxy. This will enable you to use http inside your network and you can expose home assistant via https on the external network.
Search for Nginx or Caddy. Both available as addons for home assistant.
There in lies the problem. Tried NGINX and can’t use port 443, so never could make it work. AT&T won’t release the port, as it’s built into their BGW210-700 load (per a cs rep) for TV WAP Services.
So bit the bullet and went to Nabu Casa. Don’t like paying $5 a month while I’m in testing mode, but tired of wasting months with DuckDNS issues. Now back to the Curl issue. The whole premise was to coordinate motion detection from SecuritySpy on my Mac to send a webhook to HA.
, but only the garage script actually runs. I’ve executed the automations within HA and they function correctly, but the webhook ID doesn’t seem to be coming through except for the one mentioned. The scripts are identical except for their name, and I did try as paul2020 suggested to change the quote aspects, but with no joy.
One note, from within Script Editor, I can “play” the garage script and it functions, whereas the others will not. To me, this indicates that the curl command
I turned on logger: in my configuration.yaml file and it brought my HA to a crawl with too many entries. I changed it to…
This was a cut/paste from Boxgrove on SecuritySpy forum, but I think it’s something in the pasting of the quotes here. I’ve been also trying single quotes and I’ll try a few changes. As for the data, there is no data to pass. I just want that when the webhook is called to execute the automation. If I need to pass data, but that data isn’t used anywhere, then that’s fine.
but here’s the latest…
So I went into Terminal on Mac and entered the curl command, and it executed with no errors. Went back into File Editor on HA and found this line in the debug for the appropriate time stamp…
2020-07-15 00:46:20 DEBUG (MainThread) [homeassistant.components.webhook] Handling webhook POST payload for driveway_ss_trigger_1
So if I’m thinking about this correctly, the curl command is getting to HA. HA is recognizing the webhook, but it is not executing. Is this because of the lack of data in the curl command? The garage_ss_trigger_1 works just fine and it’s the same syntax. I can manually execute the automation in the Configuration and it works. here is the excerpt from the automations.yaml file…
So here’s a question…where can I find the details relative to the syntax and description for items like this? In looking at the home-assistant.io website, the reference is there but not the underlying explanations and I’d like to learn.