Predictika · smart-home automation plans: hubs, radios, bridges, offline use and safety

An AI home assistant's automation plan, checked before it is created

An AI home assistant prepares a smart-home automation plan (“when this device does X, do Y”) for a fictional homeowner. Before it is created, the assistant sends it to Predictika’s validator, which checks it against the hub, device and safety rules, compares the device count the assistant states with the one it computes, and returns a verdict with every reason.

Scope: Automation plans for Apple Home, Google Home, Alexa, SmartThings and Home Assistant hubs. See everything this validator covers

This validator models smart-home automation plans on five hub types. It handles any combination of hub, trigger device, action device, command and offline requirement among the modeled devices, not just the scenarios shown below.

  • Reachability — whether the chosen hub can control the trigger and action devices: a native integration or Matter, plus the Thread, Zigbee or Z-Wave radio or the brand bridge the device needs.
  • Command and safety policy — commands checked against what the target accepts, and a policy that a sensor or camera never unlocks a door on its own.
  • Offline and cloud dependence — automations that must work with the internet down against cloud-only devices and hubs that run automations in the cloud; camera and lock automations that depend on vendor clouds need approval.
  • Hub capacity and the stated count — the hub device limit once the new devices are added, and a check that the device count the agent states matches the computed count.

It does not cover device purchase or pricing, energy-usage automations, or hubs and devices outside the modeled catalog. Compatibility data are illustrative estimates built from public product information, not any vendor's.

The AI home assistantBuilds the automation plan from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

9 scenarios in 4 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI home assistant says

Proposing agent: AI home assistant (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where a typical hub app gets it wrong
Click to expand
    
Our assessment of what a typical smart-home hub app does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical hub appPredictika
Compatible is not the same as workingOnly with workarounds
A catalog flag says "works with" an ecosystem; whether it works in this home depends on the hub radio, a bridge and Matter support together.		Reachability is derived from the hub, the device, the bridge and the ecosystem on every call.
One hub swap that changes many checksOnly with care
Changing the hub changes the radios, the ecosystem, where automations run and the device limit at once, so each check is a separate rule and a person meets them one at a time.		The hub is one field of the request; every check that reads it is made together on every call.
Safety policy across every lock and sensorOnly with care
A rule that a sensor or camera never unlocks a door has to be repeated for each device type and each hub, and a new device is easy to miss.		The policy reads the kinds of the trigger and the target, so it applies to any combination in the catalog.
A count the assistant states that must match a computed oneOnly with workarounds
The hub count is existing devices plus the new ones, so a separate rule must recompute it and compare it with what the assistant said.		The stated count is a field of the request and is compared with the computed count on every call.
Every problem returned in one answerOnly with workarounds
Apps tend to check as a step is saved, so an assistant often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the plan; approval findings need a person to sign off; everything else is computed.

    
1The trigger device Ring Stick Up Cam has no Apple integration and is not Matter certified - it is not in this home at all, whatever its box says about compatibility.
2A security automation (Ring Stick Up Cam to Philips Hue bulb) that only works while the internet and vendor clouds are up.
3The action device Philips Hue bulb needs its brand bridge (HUE_BRIDGE), which this home does not have.
4A security automation (Google Nest Cam to TP-Link Kasa smart plug (non-Matter)) that only works while the internet and vendor clouds are up.
5The automation must keep working with the internet down, but the trigger Google Nest Cam works only through its vendor cloud.
6The automation must keep working with the internet down, but the action device TP-Link Kasa smart plug (non-Matter) works only through its vendor cloud.
7The automation must keep working with the internet down, but the Google Nest Hub (2nd gen) runs its automations in the cloud.
8A security automation (Ring Stick Up Cam to IKEA TRADFRI Zigbee bulb) that only works while the internet and vendor clouds are up.
9The action device Schlage Connect Z-Wave lock has no Alexa integration and is not Matter certified - it is not in this home at all, whatever its box says about compatibility.
10The action device Schlage Connect Z-Wave lock speaks ZWave, and the Amazon Echo (4th gen) has no ZWave radio.
11A security automation (Eve Motion sensor to Schlage Connect Z-Wave lock) that only works while the internet and vendor clouds are up.
12The action device Schlage Connect Z-Wave lock speaks ZWave, and the SmartThings Station has no ZWave radio.
13Policy - a sensor must never unlock Schlage Connect Z-Wave lock on its own; unlocking needs a person (app, keypad or presence with confirmation).
14Unlock is not a command a light (Nanoleaf Essentials bulb) accepts.
15A security automation (Eve Motion sensor to Aqara U200 lock (Matter over Thread)) that only works while the internet and vendor clouds are up.
16The Google Nest Hub (2nd gen) would hold 201 devices after this plan, over its limit of 200.
17The device count the agent states for the Apple HomePod mini is 100, but it already has 100 and this plan adds 2, which is 102.
18The SmartThings Station would hold 201 devices after this plan, over its limit of 200.
19A security automation (Ring Stick Up Cam to Schlage Connect Z-Wave lock) that only works while the internet and vendor clouds are up.
20Policy - a camera must never unlock Schlage Connect Z-Wave lock on its own; unlocking needs a person (app, keypad or presence with confirmation).
21Lock is not a command a plug (TP-Link Kasa smart plug (non-Matter)) accepts.
22The automation must keep working with the internet down, but the trigger Ring Stick Up Cam works only through its vendor cloud.
23The action device IKEA TRADFRI Zigbee bulb has no Apple integration and is not Matter certified - it is not in this home at all, whatever its box says about compatibility.
24The action device IKEA TRADFRI Zigbee bulb speaks Zigbee, and the Apple HomePod mini has no Zigbee radio.

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Nest Cam, Z-Wave lock, full SmartThings Station: A Nest Cam is to unlock a Schlage Z-Wave lock through a SmartThings Station that already holds 199 devices, and it must work offline

    
The agent's request. Automation for the SmartThings Station: when the Google Nest Cam detects motion, unlock the Schlage Connect Z-Wave lock. It must keep working when the internet is down. The hub already has 199 devices. I state that the hub will hold 2 devices after this plan. Ready to create.

    
Verdict: Blocked.

    
    
      
  • Trigger device not in this home. The trigger device Google Nest Cam has no SmartThings integration and is not Matter certified - it is not in this home at all, whatever its box says about compatibility.
    • 
      
  • Action device needs a radio the hub lacks. The action device Schlage Connect Z-Wave lock speaks ZWave, and the SmartThings Station has no ZWave radio.
    • 
      
  • Cloud-only trigger device. The automation must keep working with the internet down, but the trigger Google Nest Cam works only through its vendor cloud.
    • 
      
  • Sensor or camera cannot unlock a door. Policy - a camera must never unlock Schlage Connect Z-Wave lock on its own; unlocking needs a person (app, keypad or presence with confirmation).
    • 
      
  • Hub device limit exceeded. The SmartThings Station would hold 201 devices after this plan, over its limit of 200.
    • 
      
  • Stated device count differs. The device count the agent states for the SmartThings Station is 2, but it already has 199 and this plan adds 2, which is 201.
    • 
    

    
2. Nest Cam, Z-Wave lock, full SmartThings Station: The agent moves the plan to a Home Assistant hub with Z-Wave

    
The agent's request. Automation for the Home Assistant Green with Thread/Zigbee and Z-Wave sticks: when the Google Nest Cam detects motion, unlock the Schlage Connect Z-Wave lock. It must keep working when the internet is down. The hub already has 199 devices. I state that the hub will hold 2 devices after this plan. Ready to create.

    
Verdict: Blocked.

    
    
      
  • Cloud-only trigger device. The automation must keep working with the internet down, but the trigger Google Nest Cam works only through its vendor cloud.
    • 
      
  • Sensor or camera cannot unlock a door. Policy - a camera must never unlock Schlage Connect Z-Wave lock on its own; unlocking needs a person (app, keypad or presence with confirmation).
    • 
      
  • Stated device count differs. The device count the agent states for the Home Assistant Green with Thread/Zigbee and Z-Wave sticks is 2, but it already has 199 and this plan adds 2, which is 201.
    • 
    

    
3. Nest Cam, Z-Wave lock, full SmartThings Station: The agent resubmits after fixing the errors

    
The agent's request. Automation for the Home Assistant Green with Thread/Zigbee and Z-Wave sticks: when the Eve Motion sensor detects motion, lock the Schlage Connect Z-Wave lock. It must keep working when the internet is down. The hub already has 199 devices. I state that the hub will hold 201 devices after this plan. Ready to create.

    
Verdict: Allowed.

    
4. A Hue bulb without its bridge: Eve Motion turns on a Philips Hue bulb on an Apple HomePod mini

    
The agent's request. Automation for the Apple HomePod mini: when the Eve Motion sensor detects motion, turn on the Philips Hue bulb. I state that the hub will hold 2 devices after this plan. Ready to create.

    
Verdict: Blocked.

    
    
      
  • Action device needs a brand bridge. The action device Philips Hue bulb needs its brand bridge (HUE_BRIDGE), which this home does not have.
    • 
    

    
5. A Hue bulb without its bridge: The agent resubmits after fixing the errors

    
The agent's request. Automation for the Apple HomePod mini: when the Eve Motion sensor detects motion, turn on the Philips Hue bulb. The home has the Hue Bridge. I state that the hub will hold 2 devices after this plan. Ready to create.

    
Verdict: Allowed.

    
6. A sensor that unlocks a door: Eve Motion unlocks a Schlage lock on a Home Assistant hub

    
The agent's request. Automation for the Home Assistant Green with Thread/Zigbee and Z-Wave sticks: when the Eve Motion sensor detects motion, unlock the Schlage Connect Z-Wave lock. I state that the hub will hold 2 devices after this plan. Ready to create.

    
Verdict: Blocked.

    
    
      
  • Sensor or camera cannot unlock a door. Policy - a sensor must never unlock Schlage Connect Z-Wave lock on its own; unlocking needs a person (app, keypad or presence with confirmation).
    • 
    

    
7. A sensor that unlocks a door: The agent resubmits after fixing the errors

    
The agent's request. Automation for the Home Assistant Green with Thread/Zigbee and Z-Wave sticks: when the Eve Motion sensor detects motion, lock the Schlage Connect Z-Wave lock. I state that the hub will hold 2 devices after this plan. Ready to create.

    
Verdict: Allowed.

    
8. The device count the agent states: An Apple HomePod mini with 100 devices gets two more, and the agent states 100

    
The agent's request. Automation for the Apple HomePod mini: when the Eve Motion sensor detects motion, turn on the Nanoleaf Essentials bulb. The hub already has 100 devices. I state that the hub will hold 100 devices after this plan. Ready to create.

    
Verdict: Blocked.

    
    
      
  • Stated device count differs. The device count the agent states for the Apple HomePod mini is 100, but it already has 100 and this plan adds 2, which is 102.
    • 
    

    
9. The device count the agent states: The agent resubmits after fixing the errors

    
The agent's request. Automation for the Apple HomePod mini: when the Eve Motion sensor detects motion, turn on the Nanoleaf Essentials bulb. The hub already has 100 devices. I state that the hub will hold 102 devices after this plan. Ready to create.

    
Verdict: Allowed.

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI home assistant prepares a smart-home automation plan (“when this device does X, do Y”) for a fictional homeowner. Before it is created, the assistant sends it to Predictika’s validator, which checks it against the hub, device and safety rules, compares the device count the assistant states with the one it computes, and returns a verdict with every reason.
    2. 
      
  2. Each tab is a different request. We will start with the first one.
    3. 
      
  3. The agent says. Automation for the SmartThings Station: when the Google Nest Cam detects motion, unlock the Schlage Connect Z-Wave lock. It must keep working when the internet is down. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with six findings, all in one answer. The trigger device Google Nest Cam has no SmartThings integration and is not Matter certified - it is not in this home at all, whatever its box says about compatibility. The action device Schlage Connect Z-Wave lock speaks ZWave, and the SmartThings Station has no ZWave radio. The automation must keep working with the internet down, but the trigger Google Nest Cam works only through its vendor cloud. The other three are on screen.
    6. 
      
  6. The validator returned six blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the configuration are checked against each other.
    7. 
      
  7. What this shows: for one hub swap that changes many checks, a hub app is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the hub to Home Assistant Green with Thread/Zigbee and Z-Wave sticks.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with three findings, all in one answer. The automation must keep working with the internet down, but the trigger Google Nest Cam works only through its vendor cloud. Policy - a camera must never unlock Schlage Connect Z-Wave lock on its own; unlocking needs a person (app, keypad or presence with confirmation). The device count the agent states for the Home Assistant Green with Thread/Zigbee and Z-Wave sticks is 2, but it already has 199 and this plan adds 2, which is 201.
    12. 
      
  12. Three findings cleared; still blocked on cloud-only trigger device, sensor or camera cannot unlock a door and stated device count differs.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the trigger device to Eve Motion sensor, the command to lock and the devices stated by the agent after this plan to 201.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. All three earlier findings are cleared.
    18. 
      
  18. Six problems caught in one call, fixed in two passes, and a clean configuration. That is the value of Predictika's validator: catching mistakes before the configuration goes live.
    19.