-
Notifications
You must be signed in to change notification settings - Fork 1
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
Tuya credential steps unclear and not easy to reconfigure #8
Comments
Thanks for the feedback! I'll look into everything the coming days |
Also, |
@AboveColin Thanks for large efforts with this integration and adressing the issues! By accidentally I stumbled upon the homeID first, before seeing the deviceID, so that is why I mentioned it. |
I updated the readme, should be more clear now :) |
Thats incredibly fast work. I will try it out right away, amazing! |
I updated to the 1.71 and followed the improved guidelines in the readme but unfortunately still cannot seem to get it working. `Logger: aiohttp.server Error handling request `Logger: homeassistant.config_entries Error setting up entry Philips Pets Series (My Name) for philips_pet_series |
After updating to 1.16 to fix the login issues, and tweaking the frida command to obtain the local key, I am now stuck at successfully making the tuya connection to the device. It is also not easy to play around with the inputs, as all 5 fields need to be submitted, and when it does not work, the entire integration entry needs to be removed and with all 5 fields resubmitted.
I will split the issue into 4 parts:
Updating entries: Currently, when making a mistake in the config, it cannot be updated as the integration entry need to be deleted and re-entered. Many integrations have a reconfigure option (one example of this is AfvalInfo). Since all 5 fields need to be re-entered and it needs to establish the connection to the server, this is very cumbersome when troubleshooting.
Client_id (readme) / tuya_client_id (set-up): The naming is inconsistent and it is a bit vague what roll tuya plays in this setup, as we do not have to touch the tuya app, right? Moreover, it could be specified that this is the DeviceID under: the app dashboard, appliances, pet feeder, settings, DeviceID. And specify this is NOT the same as the HomeID. (Am I correct here??)
IP (readme) / tuya_ip (setup): Again the naming is confusing, I would call it Pet Feeder IP. Moreover, what is the best way to find it? I cannot seem to find it in the app, and in my Asus router it does not show up with any name as it is listed as an unknown manufacturer. What I did was export at the devices list under 2.4Ghz, then turn off the WiFi by unplugging the power and wait for a bit, look again at the list and see what changed. Then I turned on the WiFi again by plugging it back in and have it appear again. Was this the easiest method, or are there any alternatives? With my crowded network this is not as simple as it may seem to others.
Local Key (readme) / tuya_local_key (setup): Again for the naming I would stick to Local Key. Additionally, the formatting from the obtained output.txt file is confusing and it is unclear what to use as an input here.
For example, my output looks like
"localKey\":\"FceXXXX]+$7}9Zl.\",
, now what part do I take:\"FceXXXX]+$7}9Zl.\"
,"FceXXXX]+$7}9Zl.\"
,FceXXXX]+$7}9Zl.\
, orFceXXXX]+$7}9Zl.
?Since I have numerous unknowns, I tried multiple combinations but could not get it to work yet. This could be from any simple reason such as needing to take a different value for Client_id, accidentally still having selected the wrong IP, or wrong formatting on the LocalKey. If someone could clear up some of the unknowns will become much easier to troubleshoot a single value rather than all three.
The text was updated successfully, but these errors were encountered: