Hello !!
I am from France and I would like to thank all the contributors who share their knowledge here, it has helped me a lot!
I will try to explain my problem as clearly as possible.
My problem is I have lots of difficulties to get its data.
I can retrieve data but it is very random.
Example, I analyse the log of the Tuya iot site, I see my temperature change 3 times in one hour (19Ā°C, 19,5Ā°C, 20Ā°C) (each time the sensor connects/disconnects to the wifi)
But on my server mqtt doesnāt get all the values directly, for example only the value 19,5Ā°C. Even after 3 hours, I still have 19.5Ā°C on openhab.
Explanation:
The sensor only stays connected for less than 2 seconds.
The TuyAPI tries to connect to devices at start-up. If a device is not found, the PLC tries again every 10 seconds. Of course, I am very likely to miss the moment when the temperature sensor is connected (less than 2 seconds).
My ābad solutionā:
In the api files, I have decreased the retry time before connecting after a failure from 10sec to 100msā¦ Itās works but itās no very cleanā¦
So, how can I manage this type of device which is not always connected to wifi with tuyamqtt ?
Maybe for example : get the connection packet of the device when it connect to wifi to āwake-upā TuyaAPI and get MQTT channels data ?
Thank you to take the time to read me. I hope that is clear. Donāt hesitate to ask me for more information.
Regards.
Here is a screenshot with more explanation with tuyamqtt in debug mode. No problem with devices that are always connected to Wifi (like my switches).
But the problem is when a device is only connected for only 2secondes to send its data to the cloud.
You can see I have decrease the reconnection time to 100ms. But by befault it is 10sec.
See with this bad solution, the api manages to connect when the device connects, sends its data and then disconnects.
But how do you do this without trying to connect to it all the time?
There are similar issues reported but no solution provided as far as I can see. We can do a PR on tuya mqtt once they have a solution in tuyapi. But there is no guarantee that it will be fixed soon (or ever).
I will do some research if there is another possibility to catch the values of those devices. Imho the states delivered by the device has to be retained somewhere. Otherwise you wonāt be able to see the values in the tuya app either
Why I can get the values from Tuya App ? Because when the device connect to the wifi, it send the data to the Tuya Cloud.
And the Tuya App ask data to the Tuya Cloud.
The goal of tuyapi is to intercept the communication between device and its cloud, and transform them into MQTT data for my MQTT server and Openhab.
It would be necessary to succeed in intercepting the wifi connection requests of a device
The project of @tsightler is based on tuyapi afaik. But maybe your device falls under this case:
TuyAPI does not support sensors due to the fact that they only connect to the network when their state changes. There are no plans to add support as itās out of scope to intercept network requests.
To be honest, I prefer Zigbee sensors - they are just more reliable. Recently I added Lora-based sensors as their signal range is absolutely impressive!
If you want to stick with the sensor, I could only think of requesting the values via the Tuya Open API from the cloud. But this will of course break the original idea of controlling/reading your devices locally
@Roms , @J-N-K has a Tuya Binding that I have been trying and it works quite well. Unfortunately, I only have always-on devices in my house, but i was wondering if the binding would work with battery powered sensors.
The Binding is quite straightforward, to install, so I just wanted to mention it in case youād like to try and see if your battery-powered devices work with it. if they do, it would be great to know.
I am also a long time AgentK/tuya-mqtt user (In fact, currently, i have both AgentK solution and smarthome/j solutions installed), but i really liked the idea of having a binding that is easily installable from a repository, and that automatically detects all your devices. It is also great if your openhab setup fails and you need to rebuild, since is much less configuration.
If you already have a tuya iot project configured properly, the binding configuration consists on little more than entering your api key and secret. The binding will automatically discover your tuya devices by accessing the tuya iot project. The docs explain it quite well.
In my case, I found that defining an aditional on/off channel for eaxh device worked better with how
I define my light groups. But that is optional, and also very straightforward to do.
I did not have to remove AgentK/tuya-mqtt solution. In fact, I am running both solutions in parallel right now, since i am still testing.
Let me know how it goes.
Thank you very much @ricardol ! I will test this in a few hours.
Ok so I can continue to use my wifi switches (without battery) with tuyamqtt, and just use the smarthomej binding tuya for my battery powered device. At least for the testā¦
But to be sure : Is the Tuya Cloud access is necessary for each Openhab startup (electrical disconnection/reconnection of my Rpi for example) ?
Or is it only needed for the first binding configuration ?
The idea after that is that I want my devices to be completely disconnected from Tuya Cloud after the first pairing or adding a new device (network setup)
Ok so I can continue to use my wifi switches (without battery) with tuyam-qtt, and just use the smarthome/J binding tuya for my battery powered device. At least for the testā¦
Yes, you can. You can actually use both solutions for everything, they do not conflict with each other in my experience (If the battery operated sensors work with smarthome/J)
But to be sure : Is the Tuya Cloud access is necessary for each Openhab startup (electrical disconnection/reconnection of my Rpi for example) ?
Tuya Cloud connectivity is only necessary for initial discovery. In fact, it is not necessary at all. You could also configure everything manually. Tuya Cloud connectivity is Just more convenient. (With the common exceptions being to add a new device, and when a device gets reset to factory, like, for example, power outages).
I have a problem with Tuya Cloudā¦ The IoT Core trial has expired, so I canāt get my devices keys.
I asked for an extensionā¦ I am waiting for an answer.
But itās annoying because as soon as the license expires, you canāt use tuya-cli wizard for example or retrieve the keys on the Tuya Cloudā¦
Hello @Roms ,
When i configured this, my trial was expired too, but i was still able to read the key and secret from the interface.
Just to be clear, to configure the smarthome/j binding, you do not need the device keys. You need the project key and secret.
You can get that from iot.tuya.com. On the left hand side, click on the Cloud Icon, and you will be presented with a list of your projects. If you click on the project you use for tuya-mqtt, you will be presented with a page that shows your access id and secret in it (Look under āAuthorization Keyā).
When i configured this, my trial was expired too, but i was still able to read the key and secret from the interface.
How do you do that ? From Tuya Website ?
I know 2 methods to get the Id/key of a device:
-Use the API Explorer from Tuya Website and make a Device Informatio request : But it said me I havenāt the permission (trial expired)
-Use the tuya-cli wizard in Openhabian : But it donāt works anymore for now. I donāt know why but I guess it is because of my expired trial ?
Just to be clear, to configure the smarthome/j binding, you do not need the device keys. You need the project key and secret.
I have configured the āprojectā thing with my project Id and Secret, it is online and seems to be fine.
In the documentation it says āThe best way to configure a tuyaDevice is to use the discovery serviceā.
Ok, but how do you use the discovery service?
Nothing seems to discover automatically. When I click on Scan button, it doesnāt detect anything. So I tried to create the ātuyadeviceā thing manuallyā¦
I am just thinking about it nowā¦ but do I need to re-pair my devices with the app to start discovery service of the binding ?
Thanks for your help.
edit : My IoT core licence has been renewed for 6 Month just now.
How do you do that ? From Tuya Website ?
Correct. I get the access ID and secret for the project from iot.tuya.com
I have configured the āprojectā thing with my project Id and Secret, it is online and seems to be fine.
In the documentation it says āThe best way to configure a `tuyaDevice` is to use the discovery serviceā.
Ok, but how do you use the discovery service?
Yes. Once the Tuya cloud thing is online, you just scan for devices, and they show up.
3 Things come to mind:
Make sure that the Data Center, app username, app password, country code and app type are correctly defined according to your specific scenario
In iot.tuya.com, under cloud, got o āLink Tuya App accountā. Is the account linked? If it is, make sure that under āManage Devicesā, you have given the account permissions to handle all the devices. Same Thing with āLink tuya Appā. The easiest think to do is to choose āAutomatic Linkā as devices managment method, and to give āread, write and manageā permissions (I am actually not sure āLink Tuya Appā is needed. This will let you link your custom apps, and unless you have devices in those customs apps, it wonāt serve any purpose for discovery).
Yes you can get the Acess ID and Secret for the Project without needed the Trial Licence.
But, to get the Ip, Local Key, Product Id of a Device, do you need the Trial Licence ?
I know it is not necessary for this Tuya Binding, but I want to know if I can get them manually without the licence.
Yes all is ok for Data Center, app username (email ?), app password, country code and app type.
In tuya.com all is ok, Iāve just checked it : All my 3 devices are linked and have the 3 permissions and are in automatic link.
I will try to unpaired and paired the devices from the Tuya Smart App
@ricardol
I have just trying and it is works, my 3 devices are detected in Paper UI !
I donāt change anything in the setup. The only difference between today and yesterday : My Trial Licence has been renewed this morningā¦
That is not good if the Trial Licence is mandatory each time I have to add a device
My assumption is the discovering service of the binding use the API Explorer of the Tuya Cloud to get IDs.
But to use the API Explorer you need the Tuya Trial Licence (I test it manually yesterday without the Licence, It said me Permission refused because of Trial expired)
Yes you can get the Acess ID and Secret for the Project without needed the Trial Licence.
But, to get the Ip, Local Key, Product Id of a Device , do you need the Trial Licence ?
I know it is not necessary for this Tuya Binding, but I want to know if I can get them manually without the licence.
My Tuya iot account and setup is more than 2 years old. I never renewed or had to upgrade the license. I have added devices lately, and never needed a license either.
Additionally, i have had a lot of power outages, (which sometimes reset your devices), and due to this, i had to re-add several devices to my app, and regenerate the devices.json file for tuya-mqtt, because id and secrets changeā¦i never had a problem doing it.
So, your battery operated devices work? Have you checked that they report properly, and at a periodic rate? Do they appear off line or online most of the time? (I wonder if they āsleepā during measurements, to save battery). If they work, i might be tempted to go ahead and by some door sensors for testingā¦
Ok I trust you ^^
So something is (was ?) wrong with my project or setup ā¦ I donāt know why it didnāt work before. I would try to do it all again with a new project and new tuya count without Trial Licence later.
I am not at home for now so I canāt move the sensor to āchangeā its temperature. At the moment it is offline. When the temperature changes, it will be online for 1 or 2 seconds. I hope this Tuya Binding will capture his data!
I was wondering if there wasnāt a solutionā¦
