-
Notifications
You must be signed in to change notification settings - Fork 166
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
Issue with platform name and config.json setup #355
Comments
Will be fixed in v2.1.0, thanks for reporting! |
I am encountering the same issue and unable to use the plug-in within Hoobs 4. It won't discover the devices. @stauffes - can you share what your work-around was in the config.json for the devices to be recognized? Thanks in advance for your help! |
UPDATE: Played around with the code and got it working. Would be nice to see this updated in the next version though as per your comment, it will overwrite the code again on the bridge re-starting. |
Upgraded to HOOBS 4 and made the following changes to the code to get it working:
|
…he comments in the 2.0.1 Release notes. This will resolve Issue #355 but will be a breaking change requiring the config to be updated before restarting the homebridge.
This should now be fixed as per version 3.1.0. I updated the schema so that the existing configs from the previous versions would work without changes. |
Thank you! |
I just updated to 3.1.0 on HOOBS 4 and index.js has
The log file showed
I changed |
Checklist
Describe the bug
I am able to install the plugin on a new bridge, however, the config.json file is pre-populated with two platforms named Tuya an d TuyaLan. The UI config only displays the platform Tuya and any added devices fall underneath this platform, however when I go to run the bridge, it is not able to find any devices because it is expecting them to be under the TuyaLan platform. I have tried to install this plugin on both my Pi and a hoobs running on a virtual ubuntu with the same effect. I have had some moderate luck manually configuring the config.json, however it is often overwritten when the bridge starts again with the same issue as before. Not sure I understand why the "Tuya" platform is being populated in the config.json file or why that is what is editable in the UI.
To Reproduce
Install this plugin
Expected behavior
I would expect the config.json file to only have one platform named TuyaLan and the UI to be able to edit devices within this platform.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: