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

Fanv2 showing up as unsupported in the web interface #418

Closed
bushshrub opened this issue Nov 18, 2019 · 3 comments
Closed

Fanv2 showing up as unsupported in the web interface #418

bushshrub opened this issue Nov 18, 2019 · 3 comments
Labels

Comments

@bushshrub
Copy link

Describe Your Problem:

Fanv2 showing up as not supported on the web interface. Fan is configured from the homebridge-broadlink-rm plugin.

Logs:

https://hastebin.com/mijofirage.coffeescript
Homebridge Config:
https://hastebin.com/jusefeqepu.json

Screenshots:

https://i.imgur.com/Q3hm6Fa.png

Environment:

  • Node.js Version: v11.9.0
  • NPM Version: 6.5.0
  • Homebridge Version: 0.4.50
  • Homebridge Config UI X Version: 4.6.3
  • Operating System: Ubuntu Server 18.10 Cosmic Cuttlefish
  • Process Supervisor: screen (basically nothing)
@oznu
Copy link
Member

oznu commented Nov 22, 2019

FanV2 is not currently a supported accessory type. See #47

@bushshrub
Copy link
Author

Sorry, let me rephrase for clarity. My accessory is a regular Fan, yet it is showing up as not supported in the web interface. This is rather strange. Is it because it is a Fanv2? I assumed that all fans were the same type

@oznu
Copy link
Member

oznu commented Nov 24, 2019

Fanv2 is a different accessory type to Fan in the HomeKit ecosystem so it needs to be implemented independently. I've linked this issue to the meta issue and I'll see how what's involved in adding it soon.

@oznu oznu closed this as completed Nov 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants