HomeSeer
homebridge-homeseer4 · v1.0.36
Adds HomeSeer 3 and 4 devices, mostly Z-Wave, to HomeKit.
What it says it supports
Brands
- HomeSeer
- Z-Wave
Devices it names
- HomeSeer 3
- HomeSeer 4
Shows up in Apple Home as from its README
- Lights
- Outlets
- Switches
- Thermostats
- Fans
- Windows and Coverings
- Garage Door Openers
- Locks
- Security Systems
- Sensors
- Valves
Sensor readings in its code
What people report
Plugin treats devices as Z-Wave style HomeSeer devices; wiki lists supported HomeKit types, and non-Z-Wave devices need virtual device mapping. Few specific models are named.
- Works1
- Partly works2
- Requested1
The plugin’s own supported-device list
| Device | Status | What they said | Source |
|---|---|---|---|
| Google Nest Thermostat (HS4 plugin) | Works | Support added for migrated Google Nest accountsSaved copySpecifically for people that migrated their Nest accounts to Google Nest accounts. New HS4 plugin for GoogleNest uses different API number and device numbers, which prevents it from being imported correctly. Now you should be able to add the root thermostat device and it will import correctly. Been working okay for the last couple hours on my setup. Only issue is it appears the GoogleAPI has some polling limitations per minute, but for regular users it shouldn't be an issue. Excerpt saved from GitHub on 2026-10-22. | PR #188 · 2022-10 |
| HomeSeer HS-FC200 fan controller | Partly works | Needs Status Graphics page altered to work properly; untested adviceSaved copyHomeSeer Fan Controller Support This page is a work-in-progress. This advice is based on comments from other users and I have not tested further: To get the HomeSeer fan controller (HS-FC200) to work properly, you need to alter the "Status Graphics" page for the fan device to what is shown at the following links: Note, there may be a small Error in the following graphic -- It shows "On" as being set to 100, but I think the "100" entry should be deleted, and the slider range may need to be set to 1-98. Excerpt saved from GitHub on 2026-10-22. | Wiki: Fan Controller Support |
| MyQ garage door opener (HomeSeer plugin) | Partly works | Works via virtual switch and events mapping its 1/2 values to 255/0Saved copyThis plugin generally treats all devices as if they were Z-Wave devices. What this means is that it expects HomeSeer to use "standard" Z-Wave values to indicate things like "on" (Value = 255), "off" (value = 0), "Open" (value =255), "closed" (value =0), etc. If you have a device or plugin that uses different values, you can "map" it to Z-Wave using virtual devices and events. I'll illustrate this by example for a Garage Door Opener. Z-Wave and this plugin expect a Garage Door Opener to use the value of 255 to indicate "open" and the value of 0 to indicate "closed". However, I understand that … Excerpt saved from GitHub on 2026-10-22. | Wiki: Mapping HomeKit Devices to a Virtual HomeSeer Device |
| Mimo-lite relay garage door | Requested | Virtual garage door simple config PR closed unmergedSaved copyThis allows you to use a mimo-lite relay to control your garage door and use the simple config. If Homebridge-Homeseer4 see's a virtual device type under the garage door (type unknown), it will instead use "opening" and "closing" controls, in order to effectively show the garage door opening and closing in HomeKit. You will need to set up a virtual garage door device in HomeSeer, and corresponding events to control it. I also have a wireless sensor that shows when the garage door is fully open, and use the mimo-lite sensor to show when the door is fully closed, although the events can be … Excerpt saved from GitHub on 2026-10-22. | PR #182 · 2022-08 |
Gathered from the plugin’s GitHub issues, pull requests, discussions, wiki and docs, and from r/homebridge. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local
HomeSeer software interface
You’ll need
- HomeSeer 3 or 4
Compatibility
| Verified by Homebridge | No |
|---|---|
| Homebridge versions | >=1.4.1 |
| Homebridge 2.0 | No |
| Node.js | >=16.0.0 |
| Settings in Homebridge UI | Yes |
| Matter | No |
| Platform name | HomeSeer |
| License | ISC |
Community signals
| Downloads a week | 26 |
|---|---|
| Downloads a month | 70 |
| GitHub stars | 30 |
| Open issues | 2 |
| Closed issues | 109 |
| Last code push | 2023-07-02 |
| Latest version | 1.0.36 (2022-10-18) |
| First published | 2019-12-17 |
| Releases | 35 |
In ReReHome
Whatever this plugin publishes reaches Apple Home as a normal HomeKit accessory behind your Homebridge bridge, so ReReHome shows and controls it like any other.
Bridges get their own settings page listing the accessories behind them.
HomeKit services in its code
Found by scanning the published npm package. A plugin can register a service only for some devices.
- BatteryService
- CarbonDioxideSensor
- CarbonMonoxideSensor
- ContactSensor
- Fan
- Fanv2
- GarageDoorOpener
- HumiditySensor
- LeakSensor
- LightSensor
- Lightbulb
- LockManagement
- LockMechanism
- MotionSensor
- OccupancySensor
- Outlet
- SecuritySystem
- SmokeSensor
- Switch
- TemperatureSensor
- Thermostat
- Valve
- Window
- WindowCovering