C-7 hub runs 188.8.131.52 @bravenel
Once in while "Wait for Expression" is missing when Expression become true and
instead waits for Timeout to expire.
Here is a rule:
Here is time stamps for the "Home Arrival Sensor"
And here is a log for the rule:
The problem is : Home Arrival Sensor reported presence at 2022-06-16 07:22:34.639 PM EDT
2022-06-16 07:22:34.724 Action: Wait for Expression: Home Arrival Sensor present(F) [FALSE] --> timeout: 0:00:45
is missing the true state of expression and instead executes Timeout .
Is this a race condition due to very close timing?
I have all their new while loops very buggy, it often take hours not minutes to get it to code proper, I shoot videos so I have this evidence,
The OP’s rule screenshot doesn’t show a while loop. Your post is off topic. If you believe you have discovered a bug, please create a new thread and share your evidence.
Point taken, the Hub Mesh interface has been completely reworked and the documentation has not been updated accordingly. It is in the works, though so the new document will be made public soon. Thanks for pointing this out.
I look forward to it. Reverting one to 2.3.1 did expose the ability to make devices available to the other hub, this is my hack, for now.
But how about addressing my original question?