Please advise regarding the error below:
Have you checked the Events for the sensors involved around the time of the error log? To see both which one, if any, changed and to what value?
Also, do you see the error message often? Basically, does it line up with any of the sensor devices changing state.
Finally, Have you confirmed that the error log is actually coming from the app (rule) you have posted?
Thanks for your reply.
Yes, the events or logs show that the error times line up with one of the sensor changing state - the sonoff sensor.
I have seen these errors before, but there seems to be more today.
I presume that the error log is coming from the rule as when I click on the error then it takes me to the app rule?
That is expected... I wouldn't read too much more into that than that is where the error occurs (still a valuable feature of the logs page... ), but it doesn't mean the app is producing the error, if you get my drift...
1 Like
So by this, you mean the Bathroom sensor? And when other sensors change stage, the error does not occur?
Are you using a system driver or a custom one?
It seems like one of your devices in that rule is sometimes posting a "null" value for the Humidity, which is causing the error. You can see in the error message it is having a problem with a null value.
2 Likes
Yes, using custom driver for the bathroom (sonoff sensor) and both Hallway and Living room are switchbot sensors which are integrated in HE via Home Assistant / Home Assistant Device Bridge.
However, I can now see that the recent errors are in line with all three sensors... so, it's not likely to be sensor related?
@bravenel any hints as to what this error above might be about? Line 9525 of RM apparently.
1 Like
I'm looking into it.
2 Likes
Please turn on all logging in this rule, so you can see the app logs for it, and post a screenshot of that here. It's not possible with what you've shown to see what is the source of this error. I am not able to reproduce it, but I'm just guessing at the sequence of events.
I will continue to look into this, but it is perplexing as I'm not able to reproduce it.
1 Like
Can you switch to a stock driver and see if that changes anything?
1 Like
Sure, will do.
FYI - please note that the error was occurring all day yesterday, and there were several errors every hour.
However, the error occurred one last time @17.07 shortly after the hub started with new software version 2.3.7.126, and has not occurred since then.
Also, I had two identical rules triggered on different humidity ranges for two different switches and same sensors, but for some reason only the dy mode rule was affected. Anyway, this was a strange issue and I guess I can’t explore any further now. Thanks
Nice. Perhaps it's fixed.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
