-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Plugin does not run #10
Comments
Your config.json doesn't validate on jsonlint.com but that might just be a formatting issue. Would you be up for removing all other plugins on your config.json running, and then posting the logs? I will upload an example. |
I validated on jsonlint.com, so I'm pretty sure I just screwed something up while saving to .txt. I can't turn off the other plugins just now without causing problems for some folks in the house, but if it's helpful, I rebooted my server and have a better log for you now. I think there's something wrong with my setup where hitting the restart button in Config UI X isn't actually restarting HB. But in this rebooted log, you can see your plugin loading and finding no devices, even though the controller is turned on. I hope this helps. If not, I can figure out a time to uninstall the other plugins temporarily. [7/16/2020, 5:08:58 PM] Got SIGTERM, shutting down Homebridge... HAP Warning: Characteristic undefined not in required or optional characteristics for service 0000008A-0000-1000-8000-0026BB765291. Adding anyway.
[7/16/2020, 5:12:44 PM] Homebridge is running on port 51826. [7/16/2020, 5:12:45 PM] [homebridge-magichome-dynamic-platform] �[0;37m[7/16/2020, 5:12:50 PM] �[0m�[0;36m[Config]�[0m Starting Nest application... |
Okay, it is definitely the "registered zero accessories" bug. I think this is due to a lack of a feature that I need to add that allows my plugin to interface with devices using the original LEDnet protocol. Are you by chance using an RGB controller? |
Yep, I'm using this one, specifically: https://smile.amazon.com/gp/product/B0746654D5/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 |
@barryl93 Just posted a minor update that included a bug fix. Please update the plugin and restart homebridge. Hopefully this fixes your issue. Otherwise you'll have to wait for the major update |
No luck for me. All good though. Will wait as well for the bigger update. I am working through some tuya issues. Argh :)
…
On Jul 21, 2020 at 3:01 AM, <Zacknetic ***@***.***)> wrote:
@barryl93 (https://github.com/barryl93) Just posted a minor update that included a bug fix. Please update the plugin and restart homebridge. Hopefully this fixes your issue. Otherwise you'll have to wait for the major update
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (#10 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/ALLAX27YB2YEM2S6GAIRVULR4U4MRANCNFSM4O4ZQZ2A).
|
No good for me, either, but absolutely no big deal -- this is more of a fun project than anything else. I appreciate the response! |
@barryl93 @vascott1 I have posted a major update which may solve your problem. Please update to the latest version and ensure your magichome accessories are completely removed before trying to use them again. You can do this by either deleting your accessories folder and removing everything, or by using my prune feature. Be sure to disable it after a restart. |
I have posted yet another update that may solve your issues. I am closing this now due to lack of activity, but please re-open it again if you'd like additional help. Thank you. Please update your plugin to version 1.5.1 . Note: if you are updating from version 1.4.x you'll need to purge all your magichome devices after updating. Then restart homebridge to rescan. With help, I found a bug in the code that caused duplicate device to register if the user had multiple subnets. Thus the crash. I was trying to scan on more than one subnet but didn't account for devices showing up on more than one. |
Closing this issue but feel free to reopen it if you continue to find issues. Be sure to update to the latest version 1.6.2 and purge your magichome devices. |
Sure! BTW, I also tried uninstalling and re-installing the plugin, just in case, but still no luck.
config.txt
log.txt
Originally posted by @barryl93 in #5 (comment)
The text was updated successfully, but these errors were encountered: