Skip to content
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 TS0601 thermostat: “lastupdate” is empty #4147

Closed
TheNON75 opened this issue Jan 9, 2021 · 20 comments
Closed

Tuya TS0601 thermostat: “lastupdate” is empty #4147

TheNON75 opened this issue Jan 9, 2021 · 20 comments
Labels

Comments

@TheNON75
Copy link

TheNON75 commented Jan 9, 2021

Describe the bug

Whenever a config or state update occurs, the "lastupdate" information is always empty.

Steps to reproduce the behavior

Check rest api or websocket
(Referring to the developer, this part is not developed yet)

Expected behavior

filled with correct date time

Screenshots

Environment

  • Host system: (Raspberry Pi / PC / NAS)
  • Running method: (Raspbian / Ubuntu / Home Assistent deCONZ Add-on / Marthoc Docker container / Windows / Virtual Machine)
  • Firmware version: (26xxyy00)
  • deCONZ version: (2.xx.yy)
  • Device: (ConBee I / ConBee II / RaspBee I / RaspBee II)
  • Do you use an USB extension cable: (yes / no) -- only relevant for ConBee I/II
  • Is there any other USB or serial devices connected to the host system? If so: Which?

deCONZ Logs

Additional context

@Smanar
Copy link
Collaborator

Smanar commented Jan 9, 2021

Yep , my fault.
I think there is this bug in all tuya device.

Someone can compile a modification to make a test ?

@Smanar
Copy link
Collaborator

Smanar commented Jan 10, 2021

Ok , have made some tries with @machielw, the problem is found, will be corrected when I will add his device for next beta I think.

#3183

@TheNON75
Copy link
Author

Hi @Smanar,

Thanks for the good news, great work!

@Smanar
Copy link
Collaborator

Smanar commented Jan 10, 2021

And from his test, it solve too a "not reachable" bug.
It s enabled only for him ATM, but will add it for other command too.

@TheNON75
Copy link
Author

Excellent, @Smanar!
What was the not reachable bug in details?

@Smanar
Copy link
Collaborator

Smanar commented Jan 11, 2021

I think it was the same problem, the "lastupdate " was never updated, and after some time the device was marked as "unreachable".

image

@easybeat
Copy link

I think it was the same problem, the "lastupdate " was never updated, and after some time the device was marked as "unreachable".

image

Oh this sounds like a similar problem on TS0601 Radiator TRV. I lose connection with this all the time...is this possible?

@Smanar
Copy link
Collaborator

Smanar commented Jan 19, 2021

Depend of you realy loose the connxion or just have it marked as unreacheable ?
If you still receive information like temperature, yep I think it s same problem, we have soon finished the siren, I will put a link for tries here.

@easybeat
Copy link

easybeat commented Feb 9, 2021

@Smanar I've just updated to 2.09.02 and it looks like on my TS0601 TRV the last updated is still null:

Screenshot 2021-02-09 124118

This is a screenshot from ioBroker. Is there a way to check this in Deconz App?

Thanks

@Smanar
Copy link
Collaborator

Smanar commented Feb 9, 2021

The last update issue is normaly corrected here #4379 (not yet validated)

But I have made a mistake for some TRV on a previous PR too, what is your manufacture name ?

@easybeat
Copy link

easybeat commented Feb 9, 2021

The last update issue is normaly corrected here #4379 (not yet validated)

But I have made a mistake for some TRV on a previous PR too, what is your manufacture name ?

Screenshot_20210209-174534

@Smanar
Copy link
Collaborator

Smanar commented Feb 9, 2021

Arf bad luck :(, I m asking to manup if I can correct it, but ATM you will probably have problem with preset/mode request if you use it.
In worst situation the corrective will be in the beta, just after the stable, the code is already in PR list.

@easybeat
Copy link

easybeat commented Feb 9, 2021

Hey, no problem!! It can wait.

Thanks for your work.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 3, 2021

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Mar 3, 2021
@github-actions
Copy link
Contributor

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

@TheNON75
Copy link
Author

Unstale

@Smanar
Copy link
Collaborator

Smanar commented Jun 30, 2021

This bug is still present ?

@TheNON75
Copy link
Author

I had to revert from the latest version as there was at least one other issue with it, so I cannot tell right now.
In which stable is it fixed? Sorry it is unclear from the above posts.

@Smanar
Copy link
Collaborator

Smanar commented Jul 1, 2021

The last one is enought, long time this issue is "supposed" to be resolved.

@TheNON75
Copy link
Author

I confirm it works in the latest.
(I might need to open a new issue for the "lastseen")

Thank you very much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants