Is removing the “add group” trigger in the Notification MeshBot a workaround until the function is fixed again?
Or to put it another way: How do I create a Notification MeshBot for a motion sensor that is armed? I would now set “armed = true” and “motion sensor = true” as triggers. Or do I have a misconception here?
We are introducing some changes in plugin structure. We are planning to complete it next week. That’s why you are getting that error. We will announce the changes here on forum. Sorry for inconvenience.
The types of MeshBots are different. In the architecture it will be important to seperate what is an “Automation” MeshBot vs Notification vs Interaction Meshbots…
Because they will have different capabilities etc.
For example: if you want to assign a “Default Notification” to a device or device group, you will be able to select from “Notification Meshbots” vs rummaging thru Automation MeshBots and so on…
Important to separate the the types of the MeshBots.