Homey

Use this guide to connect Navet to Homey in standalone mode. The same OAuth client settings can enable Homey as an additional provider in the Home Assistant App.

Overview

Navet uses the Homey cloud OAuth flow. You run Navet yourself, configure an Athom Web API client, and sign in through the provider picker.

When To Choose This Path

Choose this path when:

• you want Navet in standalone mode
• you use Homey as the provider
• you are comfortable creating an Athom Web API client

Prerequisites

You need:

• a Homey Cloud app or client from Athom
• the generated client ID and client secret for that app

Start here:

• Homey Developer Tools
• Homey Web API documentation

Setup Steps

1. Create the Homey API client

1. Sign in to the Homey Developer Tools with the Athom account you want to use for Navet.
2. Create a new Web API client.
3. Set the client name to something recognizable such as Navet.
4. Set the redirect URL to the exact Navet callback URL that should receive the OAuth callback. Example: http://localhost:8080/__navet_homey__/callback for local Docker, https://navet.example.com/__navet_homey__/callback for a hosted deployment.
5. Save the client.
6. Copy the generated client ID and client secret.

2. Configure Navet

Use this docker-compose.yaml:

services:
  navet:
    image: ghcr.io/awesomestvi/navet:latest
    container_name: navet
    restart: unless-stopped
    ports:
      - "8080:80"
    volumes:
      - navet-data:/data
    environment:
      NAVET_HOMEY_CLIENT_ID: your-athom-client-id
      NAVET_HOMEY_CLIENT_SECRET: your-athom-client-secret
      # Optional: set this only if Navet cannot infer the public callback URL correctly.
      NAVET_HOMEY_REDIRECT_URI: https://your-navet-url.example.com/__navet_homey__/callback

volumes:
  navet-data:

Set NAVET_HOMEY_REDIRECT_URI only when Navet cannot infer the public callback URL correctly, such as when Navet sits behind a reverse proxy or the public callback URL differs from the browser origin users open. Navet also supports a custom callback path if you register a different exact URL with Athom, such as https://navet.example.com/callback.

3. Start Navet

docker compose up -d

Open Navet and choose Homey, or choose Connect under Homey in Settings -> System to add it to an existing dashboard. Sign in with your Athom account.

4. Sign in

1. Open Navet.
2. Choose Homey on the provider screen.
3. Continue to Athom sign-in.
4. Return to Navet after the OAuth redirect.
5. If your Athom account has more than one Homey, choose the one this dashboard should use.

What To Expect

• Navet stores the Homey session through same-origin runtime endpoints in the Navet app.
• Homey devices and zones load after sign-in.
• Homey contributes rooms, lights, switches, fans, sensors, locks, covers, thermostats, speakers, people, and notifications to Navet.
• Lock cards show the device’s locked or unlocked state. Lock and unlock actions use Homey’s writable locked capability.
• Blinds, curtains, and sunshades use cover cards. Devices with a writable position capability support percentage adjustments and open/close actions. Movement-only devices offer their supported open, close, and stop controls. Stop is enabled only when Homey exposes that command; tilt controls are unavailable through this adapter.
• Thermostat cards show target and current temperatures, follow the device’s temperature range, and support target changes and available operating modes. Speakers provide playback, volume, mute, and other controls when Homey exposes writable capabilities. Media browsing and speaker grouping are not available through this adapter.
• Manually runnable Flows and Advanced Flows, along with Moods, are available as scene cards.
• Insights can show the last 24 hours, 7 days, or 31 days. Device sensor history is available when Homey exposes a matching Insights log. See Energy readings for dashboard coverage.
• Hiding a Homey notification in Navet leaves the notification in Homey. App updates and hub restarts remain managed in Homey.
• Availability depends on your Homey version and the permissions granted to the OAuth client.
• Dedicated camera, calendar, weather, Assist, task, and provider room administration services are not registered for Homey.
• In a standalone installation, Homey can stay connected alongside Home Assistant or openHAB; selected providers are combined in shared dashboard collections.
• If you sign out from Navet, the stored Homey session is cleared from the Navet side.

Scenes and flows

Homey Moods and manually triggerable Flows, including Advanced Flows, appear as scene shortcuts in Lights and under Household → Routines → Quick actions. Select a shortcut or its Run button to activate its Mood or run its Flow through Homey. Disabled Flows are not offered as shortcuts.

Energy readings

Homey devices with power or electricity meters appear in Energy alongside devices from other connected providers. Power and energy readings from the same Homey device share a device row. Current power uses the live reading; today’s electricity consumption uses recorded changes in a matching Insights meter log. A lifetime meter total is not treated as today’s consumption.

Whole-home, grid, and solar totals use their configured sources. Navet does not add individual device readings to a household meter, since those readings can overlap. Homey Insights do not provide the dashboard’s aggregate statistics or whole-home source configuration.

Security readings

Homey contact, motion, occupancy, presence, smoke, carbon monoxide, gas, water leak, heat, tamper, vibration, sound, and battery alarms appear automatically in Security. Battery levels are included in system health, with low levels marked for attention. Other Homey alarm capabilities appear as problem readings. Sensors you hide stay hidden. Missing readings and unavailable devices are shown as unknown rather than clear.

Recent activity includes recorded changes for entities with Homey Insights history. Current activity stays visible when an entity has no recorded history.

Troubleshooting

• If the Homey option does not appear on the login screen, check that NAVET_HOMEY_CLIENT_ID and NAVET_HOMEY_CLIENT_SECRET are set in the running Navet container.
• If sign-in returns to the wrong URL, set NAVET_HOMEY_REDIRECT_URI to the exact callback URL registered in your Athom Web API client.
• If Navet keeps asking you to choose a Homey again, confirm the selected Homey is still available to the signed-in Athom account.