[Solved]. Snipe hunting a missing entity
-
I'm getting these two alerts regarding an entity that cannot be found. Entirely possible as I cut some fat out of my Hubitat last week.
I've confirmed in MSR that entity
hubitat>161doesn't exist, again, totally fine.My issue is trying to find the two rules impacted here. I seem to recall in past builds of MSR that there was a yellow triangle next to a ruleset if it had an issue like this but I've gone thru every ruleset and don't see this.
Is there a means by which I can search by
rule-kohw6jf2?*Hubitat C-7 2.4.3.123
*Proxmox VE v8, Beelink MiniPC 12GBs, SSD*HASS 2025.9.4
w/ ZST10-700 fw 7.18.3*Prod MSR in docker/portainer
MSR: latest-25264-2fbe9217
MQTTController: 25139
ZWave Controller: 25139 -
I'm getting these two alerts regarding an entity that cannot be found. Entirely possible as I cut some fat out of my Hubitat last week.
I've confirmed in MSR that entity
hubitat>161doesn't exist, again, totally fine.My issue is trying to find the two rules impacted here. I seem to recall in past builds of MSR that there was a yellow triangle next to a ruleset if it had an issue like this but I've gone thru every ruleset and don't see this.
Is there a means by which I can search by
rule-kohw6jf2? -
As @wmarcolin said, it's giving you the name of the rule, so it should be easy to find by name, rather than by ID. And the
<SET>indication means it's in the SET reaction (and also RESET, apparently) of that rule (that's also the meaning of:Sand:Ron the rule IDs). -
In theory the rule that is using this device is Garage Door, search for it and you will certainly have this device within your process. The yellow triangle shows that the trigger has an error. Can you send a screen shot of this Garage Door rule?
@wmarcolin I'm right with that theory... except I don't have a
Reactionorrulesetnamed "Garage Door". I looked at any rules related to the garage door, especially those that happened at or near the time noted in the error.
None of those ruleIDs match, however.
-
Found it - it was a notification ruleset, well buried.
Confirming, there's no indicator if the error is in the
<SET><RESET>portion of a ruleset, just a trigger?*Hubitat C-7 2.4.3.123
*Proxmox VE v8, Beelink MiniPC 12GBs, SSD*HASS 2025.9.4
w/ ZST10-700 fw 7.18.3*Prod MSR in docker/portainer
MSR: latest-25264-2fbe9217
MQTTController: 25139
ZWave Controller: 25139 -
Found it - it was a notification ruleset, well buried.
Confirming, there's no indicator if the error is in the
<SET><RESET>portion of a ruleset, just a trigger? -
The error you showed is in SET and RESET, you must be using this device that does not exist hubitat>161 in both.
Can you send me a printout of the rule you found in the ruleset? Edit it and show how the configuration looks like.
Even though the Echo's are using "Announce All" you have to choose ONE as the entity. Seems the one I'd chosen here was one of the ones I've downsized from my account.
-
T toggledbits locked this topic on