Phare Protect for Home Assistant.

1 Before you start

You need:

• A Phare C1, C1 Core or C1 Pro set up in the Phare Protect app, in a home you own or that is shared with you.
• The Phare Protect app, version 1.2.0 or later, to create the token Home Assistant signs in with.
• Home Assistant 2025.1 or later, connected to the internet. If you don't run it yet, step 2 covers the options.

The integration talks to the Phare cloud over HTTPS. It does not connect to your alarms over your home network, so Home Assistant and your Phare devices don't need to be on the same Wi-Fi, or even in the same building.

2 Install Home Assistant

Already running Home Assistant? Check its version under Settings → About and skip to step 3. If you are not sure how it was installed, Settings → System → Repairs → ⋮ → System information shows the Installation type; step 3 asks for it.

New to Home Assistant? Pick the setup that suits you. The Phare integration works the same on all of them.

docker run -d \
  --name homeassistant \
  --restart unless-stopped \
  --network host \
  -e TZ=Europe/London \
  -v "$HOME/homeassistant:/config" \
  ghcr.io/home-assistant/home-assistant:stable

docker run -d \
  --name homeassistant \
  --restart unless-stopped \
  -p 8123:8123 \
  -e TZ=Europe/London \
  -v "$HOME/homeassistant:/config" \
  ghcr.io/home-assistant/home-assistant:stable

services:
  homeassistant:
    container_name: homeassistant
    image: ghcr.io/home-assistant/home-assistant:stable
    restart: unless-stopped
    network_mode: host
    environment:
      TZ: Europe/London
    volumes:
      - ./homeassistant:/config

3 Get the integration

Phare Protect is published on GitHub as pharelabs/phare-home-assistant. How you add it depends on your Home Assistant version.

docker exec -it homeassistant bash -c "wget -O - https://get.hacs.xyz | bash -"

wget -O - https://get.hacs.xyz | bash -

4 Create a token in the Phare Protect app

Home Assistant signs in with a personal access token, not your password. You create and revoke tokens yourself in the app.

1. In the Phare Protect app, go to Settings → API tokens and tap Create token.
2. Give it a name you will recognise, such as Home Assistant.
3. Under What may it do?, choose a scope (see below).
4. Leave Expiry date empty, or pick a date if you want the token to stop on its own.
5. Create it and copy the token, which starts with phare_pat_. It is shown once. Keep it somewhere safe, such as a password manager, until you have pasted it into Home Assistant.

Treat a Read and control token like a password: anyone who has it can arm, silence and change your devices. A token stops working after 90 days without use (Home Assistant uses it every minute, so this only happens if it stays off), or on the expiry date you chose. You can revoke it at any time: tap it in Settings → API tokens.

Use a separate token for each Home Assistant installation or script, so you can revoke one without breaking the others.

5 Connect your account

1. In Home Assistant, go to Settings → Devices & services → Add integration and search for Phare Protect.
2. Paste the token into Personal access token. Leave API base URL as it is.
3. Select Submit.

Add Phare Protect to my Home Assistant

Within a minute, each Phare alarm appears as a device in the area of its room (Kitchen, or Kitchen (Flat 1) if you have several homes), and each home appears as a device of its own holding the home-wide controls. Readings match the app within a minute.

Have more than one Phare account? Add the integration again with a token from the other account. Each account is one entry.

6 Faster alerts Optional

Out of the box, Home Assistant asks Phare for news once a minute, so an alarm shows up within about a minute. If Phare can reach your Home Assistant from the internet over HTTPS, it pushes each alert instead, and it arrives within seconds. The once-a-minute check keeps running as a safety net, so a missed push still shows up.

Push needs a Read and control token, because setting it up registers the address with your Phare account. Readings are always fetched once a minute: alarms on Wi-Fi publish every 60 seconds and on cellular (LTE-M) every 5 minutes, so asking more often would not show anything new.

Check that it works

If push could not be set up, the log says why, once, in a line starting Phare alerts arrive by polling. Look for it under Settings → System → Logs. No such line after a reload means push is on.

Every push is signed by Phare and checked before it is used: a forged or replayed one is dropped and logged. Removing the integration tells Phare to stop sending.

7 What you get

Each entity appears only when your device has the sensor or feature behind it.

On each Phare alarm

On each home

The integration's texts are in English, Catalan, Spanish and French, following your Home Assistant language.

8 Automation ideas

To use one: Settings → Automations & scenes → Create automation → Create new automation, then ⋮ → Edit in YAML, paste, and save. Replace the entity IDs with yours: find them under Settings → Devices & services → Entities (search for smoke, movement and so on), or switch back to the visual editor and pick them from the lists.

Smoke or CO: light the way out

Turns every light on full, unlocks the front door and sends a critical notification that sounds even when the phone is on silent (iPhone). Only unlock the door if that suits your home.

alias: Phare – smoke or CO, light the way out
mode: single
triggers:
  - trigger: state
    entity_id:
      - binary_sensor.kitchen_smoke_alarm
      - binary_sensor.hallway_smoke_alarm
      - binary_sensor.kitchen_carbon_monoxide_alarm
    to: "on"
actions:
  - action: light.turn_on
    target:
      entity_id: all
    data:
      brightness_pct: 100
  - action: lock.unlock
    target:
      entity_id: lock.front_door
  - action: notify.mobile_app_your_phone
    data:
      title: Phare alarm
      message: "{{ trigger.to_state.name }}"
      data:
        push:
          sound:
            name: default
            critical: 1
            volume: 1.0

Carbon monoxide: stop the boiler and ventilate

alias: Phare – CO, stop the boiler
mode: single
triggers:
  - trigger: state
    entity_id: binary_sensor.kitchen_carbon_monoxide_alarm
    to: "on"
actions:
  - action: climate.set_hvac_mode
    target:
      entity_id: climate.boiler
    data:
      hvac_mode: "off"
  - action: fan.turn_on
    target:
      entity_id: fan.extractor

Arm the break-in alarm when everyone leaves

Uses the people Home Assistant tracks with the Companion app. Needs a Read and control token and a C1 Pro.

alias: Phare – arm when everyone leaves
mode: single
triggers:
  - trigger: numeric_state
    entity_id: zone.home
    below: 1
    for:
      minutes: 5
actions:
  - action: alarm_control_panel.alarm_arm_away
    target:
      entity_id: alarm_control_panel.home_break_in_alarm

And the other way round:

alias: Phare – disarm when someone gets home
mode: single
triggers:
  - trigger: numeric_state
    entity_id: zone.home
    above: 0
actions:
  - action: alarm_control_panel.alarm_disarm
    target:
      entity_id: alarm_control_panel.home_break_in_alarm

Movement while armed: lights and siren

alias: Phare – movement while armed
mode: single
triggers:
  - trigger: state
    entity_id: binary_sensor.living_room_movement
    to: "on"
conditions:
  - condition: state
    entity_id: alarm_control_panel.home_break_in_alarm
    state: armed_away
actions:
  - action: light.turn_on
    target:
      entity_id: all
  - action: siren.turn_on
    target:
      entity_id: siren.outdoor

Tell me when a device needs attention

Offline for 15 minutes, mains power lost, low battery or a fault.

alias: Phare – device needs attention
mode: queued
triggers:
  - trigger: state
    entity_id: binary_sensor.kitchen_connectivity
    to: "off"
    for:
      minutes: 15
  - trigger: state
    entity_id:
      - binary_sensor.kitchen_mains_power
      - binary_sensor.kitchen_battery
      - binary_sensor.kitchen_device_health
    to: "on"
actions:
  - action: notify.mobile_app_your_phone
    data:
      title: Phare
      message: "Check {{ trigger.to_state.name }}"

Humidity out of range: run the dehumidifier

alias: Phare – humidity, dehumidifier on
mode: single
triggers:
  - trigger: state
    entity_id: binary_sensor.bathroom_humidity_alarm
    to: "on"
actions:
  - action: switch.turn_on
    target:
      entity_id: switch.dehumidifier

React to the raw alert

With pushed alerts on, each alert also fires a phare_alert event carrying its fields: type_code (fire, co, mvmt, tmp, hum, flt, pwr, bat), stage, event, name, room, device_id, space_id and ts. Useful when you want the alert's own wording.

alias: Phare – log pushed alerts
mode: queued
triggers:
  - trigger: event
    event_type: phare_alert
    event_data:
      stage: new
actions:
  - action: logbook.log
    data:
      name: Phare
      message: >-
        {{ trigger.event.data.event }} –
        {{ trigger.event.data.name }} ({{ trigger.event.data.room }})

9 Update, change or remove

Updates

New versions appear under Settings → Updates when you installed through the Marketplace or HACS. Install, then restart Home Assistant if it asks. What changed is in the release notes. Installed by hand? Repeat the manual steps with the new release.

A new token, or a different scope

When a token is revoked or expires, Home Assistant shows a re-authenticate notice under Settings → Devices & services. Create a new token in the app and paste it there. To move from Read only to Read and control (or back), create the new token, revoke the old one in the app, and paste the new one when the notice appears, within about 5 minutes. The token must belong to the same Phare account.

Diagnostics

If support asks for them: Settings → Devices & services → Phare Protect → ⋮ → Download diagnostics. The file leaves out your token, address and coordinates, and your name, email and phone.

Remove

1. Settings → Devices & services → Phare Protect → ⋮ → Delete. This also tells Phare to stop pushing alerts.
2. Remove Phare Protect from the Marketplace or HACS, or delete /config/custom_components/phare, and restart.
3. Revoke the token in the app under Settings → API tokens.

10 Troubleshooting

11 Help and feedback

• Bugs and ideas: the issue tracker on GitHub.
• Your account, your devices, or anything private: support@pharelabs.com or our contact page.
• Building something of your own? The same token works with the Phare Protect API.