Rule Logs Location

🎬 Get Started
1

you'd think after 7 years of home automation (using vera lite, vera edge, hass.io, ST, and Hubitiat) -- -and 20+ years as a professional software developer - that I could figure this out. I can't.

Is there a single location I can look to see when a rule fired historically? Additionally, I have logging - every option - for a rule enabled, I see no logs. I'm trying to troubleshoot why a rule isn't firing as of 3 days ago with no changes to my network or Hubitat overall. Should be easy, I'm struggling.

2

Seemingly, since yesterday, the exact rule (no change) no longer works. If I click "run actions", it doesn't fire. Odd. Not sure how to troubleshoot.

Basically if:

  1. Motion Sensor A is active and
  2. Door A is closed
  3. Send an HTTP GET command.

It isn't sending.

3

I see it in "Logs", maybe it is working. Blue Iris suddenly isn't "Getting" it:

app:9292021-12-10 02:58:19.862 pm infoAction: END-IF

app:9292021-12-10 02:58:19.857 pm infoAction: Send GET to: http://192.168.1.27:8181/admin?camera=FPT&trigger&user=admin&pw=

app:9292021-12-10 02:58:19.854 pm infoAction: IF (Front Door Sensor closed(T) [TRUE]) THEN

4

I'm waiting eagerly for the next installment... it's getting very exciting. :smiley:
If you didn't have 20 years, I'd say something foolish like Paste the GET into your browser (OR curl) but...

2 Likes
5

Yup, had already tried calling the same get command manually, and it fires. I know the command works & causes the BI trigger. I know that Hubitat's status on both of the dependencies are firing. But for some reason, nothing is working as of 8 this morning. (started working sporadically instead of consistently 3 days ago, now not working at all)

image
image1840×525 287 KB

6

I apologize as i had a few too many at my work Christmas party. My logs show details, but "events" within the rule do not. I'd expect them to, maybe I'm wrong there.

The rule fires if I call a GET command by other means, but not if it fires thru Hubitat. Very odd.

7

Citing your expertise initially was a little off putting, but with this phrase you have won back my heart.

Is it possible that while your browser can reach your camera, your Hubitat cannot? Such as different VLANs?

8

I can appreciate that my initial statement was offputting, I wasn't trying to be cocky, and I admit I know FAR from everthing (rather, it's more the opposite), just trying to eliminate that it wasn't a simple issue and that I've already tried the basic steps that I should have. I've tried troubleshooting extensively before reaching out for help.

I don't use multiple VLANs, so that can't be it. It's quite odd. I've rebooted the hub & the BI server. Checked the recent activity of both sensors invovled in the rule, they check out. Checked out BI's ability to accept GET requests, that checks out. Nothing here makes sense to me and I'm not sure how to further troubleshoot.

The rule says, algorithmatically, "If the motion sensor changes to active, and the door is closed, send a GET". Hubitat says it sends the GET. BI doesn't get the GET.

If I manually fire the GET, it works (BI receives the GET). So BI can receive GETs. Not sure what else to do to troubleshoot.

9

How about sending the get to a server running TCPDump and capture it to evaluate the Headers. You've tried all the easy stuff :smiley: I can suggest this because I have all that equipment sitting here.