Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation.

About

Homey 2.x is an integration that connects a Homey hub to Home Assistant and brings its devices in as native entities. Devices are discovered automatically and appear as lights, switches, sensors, covers, climate, fans, locks, media players, scenes, buttons, numbers and selects. Homey Flows can be triggered, enabled and disabled from Home Assistant, and Homey logic variables are imported as number, switch and text entities. It talks to the hub locally, uses Homey rooms to organize devices into areas, and follows device changes such as renames and deletions. Updates arrive over Socket.IO, with polling as a fallback, and a guided assistant can migrate from the older 1.x integration while keeping entity IDs. It needs a Homey Pro 2023 or later and an API key, and it is added through the Home Assistant UI.

Automatic summary of the README and code of ifMike/homeyHASS. Something wrong, or are you the maintainer and want your own text here? Get in touch

Supports

  • Works locally Talks to your devices on your own network. No vendor cloud in between.

  • Found by itself Home Assistant spots it on the network and offers to add it.

  • From the Marketplace Installed through the Marketplace, formerly HACS.

  • Actively maintained Its author released or pushed a change in the last six months.

Provides

  • Lights
  • Climate
  • Fans
  • Covers
  • Locks
  • Media
  • Vacuums
  • Switches
  • Sensors

Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

Connect to Homey

  • Homey IP Address or Hostname
  • API Key

Also asked when confirming the device and signing in again.

Confirm migration

  • Keep my entity IDs (recommended — preserves dashboards and automations)
  • Remove the old Homey 1.x integration when done

Upgrade from Homey 1.x

  • What would you like to do?

Select Homey 1.x hub

  • Homey 1.x integration

After setup

  • Homey IP Address or Hostname
  • API Key (leave blank to keep current)
  • Fallback polling interval (seconds)
  • Recovery cooldown (seconds, between auto-recovery attempts)
  • Expose string capabilities as editable text inputs (disables read-only)
  • Expose string capabilities as read-only sensors (default, off when editable is enabled)
  • Use Homey capability titles for entity names
  • Devices
  • Homey 1.x integration
  • Keep my entity IDs (recommended)
  • Remove the old Homey 1.x integration when done

Texts from the code of ifMike/homeyHASS.

From the README

  • Automatic device discovery from your Homey hub
  • Lights, switches, sensors, binary sensors, covers, climate, fans, locks, media players, scenes, buttons, numbers, and selects
  • Full light control: dimming, color (HS), and color temperature
  • Sensor types: temperature, humidity, pressure, power, voltage, current, luminance, CO2, CO, noise, rain, wind, UV, PM2.5/PM10, VOC, AQI, frequency, gas, soil moisture/temperature, energy
  • Security sensors: motion, contact, tamper, smoke, CO alarm, CO2 alarm, water leak, battery, gas, fire, panic, burglar, vibration
From the README of ifMike/homeyHASS, MIT License. Shortened.

Shows in Vulpo

Light card, Quick Toggle card, Cover card, Climate card, Apple Watch, Control Center, Climate Live Activity, Vacuum Live Activity.

Information

Installs
186 sharing analytics
GitHub stars
11
Connection
Works locally
Upkeep
Updated in the last 6 months
Version
v2.1.4,
Category
Hubs and protocols, Smart home hubs
Kind
Marketplace integration
Needs
Needs the Marketplace (HACS on 2026.10 and older)
Domain
homey_hass

You might also like

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. About these numbers