Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/joelwetzel/homebridge-hubitat-mediainputsource
Homebridge plugin to connect a Hubitat MediaInputSource device to HomeKit.
https://github.com/joelwetzel/homebridge-hubitat-mediainputsource
Last synced: about 1 month ago
JSON representation
Homebridge plugin to connect a Hubitat MediaInputSource device to HomeKit.
- Host: GitHub
- URL: https://github.com/joelwetzel/homebridge-hubitat-mediainputsource
- Owner: joelwetzel
- License: apache-2.0
- Created: 2023-02-13T16:30:32.000Z (almost 2 years ago)
- Default Branch: master
- Last Pushed: 2023-08-01T17:40:01.000Z (over 1 year ago)
- Last Synced: 2024-11-13T11:41:46.636Z (about 2 months ago)
- Language: JavaScript
- Homepage:
- Size: 113 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Homebridge Plugin - Hubitat MediaInputSources
[](https://badge.fury.io/js/homebridge-hubitat-mediainputsource)
I made a Hubitat driver for an HDMI switch (https://github.com/joelwetzel/Hubitat-4KMX42-H2A) that implements Hubitat's "MediaInputSource" capability. This capability allows for switching between two different inputs.
Unfortunately, this capability is only lightly supported so far. I don't think it's used very often. I use a [Homebridge](https://homebridge.io) plugin from danTapps to connect my Hubitat to HomeKit: https://github.com/danTapps/homebridge-hubitat-makerapi. Unfortunately, it does not support "MediaInputSource". However, I used it as a base to make my own Homebridge plugin.
The plugin is also registered with [NPM](https://www.npmjs.com/package/homebridge-hubitat-mediainputsource), so you can add it to any Homebridge by searching for and installing homebridge-hubitat-mediainputsource. A valid config for the plugin will look like:
> {
>
> "platform": "Hubitat-MakerAPI-HDMI-Switch",
>
> "name": "Hubitat-MakerAPI-HDMI-Switch",
>
> "app_url": "http://192.168.1.113/apps/api/2/",
>
> "access_token": "REDACTED"
>
> }
My plugin queries Hubitat just like danTapps's plugin, but it ONLY looks for Hubitat devices with the MediaInputSource capability. It translates it into an appropriate accessory type in HomeKit. In HomeKit, the accessory has a category of TELEVISION, and has 3 services: Television, InputSource, and Switch. In the Home app, this renders it as an accessory with a power button and an input selector:
Extra installation step: Television devices have to be published as an "external accessory" in Homebridge. This means they won't be included by default when adding the Homebridge to your Home app. The television device has to be added separately.
You'll need to open your Homebridge Status page. When you restart the Homebridge, you'll see log lines like:
>[18/07/2023, 13:23:58] Family Room HDMI Switch D6F0 is running on port 38779.
>
>[18/07/2023, 13:23:58] Please add [Family Room HDMI Switch D6F0] manually in Home app. Setup Code: 786-74-406
You can then add the accessory in the home app using that setup code.
Issue: The Home app on iPhone has a UI bug involving television pickers. Sometimes, when you turn the power on, the input selector becomes deactivated, and if you oscillate power on and off, the input selector's activation status will always be the opposite of what it should be. Therefore, I don't really use it directly. I use the Scenes to control everything.