-
Notifications
You must be signed in to change notification settings - Fork 488
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
I don't know if it's a bug or not #1491
Comments
Please include the log messages related to this from Settings/System/Logs/Full Log |
The relevant log message is this: 2024-01-08 02:41:23.637 WARNING (MainThread) [custom_components.tuya_local.config_flow] Device matches None with quality of 0%. DPS: {"updated_at": 1704670868.2671, "4": "chargego", "5": "charge_done", "6": 0, "7": 1, "8": 100, "9": "gentle", "10": "closed", "17": 190, "19": 290, "21": 140, "23": 149, "26": 8, "28": 0} Which device is this for (it looks like a vacuum cleaner)? |
This vacuum cleaner #1284 |
Mark power, charging dps as optional Logs from use show these as sometimes missing. As they are required switches for operation, null is mapped to false (off) as an assumption. Issue #1491
That is not the device id, it is the product id.
Product id is common to all devices of that type. It can be used in future
to link devices to config files (but not currently, because product id is
only available via the cloud and during local network discovery, but
currently we do not support discovery, only manual config).
Device id is unique to your device. It is used to configure your specific
device.
|
yes, I understood, so I deleted the comment, everything is fine there) |
if you restore the backup of the home assistant with an already authorized vacuum cleaner, it works now, if you delete it, you will no longer add it, it says "this device is not supported" |
Mark power, charging dps as optional Logs from use show these as sometimes missing. As they are required switches for operation, null is mapped to false (off) as an assumption. Issue make-all#1491
hi, I don't know if this is a bug or not, but I'll write here, before that I described the add device to you, in the last update it says that it was added, but now it just gives me a sign saying "the device is not supported" (at the same time, before the update was released, I manually added it from your repository and it worked, except one team. Why is that?
This is the device #1284
The text was updated successfully, but these errors were encountered: