Feedback: visual rules with AI

I've been experimenting with the visual rules using AI. I like it a lot. I made a rule pretty quickly. Just lounging around, and it worked right out of the box. This is the first time I'm using visual rules with the AI. When I looked at it that way back then, it was fundamental, but now I can see the potential in this newer release with AI.
I do have some suggestions:

  • I generally keep my rules names short with the naming convention, so I would like descriptions if possible.
  • potentially even descriptions through the flow to help you with your thought process. The descriptions do not have to be automated.
  • Debugging log capability would be excellent. Reality and AI are sometimes different.
  • And something like a virtual panel with the devices that you enlisted to see as you step through it. Did you provide AI with all the correct information?
  • And I'm sure this one's been asked many times. Is there a way to integrate rule machines, rules, and web core? That would be a game-changer for me, allowing me to perform additional tweaking and optimization of rules and policies.
  • And instead of creating rules, would there be a way to look at your rules and see where optimizations can occur so duplicate task actions aren't taking place, potentially at the same time with different rules. Or maybe setting up global variables, which I don't really use, and setting the variable per rule to ensure I get what I want for that particular rule.
    Please understand. I love the application and keep up the great work. I'm just exploring where this could potentially take us (the community) and how we can further enhance the product. Keep up the great work!

What gem and amazing addition! The AI worked well even for reasonably complex rules - the prompt I threw at it, multiple triggers, a branch, a wait, a notification, cross-rule calls, it got right on the first try.

I also wrote a test decoder for VBR for my Automation Map App (in the current dev version) and it was a lot easier than with Rule Engine because VBR stores an explicit node/edge graph rather than the more complex Rule Machine's format.

Test VBR rule (bottom) decoded directly from JSON into Automation Map (top)

I don’t know how relative this is to your post, but I’ve never paid attention to visual rules. In fact, I find rule machine difficult in addition to that I’ve begun exploring Home Assistant and it’s new AI via the opencode app. I have also been using ChatGPT to help with some of my smart home stuff, In asking some questions today,I realized that there is a way to connect the open code app in HA to Hubitat MCP and be able to have it examine things in Hubitat. So far it looks like it’s going to be an interesting exploration. If I only knew what I was really doing, it would be maybe more fun, but I’ll figure it out.