@bravenel Suddenly (after upgrading to .138 anyway), I started getting tons of these errors--on vast numbers of my RM 5.1 apps.
Some seemed to be helped by going into the rule and doing an "update rule" and running it...but that isn't fixing all of them. I have another that just won't run at all.
Not sure it it is related--but my hub was really wonky this morning until I rebooted it about 8:20 this morning. Here is a filtered list of the errors (more of the ones above plus other ones):
I am on Hub Info v2.7.10, the current version of Hub Info is v2.7.11 (the fix for the 0.0.1 upgrade is: 2.7.11 - additional 408 processing). So, I'd say, NOT fixed long ago since I'm on a version that is only a few days old. Still, the upgrade to that came out yesterday I believe--so I just upgraded it.
App 1300 is a pure RM 5.1 Rule that isn't running when it is triggered. I have no clue what update you are suggesting I look for, since I'm on the very latest version of the hub.
I wrote my own weather device driver. It doesn't appear to be the device blowing up--it's the RM Rule that won't run.
As I explained, I had those errors showing up last night for 5-10 of my RM 5.1 apps...they were ALL refusing to execute, with the same error.
For the "weather" one above, the device driver was working and creating the "trigger" event, but the RM App was blowing up before it could even start. Thus, it wasn't even getting into the rule to mess with my device driver.
The attribute exception for the Hub Info device is generally due to the hub returning a web page instead of the endpoint data requested - normally this only occurs when the hub is restarting.