.
There is a nice livestream going on right now:
One awesome thing already learned that I never knew before: hold down Command (or Control if on Windows) as you click the workspace and you get a searchable dialog box to quickly add a node.. what a huge timesaveer!
2 Likes
Here is the post I referenced in the HA forum. Hopefully it's still relevant as I havent used these nodes in some time.
I'm trying to set this up but when I toggle my test switch, nothing comes out the device node.
I also get a 404 in my NR logs
[image]
I am running NR in a container but I don't think that is the issue as I have other integration using maker api without issue.
Edit: I see @kevin posted a similar issue earlier on. I'm also running NR as a HA addon.
@kevin , did you ever get this sorted out?
Edit 2: Figured it out. Just needed to read the Addon docs in details. @kevin , fyi, all http endpoints…
Didn’t work, thank for trying
aaiyar
June 15, 2020, 4:49pm
2874
Wait - you have NR listening on port 8123 and not 1880? 8123 used to be the starting/standard Home Assistant web interface,
2 Likes
Nice catch @aaiyar . You are correct. Port 8123 is for the HA front-end only.
@frmWink2Hubitat , the port in the url should match the port chosen in the the NR Addon (default is 1880). Click on the Supervisor tab, then select the NR Addon. At the bottom should be a cog icon for the configuration settings. Take a look at the port selected there.
1 Like
Still didn’t work I’m seeing
Blockquote tpClient/4.5.2 (Java/1.8.0_181))
[15/Jun/2020:13:55:00 -0400] 401 -(192.168.1.226) POST /endpoint/hubitat/webhook HTTP/1.1 (Apache-HttpClient/4.5.2 (Java/1.8.0_181))
[15/Jun/2020:13:55:00 -0400] 401 -(192.168.1.226) POST /endpoint/hubitat/webhook HTTP/1.1 (Apache-HttpClient/4.5.2 (Java/1.8.0_181))
[15/Jun/2020:13:55:00 -0400] 401 -(192.168.1.226) POST /endpoint/hubitat/webhook HTTP/1.1 (Apache-HttpClient/4.5.2 (Java/1.8.0_181))
Doesn’t that mean it should be working?
Do you have authentication on NR? You seem receive an error 401
If so, you can look at the FAQ on first post
See answer below from @erktrek
your webhook config in NR does not have "endpoint" in it.. shouldn't it be
"/endpoint/hubitat/webhook" ??
or remove "/endpoint/hubitat/webhook" from Maker API call and just use "/hubitat/webhook"..
2 Likes
@fblackburn thx. I finally give up, I’ve done both. It fixed the log but still no update
Blockquote Jun 15:36:27 - [info] [server:Home Assistant] Closing WebSocket http://supervisor/core
15 Jun 15:36:27 - [info] Stopped flows
15 Jun 15:36:27 - [info] Starting flows
15 Jun 15:36:27 - [info] [hubitat config:Hubitatm] Starting endpoint for /endpoint/hubitat/webhook
15 Jun 15:36:27 - [info] Started flows
[15/Jun/2020:15:36:27 -0400] 200 192.168.1.154, 172.30.32.1(172.30.32.2) POST /flows HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.1 Safari/605.1.15)
15 Jun 15:36:27 - [info] [hubitat device:Led strip] Initialized. switch: on
15 Jun 15:36:32 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
15 Jun 15:36:32 - [info] [server:Home Assistant] WebSocket Connected to http://supervisor/core
@erktrek @fblackburn
For NodeRed Addon in HomeAssistant the endpoint is exposed differently.
From addon docs
@frmWink2Hubitat , if you decide to try again, shoot me a PM (here or over in the HA forums). I can easily set this up again and send you screenshots.
4 Likes
okay but doesn't that mean you also need to add "/endpoint/,,,," to your node-red config?
According to the screenshot it looks like you just have "/hubitat/webhook" or am I still missing something?
Thanks man but h.a has broken me. Thanks for all your help
erktrek:
okay but doesn't that mean you also need to add "/endpoint/,,,," to your node-red config?
Actually, you dont. It just need to be included in the POST url in Maker Api.
His issue may be 2 fold...entering the correct port and the correct url.
1 Like
very cool thanks.. wasn't clear from the info @frmWink2Hubitat posted. so whats the advantage to running NR in HA ? - apologies if this was asked before.
It's only a benefit if you are already using HA.
NR gets backed up and restored along with everything else in HA snapshots
NR is preconfigured with most of the HA relevant nodes preinstalled
NR webUI can be accessed in the HA frontend/mobile app both locally and remotely (if you have remote access configured)
Edit: forgot to mention:
extremely easy to install..pretty much just have to enter a few config settings and click a button and the container is built. Takes less than a minute to get running if u are familiar with HA addons.
3 Likes
This is why I love it, there has been a few times where I wasn't home and was able to dork around with some NR stuff over Nabu Casa
kevin
June 16, 2020, 12:22am
2888
This is not related to HA but to Dockerised Node-RED.
I wish you well but there are obstacles to familiarise yourself with in everything technical.
1 Like
So I totally deleted the vm from scratch, deleted and reinstalled makerapi, and that worked. Thanks @stephack
1 Like