-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Item in HomeKit requires two taps to do everything #116
Comments
I believe this is a local issue on your system because a basic dimmer control is not only the most basic thing that the plugin supports but between my own setup and every other setup of HKB I'm sure there must be hundreds in use and this is the first time anyone has mentioned any issue like this. Try restarting the plugin and see what that does. I have not yet analyzed your logs but this is most certainly not a plugin issue. |
I actually rebooted the xServer…it had been running for over 100 days :-)
Working great now…awesome work on this….my wife is not as thrilled that I can control everything from Siri, but I am :-)
Sincerely,
===========================
Philip Grossman
[email protected]
… On Aug 10, 2018, at 5:18 PM, Colorado Four Wheeler ***@***.***> wrote:
I believe this is a local issue on your system because a basic dimmer control is not only the most basic thing that the plugin supports but between my own setup and every other setup of HKB I'm sure there must be hundreds in use and this is the first time anyone has mentioned any issue like this.
Try restarting the plugin and see what that does. I have not yet analyzed your logs but this is most certainly not a plugin issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#116 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AoUuCgT8vmSArWC05p0nd5UwQ_UqxI6zks5uPfi7gaJpZM4V4zuY>.
|
I just installed the HomeKit bridge for the first time and have the same problem. I installed the plugin, set it up (though the setup dialogs had more fields and did not look the same as the QuickStart documents. I was able to get it running in indigo. I created one device linked to a simple on-off lamp. I opened the Home app and created a new Home (I'm doing this in my father's house). The lamp device appeared. It took 2 clicks to toggle the lamp state. I tried removing the Home device in the plugin, disabling the plugin, removing my Home in the app, and then reconfiguring. This time I was not able to even connect the Home app to Indigo. Very frustrating |
Deleted everything: the Home in my Home App, the HomeBridge device in Indigo, the Plugin itself from the finder, and reinstalled from the zip file. Was able to connect this time from the Home app. Still the same behavior. See the log: `Feb 18, 2019 at 9:04:02 AM Feb 18, 2019 at 9:05:04 AM HomeKit Bridge Error Exception in plugin.serverFormFieldChanged_Action line 3654: 'key objectType not found in dict' Feb 18, 2019 at 9:06:35 AM Feb 18, 2019 at 9:07:40 AM Feb 18, 2019 at 9:08:56 AM Feb 18, 2019 at 9:17:50 AM Feb 18, 2019 at 9:18:30 AM Feb 18, 2019 at 9:19:00 AM Feb 18, 2019 at 9:20:12 AM Feb 18, 2019 at 9:21:54 AM |
I’m seeing the same behavior as @nwikner. Lemme know if there’s anything I can to to help debug this Edit: In my case stopping and starting the Indigo server (not HomeKit Bridge server) made this start working. Not sure what the deal is there but prob some state issue. At any rate, it works. Thanks! |
I had the same problem and can confirm a reload via |
Expected Behavior
Item (smartphone plug in dimmer) shows up in home kit and taping should turn on light, taping again should turn off light
Current Behavior
Icon shows light off, taping shows icon "on" but light does not turn on, tapping again shows light off, but does nothing, tapping a third time, turns the light on and shows the light on.
Steps to Reproduce (for bugs)
Does this with the two lights (plug in modules) that I have added to the Homebridge server.
Versions
1.0.2
Indigo 7.1.1
Configuration
Homebridge Log / Command Output
Device Simulation Report
The text was updated successfully, but these errors were encountered: