Overview
FERAL integrates with your smart home through two paths: Home Assistant for broad device compatibility, and direct HUP mesh for low-latency local control of supported devices. Both paths let you control hardware via natural language.Home Assistant Integration
Ensure Home Assistant is running
FERAL connects to Home Assistant’s WebSocket API. Your HA instance must be accessible on the local network.
Create a long-lived access token
In Home Assistant, go to your profile → Long-Lived Access Tokens → Create Token. Copy the token.
Direct HUP Mesh Control
For supported devices, FERAL can bypass Home Assistant and control hardware directly over the local network or BLE using the Hardware Unified Protocol.settings.json
Supported Device Types
| Category | Devices | Actions |
|---|---|---|
| Lights | Philips Hue, LIFX, Tasmota, any HA light | On/off, brightness, color, color temp, scenes |
| Thermostat | Nest, Ecobee, any HA climate | Set temp, mode (heat/cool/auto), fan |
| Locks | August, Yale, any HA lock | Lock, unlock, status check |
| Appliances | Smart plugs, switches | On/off, power monitoring |
| Media | TVs, speakers, any HA media_player | Play, pause, volume, source selection |
| Sensors | Motion, door/window, temperature, humidity | Read-only monitoring and triggers |
Natural Language Control
Once connected, you can control devices through conversation:Scenes and Automations
Define custom scenes in your settings that FERAL can trigger by name:settings.json
Proactive Smart Home
With the proactive engine enabled, FERAL can act on smart-home devices automatically:- Sleep detected (from wristband) → dim lights, lock doors, lower thermostat
- Heart rate spike during rest → adjust lighting to calming colors
- Calendar: meeting in 5 min → mute media players
- Leaving home (geofence exit) → turn off lights, lock all doors
Proactive smart-home actions respect your autonomy level. In strict mode, you’ll get an approval card before any action executes.
Troubleshooting
Home Assistant connection refused
Home Assistant connection refused
Verify the URL and token. Ensure HA is running and the API is accessible:
curl -H "Authorization: Bearer YOUR_TOKEN" http://HA_IP:8123/api/.Device not found
Device not found
Run
feral hardware list to refresh. If using HA, make sure the device is exposed and not hidden in the HA UI.Commands execute with delay
Commands execute with delay
If latency exceeds 500ms, consider switching to direct HUP mesh control for supported devices.
