search

Zacknetic / HomebridgeMagicHome-DynamicPlatform

Homebridge Plugin for MagicHome LED controllers and light bulbs
Apache License 2.0
61 stars 11 forks source link

[BUG] Concise Description of the Issue #110

Closed Damianod27 closed 2 years ago

Damianod27 commented 2 years ago

Hello. Since my few plugins required the installation of a new version of Node.js and NPM. I updated them today. From now on, the MagicHome lights control in homebridge and the Home application do not work. There are no log errors. Everything looks fine but the lights don't react.

Homebridge Vesrion : 1.35 Nodejs Version : 16.13.0 NPM Version : 8.1.0 MagicHome Version : 1.9.,4

dakovacic commented 2 years ago

I am also seeing this issue since my upgrade of Node.js to 16.13.0.

Homebridge Version : 1.35 Nodejs Version : 16.13.0 NPM Version : 8.1.0 MagicHome Version : 1.9.4

Turning the plugin logging level up to trace indicates that the plugin sees and registers my devices on initial startup, but then can't talk to them and goes into a loop of trying to rediscover them.

monteroman commented 2 years ago

I'm also seeing this behavior on the same versions. All of my MagicLight color bulbs are showing 100% brightness and turned on in My Home, however they are all powered off. They all respond normally with the MagicLight mobile app.

Damianod27 commented 2 years ago

Yes, that's right. This is a Node.js 16.13.0 problem. Some of my plugins require a new Node.js. They are more important to me. That's why he stays with the new version. Because they solve the problem in my plugins. I am waiting for the problem to be solved. It is a pity that so many days pass and nobody wants to be interested in it.

Zacknetic commented 2 years ago

Hi,

node has broken this plugin as you have deducted. It is not that I do not care about this plugin, I fact I have been developing a complete overhaul since august. I plan to push a beta on Sunday. Please join the discord and inquire if you are interested.

On Nov 5, 2021, at 4:58 PM, Damianod27 @.***> wrote:

 Yes, that's right. This is a Node.js 16.13.0 problem. Some of my plugins require a new Node.js. They are more important to me. That's why he stays with the new version. Because they solve the problem in my plugins. I am waiting for the problem to be solved. It is a pity that so many days pass and nobody wants to be interested in it.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or unsubscribe.

Damianod27 commented 2 years ago

Hello Zacknetic. Thank you for your answer. Nobody said you weren't interested in the plug. My point was that no one was interested in the reported problem. You release updates. Nobody requires you to fix the bug within seconds. You're doing a good job. Thank you for your plugin. We are waiting calmly for the updates.

Will a completely new redesigned plugin that you release in the future be an update to the current plugin or will it be a completely new plugin ?

Zacknetic commented 2 years ago

I can’t wait to bring it to you. Thank you for your patience!

On Nov 5, 2021, at 7:10 PM, Damianod27 @.***> wrote:

 Hello Zacinetic. Thank you for your answer. Nobody said you weren't interested in the plug. My point was that no one was interested in the reported problem. You release updates. Nobody requires you to fix the bug within seconds. You're doing a good job. Thank you for your plugin. We are waiting calmly for the updates.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or unsubscribe.

Zacknetic commented 2 years ago

Hello, please update to version 1.9.7 and ensure you are upgraded to node 16. This should fix your issues.

Please let me know. -z

monteroman commented 2 years ago

1.9.7 was working up until the last home bridge update came out last week. HB 1.3.8, Node 13.16.1. It's doing the same thing as it was before. You click the button on, nothing happens, but the Home app thinks it is on.

Zacknetic commented 2 years ago

1.9.7 was working up until the last home bridge update came out last week. HB 1.3.8, Node 13.16.1. It's doing the same thing as it was before. You click the button on, nothing happens, but the Home app thinks it is on.

Homebridge does not support odd-numbered releases of Node.js. Can you confirm that you are using Node 13.16.1 and if so, please update to 14.x or 16.x. Let me know how that goes.

monteroman commented 2 years ago

Sorry, i reversed the #’s. It was actually 16.13.1, not 13.16.1.

On Dec 9, 2021, at 3:19 PM, Zacknetic @.***> wrote:

1.9.7 was working up until the last home bridge update came out last week. HB 1.3.8, Node 13.16.1. It's doing the same thing as it was before. You click the button on, nothing happens, but the Home app thinks it is on.

Homebridge does not support odd-numbered releases of Node.js. Can you confirm that you are using Node 13.16.1 and if so, please update to 14.x or 16.x. Let me know how that goes.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Zacknetic/HomebridgeMagicHome-DynamicPlatform/issues/110#issuecomment-990214791, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJS2ISRX3HCEFSKEURD7Z3UQEFNPANCNFSM5HE74DGA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Zacknetic commented 2 years ago

Testing.

Zacknetic commented 2 years ago

I just tested it on:

Node.js Version | v16.13.1 Homebridge Version | v1.3.8

It is working correctly.

I will close this as it seems the original issue has been solved. @monteroman, please create a new issue using and following the bug template. The more information I have, the better my chances of solving the problem. I'll keep an eye out for it.