Skip to content
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

Remove Gen 2 devices #28

Open
Subivan1 opened this issue Nov 26, 2021 · 6 comments
Open

Remove Gen 2 devices #28

Subivan1 opened this issue Nov 26, 2021 · 6 comments

Comments

@Subivan1
Copy link

Is it possible to remove /exclude gen 2 devices? I have just upgraded all my lights to latest firmware and the gen 2 lights are now HomeKit compatible. This causes duplicate devices within HomeKit. My gen 1 devices still need to work with this plugin.
Are there any options or features that could be added to specify which twinkly devices should be included or excluded in the plugin?

@JacobSyndeo
Copy link

+1; this will be an important feature for this plugin moving forward.

@inspectorgadjet7
Copy link

Agreed. But it turns out that not all Twinky Gen II devices are supported. If your device is a ‘Polygroup’ licensed product like my pre-lit tree, HomeKit is not currently available, so this feature would need to either detect a Polygroup product somehow, or just let us hide certain devices.

@JacobSyndeo
Copy link

Let’s just be able to hide certain devices then.

@vanHoesel
Copy link

I have made some tweaks to this plugin that only now show up in the official HomeKit firmware upgrade ... but I have more to come.

Dropping Gen-II is not a wise idea, but maybe a option to turn it off

@nsforge
Copy link

nsforge commented Dec 13, 2021

I just bought some Gen 2 lights, but the built-in HomeKit support seems very broken. When I enabled it, the lights became glitchy and juddery, and the responsiveness to commands through the app dropped to 1-2s (and occasionally just timed out completely). Power cycling didn't help, and the only way I was able to fix it was to do a factory reset.

Given that the 1st-party support seems to be somewhat broken, I'd like to try using homebridge instead (since that shouldn't have any impact on the devices's onboard CPU/RAM resources), so I'd like to add another vote for adding the ability to hide devices, rather than actually dropping support for Gen 2 devices.

@vanHoesel
Copy link

By design, it is now doing a auto-detect, which is awesome, Apple Homekit should all be easy to use.

I still rely on manual configuration and have my strings even hardcoded in my router to assign an IP-address. I have listed my strings in the config file.

For 'heavy-users' I would advice to add a 'blacklist' option for IP addresses

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants