I'd second the advice above to consider the Notifications app or HSM (the latter does a bit more than just notifications, creating an alert you'd need to clear/acknowledge in HSM, which you may or may not want). However, if you do want the extra customization a rule can provide, here are a few things I can think of:
- Not sure what would be causing that "pop()" error in your first log, but I think I've seen that before if you have a "Cancel Delayed Actions" without any cancelable delayed actions. You don't seem to have either, but if you experimented with either at some point, that could be it.
- The raw HTML in past logs is normal; they will format live but not past logs as of a recent firmware update, presumably to prevent rouge past log entries from ruining the format of the whole page (live are apparently rendered differently/more "safely")
- Your "IF (Temperature < 16)" block is unlikely to be run much of the time, as the rule will not pause until that condition is met but rather evaluate it at the moment it reaches this line. While you undoubtedly know more about how your rule is supposed to flow than me, it seems like this would then not reset your "count" variable to 0, among other things you may not want.
- I also don't see anything that will repeat the notification every 30 minutes
While you'd have to flesh out these examples a bit more to get all of what you want, if you want to continue using RM for this and get repeated notifications, I'd recommend starting by looking at one of these examples I often refer people to:
You may also be interested in the "Wait for event" action in RM, which will stop and wait for a specific event get created (i.e., attribute value to change) and then continue with the rule from that point, keeping in mind that any event that matches your trigger will start your actions over and also "cancel" the pending Wait. If you go with a rule that looks more like what you already have above, this may help.