can not connect to Device #34
Comments
|
Hi, |
|
Yes I see it:
In fhem I tried to define with this: The IP I got from the Tuya App, suprisinlgy different to the rest of my Homenetwork IP |
|
Btw, you should use only tuya_cloud. I wouldn't recommend tuya module as it is not event based and therefore doesn't readings aren't updated immediately. |
|
Please use tuya_cloud instead of tuya module. |
|
May be worth to mention the Tuya I guess here is something wrong and hence the scan is not working |
|
ok, Cloud connector is defined with: By the way a change or delete and new install seems to be super qucik, only intial definition took a little longer, no clue iof it realy tries modifications to apply |
|
Yes, what's the result? |
|
failed to connect. |
|
Please just do a define of tuya_cloud setup ... Post the log output and the readings. If you get failed to connect, you need to check the clientid, secret, username and password again. |
|
just deleted all tuya Module related. The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
2021-09-27 22:35:15,457 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1632774915427}` When did you create the tuya iot platform project? It needs to be created later than May 2021. If you just created it a few days ago you need to check clientid/secret, username/password again. |
|
As username I take "Spitzname" from the Tuya App, thats the only name I have, if i take my Email, it's colored inside definition editor and does not work either |
|
Could it be that you registered with Google instead of registering an account? |
|
IOT platform project is now about 1 week old |
|
You need to register an account and use the email address. You can find the username here (in my case the email address domi****.com - of course you need to use the full one)
|
|
clientID/secret is thhis in the overview, correct? Access ID/Client ID: checked |
yes |
|
if I use this Mail, in fhem definition the portion @gmail is marked in red, as well the last character of my Password which is this:& is marked in orange. as result no new logentry !! Do I need to do the registration with another Mailprovider? |
|
no, it's actually not fhem which is marking it red, it might be just your browser which is doing a spellcheck. |
|
is the status "ready" now? |
|
Hi, sorry neede to leave yesterdy night. No it is not. Access ID and AccessSecret per copy paste added in. local_pybinding is status opened the tuya modul things i deleted as suggested no clue if important but Tuya app is open and the Tuya lightbulp is online |
|
I get crazy, I defined a second connector, same parameter all put in by copy paste and it works. ok, so nice that this seems to be done, but how to get now the new device. IT should be autoatic created but there is nothing. Thats my lighbulp, but how to define it? |
|
it is defined automatically. Try to restart fhempy (Pythonbinding_15733) as it will load all devices from the cloud again. |
|
ok, i restarted, the connector goes into Connecting and after a while to PytonBinding timeout. fhempylog says and fhemlog says |
|
Have you updated to the latest version? Timeout should have been fixed since about 1 or 2 weeks. Please do an update command in FHEM and restart FHEM afterwards. |
|
ok updated and restarted, no new device, restart pybinding again, no new device |
|
Please post the fhempy log with tuya_cloud setup device verbose=5. Do a restart after that to have a clean log. |
|
Can you please try I think the bug might be the length of the name. |
|
Ok "-" is the character which isn't supported in FHEM. I'll update fhempy to replace that one. |
|
Please do and wait till update is finished. It's finished when local_pybinding is opened again. This might take up to some minutes. After that your device should be available. |
|
Hurra, it works 🥇 Thats super cool now |
|
Perfect 👍 |
Hi, I have some trouble with Tuya as well as with Tuya Cloud. Likly due to all this ID I strugle to use the right one.
in Tuya IOT Platform I am able to link to my Tuya App, which is afterwards visible from both ends ( IOT Platform as well as inside the App) as a result I can see a UID inside IOT Platform
However I am not able to see the Device which is visible and function with no problem inside Tuya App. I guess here is already the Error.
Inside the Tuya App there is a Virtuell-ID, and IP, a MAC and the TimeZone Europe/Berlin.
Inside IOT Patform the Device Management is on Western Europe ( after adding Central Europe the Device is visible inside IOT Platform)
in fhem tuya_system shows "ready" but no device is found
likly the DeviceID used is wrong, it is neither the Virtual ID inside the Tuya App, nor the UID of the linked Tuya App.
In the individual Device setup I struggle to identify the Product-ID and I do not get the difference of DEVICE_ID and LOCAL_KEY
Now i struggle to see what to do next.
I hope you have a hint for me. Many Thanks.
The text was updated successfully, but these errors were encountered: