Cant retrieve itunes state

[ncosper]

Tried to install on two computers. Seems that if the current version of this plugin is installed it prevents new devices from pairing with homebridge. Tried on two Mac's.
Upon unistalling the plugin, I paired to homebridge no problem. Then reinstalled the plugin but it fails to retrieve the state of the accessory. Shows the possible commands that homekit can send, but gets no state therefore is useless. Im guessing its a bug unless I made the same mistake twice. Config is "platforms": [
{
"platform": "iTunes"
}
]

[SphtKr]

Hmm....that's...odd. You could try deleting ~/.homebridge/accessories/cachedAccessories and restarting Homebridge, but obviously that shouldn't be necessary. Also, deleting ~/.homebridge/persist/* should reset pairing so you could pair again, but that of course will wipe out your bridged accessories (if you are using any other plugins).

Just to check, you're aware that you can only pair a Homebridge instance with a single device, right? Once you pair with one device, other devices on the same iCloud account will automatically be able to communicate with that Homebridge instance. To get other devices that are not logged into the same iCloud account to talk to that Homebridge instance, you have to share your home with the other iCloud user account.

[BUMPRW]

Okay maybe that’s my problem I don’t use iCloud, in fact I avoid it, nevertheless all my other platforms and accessories work. I haven’t tried homebridge iTunes since my last email, so I don’t have any updates. I wrote a script file to remove then reload everything, since what you describe in your first paragraph is exactly what I had to do, including manually deleting the npm modules in my home directory; otherwise, home bridge would not restart.

I somehow missed the iCloud reference in your module description.

On Jun 28, 2016, at 11:41 PM, SphtKr notifications@github.com wrote:

Hmm....that's...odd. You could try deleting ~/.homebridge/accessories/cachedAccessories and restarting Homebridge, but obviously that shouldn't be necessary. Also, deleting ~/.homebridge/persist/* should reset pairing so you could pair again, but that of course will wipe out your bridged accessories (if you are using any other plugins).

Just to check, you're aware that you can only pair a Homebridge instance with a single device, right? Once you pair with one device, other devices on the same iCloud account will automatically be able to communicate with that Homebridge instance. To get other devices that are not logged into the same iCloud account to talk to that Homebridge instance, you have to share your home with the other iCloud user account.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #7 (comment), or mute the thread https://github.com/notifications/unsubscribe/ASW-jWnPmvFz9-cIhZ4Lv3kp_YCL8CpCks5qQfdpgaJpZM4I03kn.

[SphtKr]

The iCloud mechanism I described is a HomeKit requirement, not specifically for this module. I was keying on that you said "it prevents new devices from pairing with homebridge", but if you're saying that other platforms/accessories work, I must have misunderstood what you meant.

At any rate, haven't seen what you're describing yet, but it's possible. The next version should be smarter about it's polling for state (for instance) which may improve reliability.

[BUMPRW]

Part I: Truth in the details is that I have ICloud turned on, but as far as I know I am not using it.

Part II: I gave up on the QNAP NAS and am only running homebridge from the MiniMac, although my initial efforts were on my MacBookPro. The QNAP has a built in iTunes server, but none of my MACs see the server. I probably need to turn it off before I try again.

Through my MiniMac, I do have fairly effective music distribution and sync capabilities using Supersync. However, I am always looking for ways to improve. I am currently running the trial version of Indigo and I did try their iTunes server. I’m still trying to determine what it does.

On Jun 29, 2016, at 11:38 PM, SphtKr notifications@github.com wrote:

The iCloud mechanism I described is a HomeKit requirement, not specifically for this module. I was keying on that you said "it prevents new devices from pairing with homebridge", but if you're saying that other platforms/accessories work, I must have misunderstood what you meant.

At any rate, haven't seen what you're describing yet, but it's possible. The next version should be smarter about it's polling for state (for instance) which may improve reliability.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #7 (comment), or mute the thread https://github.com/notifications/unsubscribe/ASW-jZHySHZvKJY8cc7hBHd5SYXGgX1Gks5qQ0hdgaJpZM4I03kn.

[ncosper]

The iCloud mechanism I described is a HomeKit requirement, not specifically for this module. I was keying on that you said "it prevents new devices from pairing with homebridge", but if you're saying that other platforms/accessories work, I must have misunderstood what you meant.

I did remove everything in the persist folder a few times. I was also only trying to pair to one device. I still haven't been able to get it to work although I haven't tried since I wrote the initial issue.

The only progress I did make was to pair with the plugin uninstalled and then reinstalled. It will poll for the state and normally retrieve it but I cannot control...