-
Notifications
You must be signed in to change notification settings - Fork 2
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
ModuleNotFoundError #12
Comments
I have always had the log level "info" of "Domoticz-TinyTUYA-Plugin" turned off, when turning it on I'm getting similar errors as shown above, so I'm guessing this not to be the issue:
Think it's my subnet. |
Think I have it working now, although I'm not sure if part of this comes from the fact the devices already were imported from the cloud plugin. Still have one question though: I'm getting 6 new devices tomorrow, will those be added to Domoticz automagically? |
Spun up a separate Domoticz instance, added the plugin, ran the wizard and I'm greeted with the following error and no devices were added:
So I'm still thinking it's my subnet. |
Eureka! I removed a device from my Tuya account just to add it again but now on my main LAN instead of my IoT LAN and now the IP address was found. A restart of Domoticz and the device was added there too. So: it would be great if the plugin would also scan over multiple subnets or (probably better) the possibility to add a subnet other than the one Domoticz is on. Still testing what happens when I add the IP addresses to devices.json by hand. |
Trying this plugin hoping to move from "Domoticz-TinyTUYA-Plugin" and I'm getting the following the following errors:
I'm running both plugins in the same container, will that work? I have installed cryptography.
When running the wizard inside the container all seems to work fine until polling the devices where I'm greeted with the following errors:
My devices are on a separate IoT network, could this be causing this issue? The plugin probably only scanning the current subnet?
The text was updated successfully, but these errors were encountered: