Rule Machine app runtime error

At least one of my automations is having runtime issues:


I do see that when the required expression was to become true at 7:00am there was an "Event: null null null" message logged.
My workaround is to open that particular RM app and click on Done. That seems to restart the app and things work again (until they don't). This has happened at least once before on this app. Is this a Tempest Weatherflow Station driver issue?

This would be easier to answer with a link to the particular driver you are using (assuming it is custom code) as well as a description or screenshot of your entire rule (plus the logs you've already provided). Would you be able to provide that information?

Here is the header for the driver code I'm using:
/**

  • WeatherFlow Lite driver for Hubitat
  • Copyright (c) 2019 Justin Walker
  • Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
  • The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
  • THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
  • v1.0.0 - initial version (2020-07-06)
  • v1.0.1 - added strikeDistance (2020-07-08)
  • v1.0.2 - initialize strike attrs (2020-07-09)
  • v1.0.3 - added health check (2020-07-13)
  • v1.0.4 - added support for publish rate, reducing resolution, and precipication rate (2020-08-01)
  • v1.0.5 - bug fixes (2020-08-02)
  • v1.0.6 - added null handling and battery status (2020-08-23)
  • v1.0.7 - added water sensor capability
  • v1.0.8 - added dewpoint calculations, cleanups, fixes for parsing errors (2022-09-20, @imnotbob)
  • v1.0.9 - Fix for api key error (2023-03-03)

*/

Here's the rule screenshot:

Hoping this is what you're after. Perhaps I can see if there's a newer version of the driver code.

Can you please provide a link? The comments at the top do not provide enough information (and while searching is possible, there is often going to be more than one promising result, and only you know exactly what you have installed on your hub). Thanks!

I think this is the link. I had to search for it. Too bad it wasn't in the header.

How did you get the code originally? :thinking:

In any case, going back to the original issue:

I'm not seeing any cludes with the windoSpeed attribute in this driver (it appears to be a number, not a string--one guess I'd have otherwise), assuming this is indeed the code.

The "null null null" thing is a bit odd, like maybe you had a trigger event for a device that was removed or something (though a "Done" should fix that). Re-creating the rule might help if nothing else, or at least removing and re-creating all your triggers, depending on how drastic you want to start with. :slight_smile: