Skip to content
System One

Jev on robots, drones and smart-home devices: 15 projects

Hardware projects need a controller that picks the next action from the current state: move the arm, steer the drone, switch the light. A decision model suits the choosing step. It takes the state as structured text and returns a typed choice with a confidence value, which a safe controller can bound and check before anything moves. The examples in this hub run on Jev and other decision models, and Laya appears in several. Most run in simulation. Examples include jev-drone by RomanSlack in MuJoCo, kxzk/typesafe-jev-drone-demo, and TarunTomar122/jev-askable-arm for a simulated Franka Panda arm. Smart-home entries are different: allenporter/home-assistant-typesafe and AboveColin/HA-Jev work with real Home Assistant setups. Before you copy one, check whether it has run on hardware at all, what hard limits sit outside the model, and what the device does when the model is unsure. Simulation results say little about a real device, so weigh each entry by how close it is to hardware. Safety limits belong in code you control.

15 entries

All entries

Showing 15 of 15

How decision models are used for robots and devices

The loop is: read the sensors, turn them into a compact state, ask the model for the next bounded action, and run it through a safety layer. lykycy123/RoboJEV uses two stages: Jev picks an intent, then picks motion and a gripper command. TarunTomar122/jev-askable-arm has Jev pick one of about 30 hardcoded primitives per step. The safety layer should reject any action outside set bounds.

Smart homes use choice for intent and score or noul for conditions. Laya for Home Assistant by allenporter scores registered intents and exposed entities with Laya in one forward pass. luxus/ha-conversation-jev lets Jev handle simple light actions and hands anything else to Grok, gated by confidence. Keep the list of devices and intents the model can see short, since it can only pick among what it is shown.

Loop rate is the limit. The drone entry runs Jev in its control loop at 2.5 Hz, which suits slow, high-level choices and not low-level motor control. Keep fast control in ordinary code and let the decision model pick goals or targets. Several entries also run the model less often than the control loop, passing it a summary of the state. Test in simulation first, and add a hard stop that does not depend on the model.

FAQ

Can Jev control a robot arm or drone?

In simulation, yes. Entries here have Jev picking the next bounded action for a Franka Panda arm in MuJoCo and ManiSkill and for a drone. Real hardware needs a safety layer outside the model, and few entries show it.

Can Jev control a smart home?

Yes. AboveColin/HA-Jev and allenporter/home-assistant-typesafe connect it to Home Assistant, and luxus/ha-conversation-jev uses it to classify spoken commands. Laya for Home Assistant runs fully local.