在线时间:8:00-16:00
迪恩网络APP
随时随地掌握行业动态
扫描二维码
关注迪恩网络微信公众号
开源软件名称:ebaauw/homebridge-hue开源软件地址:https://github.com/ebaauw/homebridge-hue开源编程语言:JavaScript 100.0%开源软件介绍:Homebridge HueHomebridge plugin for Hue and/or deCONZCopyright © 2016-2022 Erik Baauw. All rights reserved. Planned ChangesSee Future Development of Homebridge Hue. IntroductionThis Homebridge plugin exposes to Apple's HomeKit ZigBee devices (lights, plugs, sensors, switches, ...) connected to a Hue bridge by Signify, or to a deCONZ gateway by dresden elektronik. Note that Hue was originally developed by Philips, before they split off their Lighting division into Signify. Signify are still using the Philips Hue brand name. For a better understanding of deCONZ, see deCONZ for Dummies. See the Wiki for a list of Homebridge Hue features and supported devices, including a comparison of the features of:
Homebridge Hue does automatic discovery of Hue bridges and deCONZ gateways. It supports multiple bridges / gateways from one installation. It supports both the v2 (square) and v1 (round) Hue bridge. It works in combination with the native HomeKit functionality of the v2 Hue bridge. Please see the Wiki for a detailed description of Homebridge Hue. PrerequisitesYou need a Philips Hue bridge or deCONZ gateway to connect Homebridge Hue to your ZigBee lights, switches, and sensors. I recommend using the latest Hue bridge firmware, with API v1.41.0 (v2 bridge) or v1.16.0 (v1 bridge) or higher, and the latest deCONZ beta, v2.9.0 or higher. You need a server to run Homebridge.
This can be anything running Node.js: from a Raspberry Pi, a NAS system, or an always-on PC running Linux, macOS, or Windows.
See the Homebridge Wiki for details.
I run deCONZ and Homebridge Hue together on a Raspberry Pi 3B+, with a RaspBee add-on board. To interact with HomeKit, you need Siri or a HomeKit app on an iPhone, Apple Watch, iPad, iPod Touch, or Apple TV (4th generation or later).
I recommend to use the latest released versions of iOS, watchOS, and tvOS. As HomeKit uses Bonjour to discover Homebridge, the server running Homebridge must be on the same subnet as your iDevices running HomeKit. For remote access and for HomeKit automations (incl. support for wireless switches), you need to setup an Apple TV (4th generation or later), HomePod, or iPad as home hub. Command-Line ToolsHomebridge Hue includes the following command-line tools:
These tools takes a InstallationTo install Homebridge Hue:
To update Homebridge Hue, simply issue another ConfigurationIn Homebridge's For finer-grained control of what resources Homebridge Hue exposes to HomeKit, and how, create resource links on the bridge / gateway, see the Wiki. TroubleshootingPlease check the FAQ. Check DependenciesIf you run into Homebridge startup issues, please double-check what versions of Node.js and of Homebridge have been installed. Homebridge Hue has been developed and tested using the latest LTS version of Node.js and the latest version of Homebridge. Other versions might or might not work - I simply don't have the bandwidth to test these. Run Homebridge Hue SoloIf you run into Homebridge startup issues, please run a separate instance of Homebridge with only Homebridge Hue (and Homebridge Config UI X) enabled in Debug Log FileHomebridge Hue outputs an info message for each HomeKit characteristic value it sets and for each HomeKit characteristic value change notification it receives.
When Homebridge is started with To capture these messages into a log file do the following:
Debug Dump FileTo aid troubleshooting, on startup, Homebridge Hue dumps its environment, including its Getting helpIf you have a question, please post a message to the #hue channel of the Homebridge community on Discord. If you encounter a problem, please open an issue on GitHub.
Please attach a copy of ContributingSometimes I get the question how people can support my work on Homebridge Hue. I created Homebridge Hue as a hobby project, for my own use. I share it on GitHub so others might benefit, and to give back to the open source community, without whom Homebridge Hue wouldn't have been possible. Having said that, adding support for new devices, in Homebridge Hue, and in the deCONZ REST API plugin, is very hard without having physical access to the device. Since this is a hobby project, I cannot afford to spend money on devices I won't be using myself, just to integrate them for the benefit of others. I am happy to receive small donations in the form of new devices to integrate, or the money to buy these devices myself. I am also happy to return the devices afterwards, if you provide the shipping costs. Please contact me by email or on Discord for shipping details. CaveatsHomebridge Hue is a hobby project of mine, provided as-is, with no warranty whatsoever. I've been running it successfully at my home for years, but your mileage might vary. The HomeKit terminology needs some getting used to.
An accessory more or less corresponds to a physical device, accessible from your iOS device over WiFi or Bluetooth.
A bridge (like Homebridge) is an accessory that provides access to other, bridged, accessories.
An accessory might provide multiple services.
Each service corresponds to a virtual device (like a lightbulb, switch, motion sensor, ..., but also: a programmable switch button, accessory information, battery status).
Siri interacts with services, not with accessories.
A service contains one or more characteristics.
A characteristic is like a service attribute, which might be read or written by HomeKit apps.
You might want to checkout Apple's HomeKit Accessory Simulator, which is distributed as an additional tool for Internally, HomeKit identifies accessories by UUID. For Zigbee devices (lights, sensors, switches), Homebridge Hue bases this UUID on the Zigbee mac address. For non-Zigbee resources (groups, schedules, CLIP sensors), the UUID is based on the bridge / gateway ID and resource path (e.g. |
2023-10-27
2022-08-15
2022-08-17
2022-09-23
2022-08-13
请发表评论