Problem logging into SmartLife and Tuya

I’m having trouble linking my Tuya and Smartlife accounts back to HR; I keep getting an error message saying the username is incorrect and the password is wrong. This happens with different accounts.

1 Like

I’ve the same problem

1 Like

I am in the same situation.my region is in EU. i change my password in tuya an now my homeremote refuse to accept my new password. so far was working because my acount was old and allredy token with homeremote. when i change password i think new API activated. i made a new acount to US region and is the same problem, token error user and pass not accepted.

hello,

I need a help, I have one project with tuya devices, working with smartlife app in my costumer, i try use the Home Remote platform for release for my customer one only app. I did this in the past ( 3 or 4 years a go), but now I have a problem with authentication.

I am experiencing an issue connecting Smart Life / Tuya accounts to Home Remote Designer version 4.5.0.0.

Environment

  • Home Remote Designer: 4.5.0.0
  • Windows PC
  • Internet connection working normally
  • Smart Life mobile app working normally
  • Tuya cloud endpoints reachable

Issue

When attempting to add a new Smart Life / Tuya device provider, Home Remote returns:

1 Get accesstoken failed.

2 Username or password error!

Tests performed

Test 1 - Existing Smart Life account

  • Existing customer Smart Life account
  • Verified email and password
  • Login works correctly in Smart Life mobile app
  • Home Remote returns:

1 Get accesstoken failed.

2 Username or password error!

Test 2 - New Smart Life account

  • Created a brand-new Smart Life account
  • New email address
  • Simple password
  • No devices associated
  • Home Remote returns exactly the same error

Test 3 - New Home Remote project

  • Created a completely empty project
  • Added a new Smart Life provider
  • Same error

Test 4 - Different countries

Tested:

  • United States
  • Brazil
  • Germany / Europe

Same result.

Test 5 - Network validation

Verified:

  • Internet connection is working
  • Smart Life mobile app works correctly
  • Tuya endpoints are reachable from the PC
  • Home Remote can contact Tuya servers

Additionally, after multiple attempts Home Remote returns

1 you cannot auth exceed once in 180 seconds

which indicates communication with Tuya servers is occurring.

Conclusion

The issue does not appear to be related to:

  • Username
  • Password
  • Smart Life account
  • Project configuration
  • Local network
  • Internet connectivity

It appears the Smart Life / Tuya authentication mechanism used by Home Remote Designer 4.5.0 may no longer be compatible with the current Tuya authentication service.

Could you please confirm if:

  1. Smart Life / Tuya integration is still supported in version 4.5.0?
  2. There is a known authentication issue with Tuya accounts?
  3. There is a workaround or updated plugin available?

Thank you.

i have the same issues. Try like you different ways to connect to server tuya.
if you change password to tuya acount or make a new one, you activate a new protocol connection that i think is no more compatibile with home remote.
in the end, i stop using tuya plugin and switch to nodered that receive mqtt commands from homeremote and send to tuya device with tuya flow.

1 Like

Tuya Cloud Plugin for The Home Remote – Development Status

I’m currently working on a new Tuya Cloud plugin for The Home Remote, mainly because Tuya access has become a problem for a number of THR users.

The basic cloud connection is now working successfully. The plugin can authenticate directly with the current Tuya Cloud API using HMAC-SHA256, obtain an access token, and communicate with the current /v1.0/iot-03/ device API.

Current test status:

  • SHA-256 / HMAC-SHA256 implementation: PASS
  • Tuya Cloud authentication and access token: PASS
  • Device information request: PASS
  • Device functions/status discovery: currently being tested
  • Device control: not yet tested with the new API

My current test device is a Trotec PAC 3501 S portable air conditioner . Tuya already identifies the device correctly through the new API. It was offline during the latest test, so the next step is to repeat the function/status discovery while the device is online.

Important for anyone interested in testing the plugin later:
The plugin uses the official Tuya Cloud API, so you will need a Tuya Developer/Cloud account and a Tuya Cloud project . The project provides the Access ID (Client ID) and Access Secret required by the plugin.

If you are interested in testing the plugin when the first version becomes available, you can already create your Tuya Developer account and Cloud project in preparation.

The final goal is not to create a plugin only for this particular Trotec unit. I would like to make it as generic as possible for Tuya devices in THR.

For the public version, Tuya credentials will not be hard-coded. Access ID, Access Secret and other required information should be configurable through the THR plugin settings. The plugin and documentation will also be completely in English.

So it is not ready for release yet , but the most difficult first part — establishing authenticated communication with the current Tuya Cloud API — is now working.

Kalle

2 Likes

Tuya Cloud Generic Plugin for The Home Remote

I have been working on a generic Tuya Cloud plugin for The Home Remote (THR).

The main goal is to avoid creating a separate THR plugin for every individual Tuya device. Instead, the plugin connects to the Tuya Cloud, automatically discovers the devices linked to your Tuya/Smart Life account, reads their Tuya Data Points (DPs), and creates the appropriate devices, attributes and capabilities in The Home Remote.

Current development version:

Tuya Cloud Generic 1.9 R20 R2

The plugin is still under development, but the basic Tuya Cloud connection, automatic device discovery, live status polling and several bidirectional controls are already working with real hardware.


1. Requirements

You need:

  • The Home Remote
  • A Tuya Smart or Smart Life account
  • At least one compatible Tuya device
  • A Tuya Developer account (free to create)
  • A Tuya Cloud Project
  • Tuya Access ID
  • Tuya Access Secret
  • The correct region for your Tuya account: EU or US

Your Tuya devices should already be installed and working in the Tuya Smart or Smart Life app before setting up the THR plugin.

Useful Tuya links:

Tuya Developer Platform:

Tuya Cloud Development:
https://developer.tuya.com/en/cloud-development

Tuya Cloud API Documentation:

Tuya Developer Documentation Center:


2. Create a Tuya Developer Account

Go to:

Create a Tuya Developer account. The account is free to create.

After logging in, go to the Cloud Development section and create a new Cloud Project.

Tuya Cloud Development:

https://developer.tuya.com/en/cloud-development

For the development method select:

Smart Home

Select the Data Center that corresponds to the region of your Tuya/Smart Life account.

It is important that your Cloud Project and your Tuya/Smart Life account use the correct region.

You can check the region of your account in the Tuya/Smart Life app under:

Me → Settings → Account and Security → Region


3. Get the Access ID and Access Secret

Open your Cloud Project in the Tuya Developer Platform.

In the project authorization information you will find:

Access ID

and

Access Secret

These two values are required by the THR plugin.

Keep your Access Secret private.

For additional information about Tuya Cloud development and APIs:


4. Link Your Tuya / Smart Life Account

Your Smart Life or Tuya account must now be linked to the Cloud Project.

In your Tuya Cloud Project, open the device/account linking section and select the option to link an app account.

Tuya will display a QR code.

Open the Tuya Smart or Smart Life app on your phone and scan this QR code.

After successful linking, the devices from your Tuya account should become available to the Cloud Project.

The THR plugin can then discover them automatically.


5. Install the Plugin in The Home Remote

Add the .plugin file to your THR project and add the plugin in The Home Remote Designer.

Open the plugin Settings.

Enter:

Access ID:
Your Tuya Cloud Access ID

Access Secret:
Your Tuya Cloud Access Secret

Region (EU or US):
Enter EU for European accounts or US for US accounts.

There is no need to manually enter individual Tuya Device IDs.

The plugin discovers the devices automatically.


6. IMPORTANT – Synchronize Devices

After adding the plugin and entering your Access ID, Access Secret and Region, run:

Synchronize Devices

in The Home Remote Designer.

This step is important.

The plugin discovers the Tuya devices and analyzes their available Data Points and capabilities during synchronization.

Run “Synchronize Devices” after the plugin has been configured so that all discovered attributes and capabilities become available in THR.

If you add a new Tuya device later, or a future plugin version adds support for additional attributes, run Synchronize Devices again.

If a device is visible but expected attributes are missing, Synchronize Devices should be one of the first things to check.


7. Automatic Device Discovery

When the plugin connects to Tuya, it searches for devices associated with the linked Tuya/Smart Life account.

For every discovered device it can retrieve information including:

  • Device name
  • Device ID
  • Product information
  • Things Data Model
  • Available properties
  • Read/write permissions
  • Current values
  • Raw Tuya Data Points

The plugin analyzes these Data Points and exposes the functions it recognizes.

This is important because Tuya devices do not all use exactly the same set of DPs.

For example, one device may use:

switch_led

while another device may use:

switch

or another device-specific power DP.

The generic plugin attempts to map these Tuya functions to useful THR capabilities and attributes automatically.


8. Native THR Capabilities

Where a reliable mapping is possible, the plugin uses native The Home Remote capabilities.

For example, my currently tested Trotec air conditioner exposes the following native THR capabilities:

  • Switch
  • TemperatureSetpoint
  • Temperature
  • Humidity

This means normal THR controls such as a SwitchTile can be used.

You do not have to create a button that sends a raw Tuya command such as:

Power = true

Instead, a normal THR Switch can simply use:

On

and

Off

The plugin performs the translation between THR and Tuya.


9. Supported Device Families

The current generic detection includes Data Points commonly found in a number of Tuya device families.

Climate / Air Conditioning

Examples of supported functions include:

  • Power
  • Current temperature
  • Temperature setpoint
  • Current humidity
  • Target humidity
  • Operating mode
  • Fan speed
  • Swing
  • Sleep mode
  • Timer
  • Temperature scale
  • Fault status

Fans / Air Purifiers

Detection includes:

  • Fan switch
  • Fan speed
  • Fan mode
  • Air quality / AQI
  • Filter information
  • Filter reset
  • PM2.5
  • VOC / TVOC
  • CO2

Lights / Dimmers

Detection includes:

  • switch_led
  • Brightness
  • Color temperature
  • Color data
  • Work mode

Smart Plugs / Switches / Energy Monitoring

Detection includes:

  • Switch
  • Current
  • Voltage
  • Power
  • Energy
  • Countdown

The plugin specifically distinguishes between a Boolean power switch and an actual electrical power measurement.

Sensors

Detection includes:

  • Battery percentage
  • Battery state
  • Door/window contact
  • Motion / PIR
  • Illuminance / Lux
  • Temperature
  • Humidity

Covers / Blinds / Curtains

Detection includes:

  • Open / Close / Stop control
  • Target position
  • Current position
  • Movement state

Safety Sensors

Detection includes:

  • Smoke
  • Gas
  • Water leak / flood
  • Tamper
  • General alarm state

Door Locks

Initial generic status detection includes:

  • Lock state
  • Motor state
  • Door state
  • Battery
  • Unlock method

For security reasons, generic lock control has not been enabled without testing against actual lock hardware.


10. Tested Hardware

At the moment my primary physical Tuya test device is:

Trotec PAC 3501 S Air Conditioner

The plugin automatically discovers the device and its Tuya functions.

The device currently provides 14 raw Tuya properties, including functions for power, temperature, humidity, target humidity, operating mode, fan speed, sleep mode, swing, timer and fault status.

The following functions have been practically tested:

Automatic Device Discovery

PASS

The Trotec is discovered automatically.

No manual Device ID is required.

Live Status Polling

PASS

Changes are read back from the Tuya Cloud and updated in THR.

Native THR Switch Control

PASS

Using the native THR Switch capability:

On switches the air conditioner on.

Off switches the air conditioner off.

The actual device responds immediately and its state is reported back to THR.

Fan Speed Control

PASS

The Trotec uses the Tuya DP:

windspeed1

The available values are:

1 = High

2 = Medium

3 = Low

The plugin exposes this function through:

FanSpeedGeneric

Changing the value from THR has been practically tested and successfully changes the fan speed of the real air conditioner.

Temperature and Humidity

The device reports its temperature and humidity values to THR.

Target Humidity

The Tuya:

humidity_set

DP is automatically detected and exposed as:

TargetHumidity

Temperature Scale

The Tuya temperature-unit DP is automatically detected and exposed as:

TemperatureScale


11. Raw Tuya Data Points

The plugin intentionally keeps raw Tuya information available in addition to the semantic THR attributes.

This is useful for devices or functions that have not yet been mapped.

For example, raw properties can be exposed as DP_... attributes.

This makes it possible to inspect previously unknown Tuya devices and add support for new Data Points without creating an entirely separate plugin for each device.


12. Read / Write Safety

The plugin checks the Tuya Things Data Model before sending generic write commands.

A property must be reported as writable before the generic write path will send a command.

The plugin also validates supported values where Tuya provides the necessary metadata.

This is particularly useful for Enum properties such as fan speeds.

For example, the tested Trotec fan-speed DP reports the allowed values:

1, 2, 3

The plugin can therefore validate the value before sending the command to Tuya.


13. Tested vs. Implemented

There is an important distinction between implemented support and practically tested support.

The functions described above for the Trotec PAC 3501 S have been tested against real hardware.

Support for many other Tuya device families has been implemented based on Tuya Data Point definitions, but I currently do not own physical examples of all of these devices.

Therefore support for devices such as:

  • Tuya lights
  • Smart plugs with energy monitoring
  • Motion sensors
  • Contact sensors
  • Curtains / blinds
  • Smoke detectors
  • Gas detectors
  • Water leak sensors
  • Door locks
  • Air purifiers

should currently be considered:

Implemented – hardware testing still required

If somebody has one of these devices and would like to test it, the plugin logging should make it relatively easy to determine which Data Points the device provides and whether an additional mapping is required.


14. Troubleshooting

If no devices are discovered, check the following first:

  • Is the Access ID correct?
  • Is the Access Secret correct?
  • Is the correct EU or US region entered?
  • Is the Tuya/Smart Life account linked to the Cloud Project?
  • Are the devices visible in the linked Tuya/Smart Life account?
  • Does the Cloud Project have the necessary device permissions?
  • Did you run Synchronize Devices in The Home Remote Designer after configuring the plugin?

If authentication works but no devices are found, check the selected Tuya Data Center and account region.

If the device appears in THR but some attributes are missing, run:

Synchronize Devices

again.

This is especially important after installing a newer version of the plugin that adds additional device capabilities or attributes.

Useful Tuya documentation:


15. Current Status

Current development version:

Tuya Cloud Generic 1.9 R20 R2

At this point the plugin has working:

  • Tuya Cloud authentication
  • Automatic device discovery
  • Automatic Data Point discovery
  • Things Data Model analysis
  • Automatic THR device creation
  • Automatic attribute detection
  • Native THR capability mapping where appropriate
  • Live status polling
  • Generic read/write validation
  • Bidirectional device control

With the available real test hardware, both native Switch On/Off control and Fan Speed control have been successfully tested from The Home Remote through the Tuya Cloud to the physical device.

The next major step is testing the existing generic mappings against more real Tuya hardware.

If anyone has Tuya lights, plugs, sensors, blinds, air purifiers or other Tuya devices and would like to test the plugin, additional real-world test results would be very useful.

Tuya_Cloud_Generic_1_9_R20_R2.plugin (127.9 KB)

2 Likes

I don’t have SmartLife/Tuya but, great to see this! Nice work!

Kalle,
absolute great work! Excellent!
As I try for some days to find out the sync doesn’t work anymore, I found this solution.
Immediately I started to test but there is maybe a subscription error on Tuya development?
The console.log shows this:
TUYA TOKEN: PASS
Tuya access token received successfully.

AUTOMATIC DEVICE DISCOVERY START
READ-ONLY: No device commands will be sent.

DOCUMENTED DEVICE DISCOVERY DIAGNOSTIC 1.2 R3 START
READ-ONLY: No device commands will be sent.

DOCUMENTED DISCOVERY PROBE: GET DEVICE LIST V2
GET /v2.0/devices
TUYA API HTTP STATUS: 200
TUYA API RESPONSE RECEIVED: YES
DOCUMENTED DISCOVERY RESULT: REJECTED
TUYA ERROR CODE: 28841002
TUYA ERROR MESSAGE: IoT Core service subscription has expired.

DOCUMENTED DISCOVERY PROBE: ASSOCIATED APP USER DEVICES
GET /v1.0/iot-01/associated-users/devices
TUYA API HTTP STATUS: 200
TUYA API RESPONSE RECEIVED: YES
DOCUMENTED DISCOVERY RESULT: REJECTED
TUYA ERROR CODE: 28841002
TUYA ERROR MESSAGE: IoT Core service subscription has expired.
DOCUMENTED DEVICE DISCOVERY DIAGNOSTIC 1.2 R3 END

GENERIC STATUS / FUNCTION DISCOVERY START
READ-ONLY: No device commands will be sent.

GENERIC STATUS / FUNCTION DISCOVERY 1.4 START
GENERIC DISCOVERY: No automatically discovered devices are cached.
GENERIC STATUS / FUNCTION DISCOVERY 1.4 END

RAW DP DISCOVERY START
READ-ONLY: Things Data Model + Shadow Properties only.

RAW DP DISCOVERY 1.5 START
RAW DP DISCOVERY: No automatically discovered devices are cached.
RAW DP DISCOVERY 1.5 END

THR DEVICE SYNCHRONIZATION START
THR DEVICE SYNCHRONIZATION: No discovered Tuya devices are cached yet.
Tuya Cloud Generic disconnected.

I think this comment is important:
TUYA ERROR MESSAGE: IoT Core service subscription has expired.

is it necessary to have this subscription?
If yes there will be a bottleneck for the future because this free subscription is valid only 1 month.

Looking forward to solve this issue.
LG, Jiri

Post:
After extending the IoT core subscription the sync does work!
The question is this:
I have more than 50 devices on Tuya but the plugin finds only 20 of them.
From this 20 there are devices found of type:
Temperature sensors: BTH11-BLE, BTH01Y-BLE
Switches: QS-WIFI-S10-C03, T34-MINI, Smart Plug, Aubess Smart Switch 1-gang
Heaters: Inverter Pool Heat Pump
Smart meter: Smart meter
RF Switches controled by an IRRF-hub

What are the criteria for receiving the devices from Tuya?
Does a limitation of devices per call exist?

LG, Jiri

Hi Jiri,

Thank you very much for your feedback and for testing the plugin!

You are absolutely right. Error 28841002 indicates that your Tuya IoT Core subscription has expired.

The good news is that Tuya currently allows developers to request an extension of the free IoT Core trial.

Please try the following:

  1. Log in to https://iot.tuya.com/
  2. Navigate to Cloud → Cloud Services → IoT Core → My Subscriptions .
  3. Find your expired IoT Core subscription.
  4. Select Extend Trial Period and submit the request.
  5. Once approved, restart the plugin and try device synchronization again.

According to Tuya’s documentation, approval normally takes one or two business days.

Your log confirms that the plugin successfully authenticates with Tuya Cloud. The device discovery requests are rejected because the IoT Core subscription has expired, not because of an authentication or signing problem.

However, you have raised an important point regarding long-term usability. The plugin currently depends on Tuya Cloud API access, and free trial extensions are subject to Tuya’s policies and usage limits.

I will also consider adding a clearer diagnostic message for expired IoT Core subscriptions in a future plugin version.

Please let me know whether synchronization works after renewing the trial.

Best regards,
Kalle

[quote=“jgibron, post:9, topic:13522”]

Moin Kalle,

After extending the IoT core subscription the sync does work!
The question is this:
I have more than 50 devices on Tuya but the plugin finds only 20 of them.
From this 20 there are devices found of type:
Temperature sensors: BTH11-BLE, BTH01Y-BLE
Switches: QS-WIFI-S10-C03, T34-MINI, Smart Plug, Aubess Smart Switch 1-gang
Heaters: Inverter Pool Heat Pump
Smart meter: Smart meter
RF Switches controled by an IRRF-hub

What are the criteria for receiving the devices from Tuya?
Does a limitation of devices per call exist?

LG, Jiri
[/quote]

Moin Kalle,
I did already a testing with the new IoT core subscription.

After extending the IoT core subscription the sync does work!

The question is this:
I have more than 50 devices on Tuya but the plugin finds only 20 of them.
From this 20 there are devices found of type:

Temperature sensors: BTH11-BLE, BTH01Y-BLE
Switches: QS-WIFI-S10-C03, T34-MINI, Smart Plug, Aubess Smart Switch 1-gang
Heaters: Inverter Pool Heat Pump
Smart meter: Smart meter
RF Switches controled by an IRRF-hub

What are the criteria for receiving the devices from Tuya?
Does a limitation of devices per call exist?

LG, Jiří

Hi Jiri,

Great news! I’m glad that extending the IoT Core subscription solved the synchronization issue.

Thank you also for testing the plugin with more than 50 devices. This is extremely helpful!

I checked the official Tuya API documentation, and I think we have identified the reason why only 20 devices are discovered.

The endpoint currently used for automatic discovery supports pagination.

Tuya provides the parameters size, has_more, last_row_key, and total to retrieve devices across multiple pages.

It is therefore very likely that the plugin currently processes only the first page of results.

The discovery itself is designed to be generic, so the device types you mentioned are not intentionally excluded. However, discovering a device does not necessarily mean that all its functions are supported.

I will check the pagination handling and prepare an improvement so that all available pages can be retrieved.

Thanks again for your valuable feedback!

Best regards,
Kalle

Ok,
I believe we have also identified why only 20 of your 50+ devices were discovered.

The Tuya API supports pagination , but the previous plugin version only processed the first page of results.

I’ve now implemented pagination support in Tuya Cloud Generic 1.9 R20 R3 .

What’s new:

  • Automatic retrieval of additional device pages
  • Duplicate device detection
  • Improved discovery logging
  • Protection against endless pagination loops

The new version has been successfully tested with my own Tuya device, and the existing functionality continues to work.

However, I only have one device available for testing, so I haven’t been able to verify multiple pages yet.

Could you please test R20 R3 with your 50+ devices?

It would be especially helpful if you could share these log entries:

  • TUYA DISCOVERY PAGE
  • TUYA DISCOVERY PAGINATION END
  • DISCOVERED DEVICE COUNT

Please note that this is still a test version.

I’ve attached the updated plugin below.

Thanks again for your valuable feedback and testing!

Best regards,
Kalle
Tuya_Cloud_Generic_1_9_R20_R3.plugin (131.0 KB)

1 Like

Moin Kalle,
i just started the test of the R3 plugin.

This is the result from console.log:
AUTOMATIC DEVICE DISCOVERY START
READ-ONLY: No device commands will be sent.

DOCUMENTED DEVICE DISCOVERY DIAGNOSTIC 1.2 R3 START
READ-ONLY: No device commands will be sent.

DOCUMENTED DISCOVERY PROBE: GET DEVICE LIST V2
GET /v2.0/devices
TUYA API HTTP STATUS: 200
TUYA API RESPONSE RECEIVED: YES
DOCUMENTED DISCOVERY RESULT: REJECTED
TUYA ERROR CODE: 1100
TUYA ERROR MESSAGE: param is empty

DOCUMENTED DISCOVERY PROBE: ASSOCIATED APP USER DEVICES
GET /v1.0/iot-01/associated-users/devices
TUYA API HTTP STATUS: 200
TUYA API RESPONSE RECEIVED: YES
DOCUMENTED DISCOVERY RESULT: SUCCESS
TUYA DISCOVERY PAGE 1: received=20 | unique=20 | has_more=true | total=67
TUYA API HTTP STATUS: 200
TUYA API RESPONSE RECEIVED: YES
TUYA DISCOVERY PAGINATION: next page failed; retaining 20 discovered device(s).
TUYA ERROR CODE: 1004
TUYA ERROR MESSAGE: sign invalid
TUYA DISCOVERY PAGINATION END: 20 unique device(s).
DISCOVERED DEVICE COUNT: 20
THR DEVICE CACHE UPDATED: 20 device(s)

The number 67 is correct. That is the count of my devices in Tuya at the time.

Hope this helps.

LG, Jiří

Hi Jiří,

Thank you for the quick test and the detailed log!

Your results are extremely helpful. We now know that Tuya correctly reports all 67 devices , but the second page request fails with error 1004 – sign invalid .

I believe I’ve identified the issue: the query parameters used for pagination were not in the correct order for Tuya’s HMAC signature calculation.

I’ve corrected this in Tuya Cloud Generic 1.9 R20 R4 – Pagination Signature Fix .

What’s changed:

  • Corrected query parameter ordering for pagination requests
  • Ensured the signed URL matches the requested URL
  • Kept all existing functionality unchanged

I’ve attached the updated R20 R4 test version.

Could you please test it again with your 67 devices?

If possible, please share the following log entries:

  • TUYA DISCOVERY PAGE
  • TUYA DISCOVERY PAGINATION END
  • DISCOVERED DEVICE COUNT

Hopefully, we should now see all 67 devices across multiple pages!

Please note that this fix has not yet been verified with a multi-page device list.

Thanks again for your support and patience. Your testing is helping make this plugin much more reliable for everyone.

Best regards,
Kalle

Tuya_R20_R4.plugin (131.1 KB)

Kalle,

The R4 plugin do ad all of my devices listed in Tuya. Great!! :+1:

Now I did some testing with one of the devices: Temperature sensor
This sensor has this attributes:
Status
Online
Model
Category
TuyaDeviceId
TemperatureScale
BatteryPercentage
LockBattery
DP_temp_current
DP_humidity_value
DP_battery_percentage
DP_temp_unit_convert
DP_temp_calibration
DP_hum_calibration

Next I modify the TemperatureSensorTile.xaml
The label bind to the value was set to: {Binding @Device.DP_temp_current}
To make sure I can read out the values without any template, I create another 3 labels and bind them directly to:
DP_temp_current
DP_humidity_value
DP_battery_percentage

During the run of THR there is no value to see.

Hi Jiří,

IMPORTANT – Security warning!

I just noticed that your uploaded R4_console.log 3.txt contains sensitive Tuya authentication information, including your access token, refresh token, and user ID .

Please delete the log file from the public forum immediately!

I strongly recommend revoking or regenerating the affected Tuya credentials/tokens as a precaution, since the refresh token was also exposed.

I’m sorry about this. The plugin should never write authentication tokens to the console log. This is an issue on my side, and I will fix it in the next version.

The good news is that your pagination test was successful, and we have also identified some useful information about the missing temperature sensor values.

For now, please don’t upload any additional unfiltered logs. I’ll make sure the next plugin version removes sensitive authentication data from the output.

Thank you again for your help, and sorry for the inconvenience!

Best regards,
Kalle

Hi Jiří,

I’ve uploaded R20 R5 – Safe Logging.

This version fixes the authentication token logging issue. The working pagination functionality remains unchanged.

I’ve also successfully tested R5 locally.

Could you please do the following?

  1. Install R20 R5 and restart The Home Remote.

  2. Check whether all your Tuya devices are still discovered.

  3. Open your temperature sensor (BT_terasa).

  4. Test the following binding in a text label:

    {Binding @Device.DP_temp_current}

  5. Check whether the temperature value appears.

  6. Please send me the console log section starting with THR DEVICE SYNCHRONIZATION START and ending with THR DEVICE SYNCHRONIZATION END, including the entries for BT_terasa.

I tested the exact same binding with my own Tuya device, and it correctly displays the temperature value.

This will help us determine why your sensor values are not appearing.

Important: Please remove the previous R4 log attachment from the public forum if you haven’t already done so. It contains sensitive authentication information. Also, please review any new logs for sensitive data before uploading them.

Thanks again for your help!

Best regards,
Kalle
Tuya_Cloud_Generic_1_9_R20_R5.plugin (131.4 KB)

Thank you for the warning. I was not sure before if there is any secret inside. Now I know.
The test I did with R5 does not change the result. Still no value there.
The mentioned section THR DEVICE SYNCHRONIZATION START does not exist.

The Device to test is a BLE device with a hub needed to run.

LG, Jiří