Updated to Homebridge platform #47
Comments
|
Amazing work!
If you like, I can pull the changes into this repo and add you as a maintainer - rather than it living in a fork?
… On 15 Nov 2021, at 14:08, Fraser Sim ***@***.***> wrote:
Hi @mylesagray <https://github.com/mylesagray>,
As I was getting numerous warnings from Homebridge, I took a look at the blueair plugin to see if I could fix but then got a bit carried away.
I started working on a fork of your awesome plugin and recoded it using typescript as a dynamic platform type plugin. This way when you login, the BlueAir devices are detected and added as accessories automatically.
I also enabled configuration using the Homebridge UI so folks do not have to work with the json config directly. I also added some experimental code to allow people to hide devices that they do not want to wish to appear in Homebridge. This could also be extended to turn on/off support for features as you do.
https://github.com/fjs21/homebridge-blueair <https://github.com/fjs21/homebridge-blueair>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#47>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEUYTEFU3B4ABTMTNLHRLLUMEH6ZANCNFSM5IBY454Q>.
|
|
I'm not very experienced with this but I'm not sure that a pull is the best option as it will break a lot of people's setups. Mine was working basically fine up as long as it ran in a bridge. If you don't mind I could respond to the issues of others to direct them to my fork as an alternative? Quick change of the readme file may also work to direct people to the platform fork? |
|
Sure that works too, if you want to open a PR for a readme update, I’ll merge it.
… On 15 Nov 2021, at 14:23, Fraser Sim ***@***.***> wrote:
I'm not very experienced with this but I'm not sure that a pull is the best option as it will break a lot of people's setups. Mine was working basically fine up as long as it ran in a bridge.
If you don't mind I could respond to the issues of others to direct them to my fork as an alternative? Quick change of the readme file may also work to direct people to the platform fork?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEUYTBCIHWXJ6QTMTEEHH3UMEJWRANCNFSM5IBY454Q>.
|
|
I couldn't work out how to do the PR for just a single file and not blow up the entire repository. You could either use my readme.md file or just put a link to my repo in your readme. Sorry for the extra hassle. |
|
Added a redirection to your plugin Fraser, i'm considering archiving this repo if you are done addressing the issues from users and redirecting them to your plugin? |
Hi @mylesagray,
As I was getting numerous warnings from Homebridge, I took a look at the blueair plugin to see if I could fix but then got a bit carried away.
I started working on a fork of your awesome plugin and recoded it using typescript as a dynamic platform type plugin. This way when you login, the BlueAir devices are detected and added as accessories automatically.
I also enabled configuration using the Homebridge UI so folks do not have to work with the json config directly. I also added some experimental code to allow people to hide devices that they do not want to wish to appear in Homebridge. This could also be extended to turn on/off support for features as you do.
https://github.com/fjs21/homebridge-blueair
The text was updated successfully, but these errors were encountered: