Sometime in the past week, an automation I'd set up stopped working. I have a rule in a "Sonoff s31 15A" outlet running tasmota to make a webhook call under certain circumstances to a pair of http-in (GET) nodes on node red. I attached a debug node to those http-in nodes and noted that nothing was…

OK. 2 things: The problem appears to be restricted to mDNS (SMH) When I edited the WebSend command, I introduced http:// (because my eye skipped over to the end of the line in the tasmota commands doc which reads " WebSend [myserver.com] /fancy/data.php?log=1234 sends http://myserver.com/fancy/dat…

top - 12:09:37 up 19:43, 2 users, load average: 0.99, 1.01, 1.15 Tasks: 120 total, 1 running, 67 sleeping, 0 stopped, 0 zombie %Cpu(s): 10.1 us, 27.6 sy, 0.0 ni, 62.3 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 879284 total, 33708 free, 323380 used, 522196 buff/cache KiB Swap…

No problems there. Not at that moment anyway.

Agreed, though it's during those conditions when I get the "Connect failed" message in tasmota emanating from the WebSend call. And I suspect that was the case when I was testing in the browser yesterday too, though I didn't check it at that time. Point is, all other functions of the Pi seemed to …

I'm disappointed that I haven't heard back from Ubiquiti yet. Hopefully I'll have some time to dig into this again this weekend. It has to be the Unifi os update. Webhooks just suddenly stop working on 2 devices... it's too coincidental. I guess one thing I can try is a tasmota firmware update...

I just poured through my unifiOS logs. Can't find a damned thing. Lots of occurrences of both Sonoffs, but nothing that indicates a problem. I learned that I can issue the WebSend commands manually from the Sonoffs in tasmota and I tried doing it with a tail -f on both the node red logs and with …

I'm a novice when it comes to network debugging, so I was just reading about tcpdump. I found this example to isolating http GET requests: tcpdump -vvAls0 | grep 'GET' Is that continuous output like a tail -f and would that work if I run it on the UDM as well as the pi?

You need to look for traffic on port 1880. Close down any browser windows connected to node-red so that they don't add to the traffic. Or maybe look for traffic from the Tasmota IP I don't use tcpdump very often but my notes tell me that this site has lots of useful examples. https://danielmiessl…

Yeah, that's where I got the command I pasted above. Thanks! I will try and see.

OK! I installed tcpdump and ran the test. It appears that the webhook IS hitting the pi and that it's not a unifios issue at all: This is the command issued on tasmota: WebSend [http://raspberrypi.local:1880] /desklighton raspberrypi[2022-10-30 11:07:17]:~>sudo tcpdump host 192.168.1.43 tcpdump…

Node-RED

Node-RED Forum

Debugging http in node issues

General

Colin 30 October 2022 08:31 40

You may have to run something like tcpdump to check the requests are getting to pi and if so why they are getting blocked.

Topic		Replies	Views
I don't understand this message I see in the debug output General	9	471	16 January 2022
Problems after update General	32	2406	7 July 2019
Telegram ENETUNREACH General telegram	13	304	29 May 2023
Need help rebuilding home automation raspberry pi General	146	838	31 March 2026
Problem Connecting to Tuya Device General	7	1614	16 June 2021

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Debugging http in node issues

Related topics