search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.86k stars 30.1k forks source link

Tuya; delayed/missing state updates: Confirmed Tuya Cloud issue, awaiting upstream fix #60034

Closed memphis3 closed 2 years ago

memphis3 commented 2 years ago

The problem

There is a long delay in updating the switch status. When the switch is physically turned on, the switch in the HA turns on and then turns off immediately. Then it takes a few minutes to update the status. These delays appeared after upgrading to HA core ver. 2021.11.4 (HA on Debian)

What version of Home Assistant Core has the issue?

2021.11.4

What was the last working version of Home Assistant Core?

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Tuya (new version)

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tuya/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

awaldram commented 2 years ago

Hi All, Just waiting for final fix I implemented nice workaround, which fits perfectly my needs. I use only few Tuya switches and I decided simply to trigger Tuya integration reload.

Thats surely going to be heavy on the tuya data centers .? everytime you operate a tuya device you force a full status pull for every tuya device you own (scale that up and your getting hundreds of extra requests per user) likely to exasperate the current latency .

Much easier to implement the custom integration tuya-local ... it happily run alongside the core-integration and you just have to change the entities in you automatons.

You can then switch back to the cloud solution once it matures into a usable stable integration (if you wanted to)

bartplessers commented 2 years ago

Much easier to implement the custom integration tuya-local

what do you mean with the "tuya-local" integration? Does there exist an integration that can run only locally ???

vdbosch commented 2 years ago

Local tuya works only with WiFi equipment, not with Zigbee equipment of Tuya. Works great and fast (bit complex to implement) Will solve the current issues for Tuya WiFi equipment and works cloud indipendent. Outlook voor Android downloaden

CrashyNL commented 2 years ago

offtopic: tried local tuya, workes for plugs for me, but never got my Light Bulbs to work with it. I have Action LSC lights (https://www.action.com/nl-nl/p/lsc-smart-connect-slimme-filament-ledlamp4/). Any help with this would also be appreciated!

vdbosch commented 2 years ago

Local Tuya doesn't work with Zigbee ( Action hub) Outlook voor Android downloaden

awaldram commented 2 years ago

Local Tuya doesn't work with Zigbee ( Action hub) Outlook voor Android downloaden

I use Zigbee2mqtt for all my zigbee needs why have multiple hubs .? With HA solid ZHA implementation I'm surprised anyone is fighting with the multiple integrations for devices that would surely be better run under zigbee control from a single controller. Surely with multiple hubs (tuya,hue,trefida etc etc) your out of bandwidth to fit 802.11 2.4gb wifi in .

though getting off topic here .

awaldram commented 2 years ago

Much easier to implement the custom integration tuya-local

what do you mean with the "tuya-local" integration? Does there exist an integration that can run only locally ???

https://github.com/rospogrigio/localtuya 1 and multiple gang switches Wi-Fi smart plugs (including those with additional USB plugs) Lights Covers Fans

https://github.com/make-all/tuya-local

Climate devices HVAC

both will run alongside the Tuya core integration.

leeyuentuen commented 2 years ago

same problem as here: https://github.com/home-assistant/core/issues/60186

zlinoliver commented 2 years ago

Hi guys, we are working hard on fixing slow response issue and will inform everyone once it’s fixed. Sorry for the inconvenience!

damiano75 commented 2 years ago

Hi All, Just waiting for final fix I implemented nice workaround, which fits perfectly my needs. I use only few Tuya switches and I decided simply to trigger Tuya integration reload. I follwed very good thread of Mariusthvdb: https://community.home-assistant.io/t/add-service-integration-reload/231940

I hope this small "manual" targeted for Tuya integration reload help at least few of us. I'm using core-2021.11.5 at the moment.

Here's my live setup:

  1. add to configuration.yaml:
shell_command:
  reload_tuya: | 
    curl -X POST 
    -H "Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyssc3MiOiIzZmQyZTkzNzA0Mjg0MjTtYmUyZjk5ZDVkODkzM2RlNyIsImlhdCI6MTYzNzgyODA4NSwiZXhwIjoxOTUzMTg4Maa1fQ.lOujbx0BaUEmvUEctbsNPltTYlwkaUlmjYAD5dUyAFw" -H "Content-Type: application/json" 
    http://[HA_ip]:8123/api/config/config_entries/entry/e4d06c57be14e2c893d3c416c1dfe58b/reload

where: 1st long string after (Authorization: Bearer) is a long-lived access token created in HA UI > Profile (your name) > create token (at the very bottom of the page) 2nd string before (/reload) is just the entry_id of your tuya integration retrieved from .storage/core.config_entries file in the HA /config directory

  1. create automation with trigger that fits your needs. automation.yaml:
- id: '1637792981074-whatever'
  alias: tuya reload
  description: ''
  trigger:
  - platform: time_pattern
    minutes: '57'
  condition: []
  action:
  - service: shell_command.reload_tuya
  mode: single

Hi, is there a way to trigger an automation when I toggle an entity? I would like to reload the tuya integration some seconds after I toggled the switch, even if HA doesn't see any change in the entity state...

Tamas-Toth-ebola commented 2 years ago

Hi guys, we are working hard on fixing slow response issue and will inform everyone once it’s fixed. Sorry for the inconvenience!

Hi @zlinoliver !

Lot of thanks for your efforts and for the response!

Just some more details about the problem:

Home Assistant know the good states after restert, and also after reinit the integration but later under daily usage it start to become unreliable. Sometimes HA gives back good states (after a switch event) but very slowly (10+ seconds), but sometimes not, is simply lost the actual state.

I hope you can catch the problem, and thanks for it in advance!

leeyuentuen commented 2 years ago

Hi All, Just waiting for final fix I implemented nice workaround, which fits perfectly my needs. I use only few Tuya switches and I decided simply to trigger Tuya integration reload. I follwed very good thread of Mariusthvdb: https://community.home-assistant.io/t/add-service-integration-reload/231940 I hope this small "manual" targeted for Tuya integration reload help at least few of us. I'm using core-2021.11.5 at the moment. Here's my live setup:

  1. add to configuration.yaml:
shell_command:
  reload_tuya: | 
    curl -X POST 
    -H "Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyssc3MiOiIzZmQyZTkzNzA0Mjg0MjTtYmUyZjk5ZDVkODkzM2RlNyIsImlhdCI6MTYzNzgyODA4NSwiZXhwIjoxOTUzMTg4Maa1fQ.lOujbx0BaUEmvUEctbsNPltTYlwkaUlmjYAD5dUyAFw" -H "Content-Type: application/json" 
    http://[HA_ip]:8123/api/config/config_entries/entry/e4d06c57be14e2c893d3c416c1dfe58b/reload

where: 1st long string after (Authorization: Bearer) is a long-lived access token created in HA UI > Profile (your name) > create token (at the very bottom of the page) 2nd string before (/reload) is just the entry_id of your tuya integration retrieved from .storage/core.config_entries file in the HA /config directory

  1. create automation with trigger that fits your needs. automation.yaml:
- id: '1637792981074-whatever'
  alias: tuya reload
  description: ''
  trigger:
  - platform: time_pattern
    minutes: '57'
  condition: []
  action:
  - service: shell_command.reload_tuya
  mode: single

Hi, is there a way to trigger an automation when I toggle an entity? I would like to reload the tuya integration some seconds after I toggled the switch, even if HA doesn't see any change in the entity state...

here is a tutorial to automatic reload https://github.com/home-assistant/core/issues/60390#issuecomment-979797028

KHV8 commented 2 years ago

Hi damiano75

Reload works very well as a workarround. Super easy to integrate into a already existing automation

  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: homeassistant.reload_config_entry
    target:
      entity_id: light.hombli_smart_led_strip
steve1011011 commented 2 years ago

Hi damiano75

Reload works very well as a workarround. Super easy to integrate into a already existing automation

  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: homeassistant.reload_config_entry
    target:
      entity_id: light.hombli_smart_led_strip

You are however, inadvertently putting more pressure on the Tuya servers, so I would refrain from doing this, as you could go against any terms, and go down a road where they will start charging HA users for a more guaranteed service .

Best workaround everyone could do in the meantime, is setup LocalTuya using HACs . Its very simple.

leeyuentuen commented 2 years ago

Hi damiano75 Reload works very well as a workarround. Super easy to integrate into a already existing automation

  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: homeassistant.reload_config_entry
    target:
      entity_id: light.hombli_smart_led_strip

You are however, inadvertently putting more pressure on the Tuya servers, so I would refrain from doing this, as you could go against any terms, and go down a road where they will start charging HA users for a more guaranteed service .

Best workaround everyone could do in the meantime, is setup LocalTuya using HACs . Its very simple.

true to using localtuya, but some of them is still in development like zigbee motion sensor, zigbee temperature/humidity sensors,...

Moustik2002 commented 2 years ago

Hi damiano75 Reload works very well as a workarround. Super easy to integrate into a already existing automation

  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: homeassistant.reload_config_entry
    target:
      entity_id: light.hombli_smart_led_strip

You are however, inadvertently putting more pressure on the Tuya servers, so I would refrain from doing this, as you could go against any terms, and go down a road where they will start charging HA users for a more guaranteed service . Best workaround everyone could do in the meantime, is setup LocalTuya using HACs . Its very simple.

true to using localtuya, but some of them is still in development like zigbee motion sensor, zigbee temperature/humidity sensors,...

zigbee hubs aren't supported too for Local tuya

leeyuentuen commented 2 years ago

Hi damiano75 Reload works very well as a workarround. Super easy to integrate into a already existing automation

  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: homeassistant.reload_config_entry
    target:
      entity_id: light.hombli_smart_led_strip

You are however, inadvertently putting more pressure on the Tuya servers, so I would refrain from doing this, as you could go against any terms, and go down a road where they will start charging HA users for a more guaranteed service . Best workaround everyone could do in the meantime, is setup LocalTuya using HACs . Its very simple.

true to using localtuya, but some of them is still in development like zigbee motion sensor, zigbee temperature/humidity sensors,...

zigbee hubs aren't supported too for Local tuya

The Zigbee hub works in one of the PR branch, but I've tested them with some issues. if one of the Zigbee devices gets a response with the cid key, all the other device with other cid will also get notify.

steve1011011 commented 2 years ago

Hi damiano75 Reload works very well as a workarround. Super easy to integrate into a already existing automation

  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: homeassistant.reload_config_entry
    target:
      entity_id: light.hombli_smart_led_strip

You are however, inadvertently putting more pressure on the Tuya servers, so I would refrain from doing this, as you could go against any terms, and go down a road where they will start charging HA users for a more guaranteed service . Best workaround everyone could do in the meantime, is setup LocalTuya using HACs . Its very simple.

true to using localtuya, but some of them is still in development like zigbee motion sensor, zigbee temperature/humidity sensors,...

zigbee hubs aren't supported too for Local tuya

The Zigbee hub works in one of the PR branch, but I've tested them with some issues. if one of the Zigbee devices gets a response with the cid key, all the other device with other cid will also get notify.

Is zigbee hub support coming then with HA Tuya? ( I have one, registered with Tuya, but just as a backup ) .

leeyuentuen commented 2 years ago

Hi damiano75 Reload works very well as a workarround. Super easy to integrate into a already existing automation

  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: homeassistant.reload_config_entry
    target:
      entity_id: light.hombli_smart_led_strip

You are however, inadvertently putting more pressure on the Tuya servers, so I would refrain from doing this, as you could go against any terms, and go down a road where they will start charging HA users for a more guaranteed service . Best workaround everyone could do in the meantime, is setup LocalTuya using HACs . Its very simple.

true to using localtuya, but some of them is still in development like zigbee motion sensor, zigbee temperature/humidity sensors,...

zigbee hubs aren't supported too for Local tuya

The Zigbee hub works in one of the PR branch, but I've tested them with some issues. if one of the Zigbee devices gets a response with the cid key, all the other device with other cid will also get notify.

Is zigbee hub support coming then with HA Tuya? ( I have one, registered with Tuya, but just as a backup ) .

here is a PR: https://github.com/rospogrigio/localtuya/pull/628

KHV8 commented 2 years ago

Hi damiano75 Reload works very well as a workarround. Super easy to integrate into a already existing automation

  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: homeassistant.reload_config_entry
    target:
      entity_id: light.hombli_smart_led_strip

You are however, inadvertently putting more pressure on the Tuya servers, so I would refrain from doing this, as you could go against any terms, and go down a road where they will start charging HA users for a more guaranteed service .

Best workaround everyone could do in the meantime, is setup LocalTuya using HACs . Its very simple.

Might be true for some usecases, and everybody need to do a setup suited for them.

My automation is triggerede 2 or 3 times on a normal day, maybe less. Im quite sure this is not the reason for any changes in the Tuya setup :-)

DrSpaldo commented 2 years ago

Also getting this issue. I’ve uninstalled the Tuya integration and installed Tuya Local. It was a bit of mucking around but so far it’s working. I may or may not be back to the official integration!

stich86 commented 2 years ago

I don't know if it's related, but i've a similar issue on deCONZ integration. I can power on my lamps but not power off. State on Lovelance is updated but lights remain on. The only way to make it work again is to reload the deCONZ integration.

malosaa commented 2 years ago

@damiano75

works good for now thanks,

lets hope they will fix it, because before it worked normal, just before they did the last tuya update in .3 so 2021.11.2 works normal

SunilKhusal commented 2 years ago

Same issue here too.

gianklug commented 2 years ago

@KHV8 ‘s workarround works for me

zlinoliver commented 2 years ago

Hi guy, sorry again for the inconvenience！We are working hard on fixing the slow response issue, if everything goes well, it should get back to normal by the end of this week. Appreciate for your understanding.

BTW @leeyuentuen the automatic reload method may consume your 26 thousand free API calls of the trial edition faster.

steve1011011 commented 2 years ago

Hi guy, sorry again for the inconvenience！We are working hard on fixing the slow response issue, if everything goes well, it should get back to normal by the end of this week. Appreciate for your understanding.

BTW @leeyuentuen the automatic reload method may consume your 26 thousand free API calls of the trial edition faster.

I don't think people are fully aware of this limit. Granted, it is high, but like you say, not high if people are automating API calls.

If you use up all your free API calls, it's gonna cost you $5000 for the next package up if you need to subscribe to it.

Tamas-Toth-ebola commented 2 years ago

@zlinoliver just one probably new information about the problem.

I made an automation what triggered by the corresponding Tuya socket device on/off 'switching' event, and after 2 sec delay it read back its state. Basically the same workaround what more people suggesed here before but not with timely updates but the switching event itself.

The result is more then interesting.

Switching 'off' the device is working. I see on the HA switch button the lost state but 2 sec later it correct itself with the proper result. But switching 'on' the device not working. In this case the automation simply not triggered. As I feared from the 2 event/2 trigger structure I broke it into 2 discrete automation (the firstly intergrated one). One dedicated to 'on' and the other to the 'off' event. The result is the same. Switching 'off' did reported and triggered the corresponding automation but switching 'on' did not reported.

If I not made a mistake maybe this could be help on you.

Thanks again for your efforts!

AlTyndall commented 2 years ago

I wonder whether this has anything to do with your personal subscription status to the Trial subscription within Tuya IoT Platform. Following on from a message by @waseltzer about Device Status Notification API component, I looked at mine. I had ticked it, but my Trial subscription had lapsed. Background: I tried implementing Tuya Local just over a year ago, and signed up for an IoT Platform account. It looks like your Trial subscription lapses after about a year, so I had to re-subscribe to the Trial again for $0.00. Having done that it looks like my HA switches do now reflect the actual switch status, without even requiring a reload. Worth a shot for anyone still experiencing problems?

Gessink commented 2 years ago

I wonder whether this has anything to do with your personal subscription status to the Trial subscription within Tuya IoT Platform. Following on from a message by @waseltzer about Device Status Notification API component, I looked at mine. I had ticked it, but my Trial subscription had lapsed. Background: I tried implementing Tuya Local just over a year ago, and signed up for an IoT Platform account. It looks like your Trial subscription lapses after about a year, so I had to re-subscribe to the Trial again for $0.00. Having done that it looks like my HA switches do now reflect the actual switch status, without even requiring a reload. Worth a shot for anyone still experiencing problems?

My subscription is still valid until august. I still experience all the issues tho

CrashyNL commented 2 years ago

I wonder whether this has anything to do with your personal subscription status to the Trial subscription within Tuya IoT Platform. Following on from a message by @waseltzer about Device Status Notification API component, I looked at mine. I had ticked it, but my Trial subscription had lapsed. Background: I tried implementing Tuya Local just over a year ago, and signed up for an IoT Platform account. It looks like your Trial subscription lapses after about a year, so I had to re-subscribe to the Trial again for $0.00. Having done that it looks like my HA switches do now reflect the actual switch status, without even requiring a reload. Worth a shot for anyone still experiencing problems?

My subscription is still valid until august. I still experience all the issues tho

Same here (valid until june '22)

bitcrumb commented 2 years ago

I wonder whether this has anything to do with your personal subscription status to the Trial subscription within Tuya IoT Platform. Following on from a message by @waseltzer about Device Status Notification API component, I looked at mine. I had ticked it, but my Trial subscription had lapsed. Background: I tried implementing Tuya Local just over a year ago, and signed up for an IoT Platform account. It looks like your Trial subscription lapses after about a year, so I had to re-subscribe to the Trial again for $0.00. Having done that it looks like my HA switches do now reflect the actual switch status, without even requiring a reload. Worth a shot for anyone still experiencing problems?

You are right! This fixed the issue for me as well. I added the "IoT Core" "Trial Edition" to my cart for $0.00 and clicked "Buy". From that moment on I don't experience any delay or toggling/state issues anymore.

Note that my trial subscription was not elapsed yet (pretty sure, since I only subscribed a couple of months ago), but I could still "resubscribe". Could this have to do with the rename of the product as mentioned at the top of the cloud page:

Service adjustment notice: In order to clarify the content of the cloud service, the Cloud Development Plans has been renamed as the IoT core service from October 15th, and the billing rules have also been adjusted. For more information, please check pricing

@zlinoliver This might be of interest to you as well :)

memphis3 commented 2 years ago

In my case "iot core" doesn't make any changes

titiviking commented 2 years ago

Does make a difference to me, but I have to clarify that I also re-subscribed to the Device Status Notification service (although everything was still valid till June '22).

After the re-subscription, I did restart of my HA as well (may renew access_token for the api, refreshing the underlying session info).

bitcrumb commented 2 years ago

I now notice that the IoT Core trial is only available for 1 month 🤷‍♂️(other subscriptions are also time-limited). Guess I'll be trying Tuya local and/or move away from it.

mrchappell100 commented 2 years ago

I can confirm renewing your IoT core subscription fixes the error :)

mrchappell100 commented 2 years ago

But subscriptions changes from a year to 1 month so keep an eye on that...

OmegaX-NL commented 2 years ago

Does that mean I have to renew it manually every month?

leeyuentuen commented 2 years ago

I think I will focus more on TuyaLocal to be not dependent on Tuya iot platform. If there is one day the "device status notification" is not free anymore, then they will force us to pay for this service. On tuyalocal we can self have everything controlled and it will not go to the tuya servers

CrashyNL commented 2 years ago

I can confirm renewing your IoT core subscription fixes the error :)

I actually can confirm it as well! I think what also helped me was revoking authorization and authorizing again (IoT Core & Device notifications)

vdbosch commented 2 years ago

But Local Tuya doesn’t work (yet) with Zigbee!

From: Tuen Lee @.> Sent: maandag 29 november 2021 12:08 To: home-assistant/core @.> Cc: vdbosch @.>; Comment @.> Subject: Re: [home-assistant/core] Tuya switch not keeping its state when toggled - delay in switch state updating after last HA core update 2021.11.4 (Issue #60034)

I think I will focus more on TuyaLocal to be not dependent on Tuya iot platform. If there is one day the "device status notification" is not free anymore, then they will force us to pay for this service. On tuyalocal we can self have everything controlled and it will not go to the tuya servers

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/60034#issuecomment-981530937 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCKXAW4N2FEWQ5WSM4L7S3UONNHNANCNFSM5IOGRFUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

-- Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware. https://www.avast.com/antivirus

BanbaZA commented 2 years ago

I can confirm renewing your IoT core subscription fixes the error :)

I actually can confirm it as well! I think what also helped me was revoking authorization and authorizing again (IoT Core & Device notifications)

This seems to have worked for me too. Revoke authorisation and then authorise again...

leeyuentuen commented 2 years ago

But Local Tuya doesn’t work (yet) with Zigbee! From: Tuen Lee @.> Sent: maandag 29 november 2021 12:08 To: home-assistant/core @.> Cc: vdbosch @.>; Comment @.> Subject: Re: [home-assistant/core] Tuya switch not keeping its state when toggled - delay in switch state updating after last HA core update 2021.11.4 (Issue #60034) I think I will focus more on TuyaLocal to be not dependent on Tuya iot platform. If there is one day the "device status notification" is not free anymore, then they will force us to pay for this service. On tuyalocal we can self have everything controlled and it will not go to the tuya servers — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#60034 (comment)> , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCKXAW4N2FEWQ5WSM4L7S3UONNHNANCNFSM5IOGRFUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . … -- Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware. https://www.avast.com/antivirus

true, like said before in the comments https://github.com/home-assistant/core/issues/60034#issuecomment-980035053

Just want to attend that we need to try independently and not depend on the tuya server.

frenck commented 2 years ago

Just want to attend that we need to try independently and not depend on the tuya server.

This is off-topic for the issue at hand.

vdbosch commented 2 years ago

Indeed, this current issue shows again that we should be completely independent from the cloud. Local Tuya including Zigbee would than be a very good solution.

But Local Tuya should be developed first further with Zigbee, PIRs etc.

From: Tuen Lee @.> Sent: maandag 29 november 2021 12:19 To: home-assistant/core @.> Cc: vdbosch @.>; Comment @.> Subject: Re: [home-assistant/core] Tuya switch not keeping its state when toggled - delay in switch state updating after last HA core update 2021.11.4 (Issue #60034)

But Local Tuya doesn’t work (yet) with Zigbee! From: Tuen Lee @.> Sent: maandag 29 november 2021 12:08 To: home-assistant/core @.> Cc: vdbosch @.>; Comment @.> Subject: Re: [home-assistant/core] Tuya switch not keeping its state when toggled - delay in switch state updating after last HA core update 2021.11.4 (Issue #60034 https://github.com/home-assistant/core/issues/60034 ) I think I will focus more on TuyaLocal to be not dependent on Tuya iot platform. If there is one day the "device status notification" is not free anymore, then they will force us to pay for this service. On tuyalocal we can self have everything controlled and it will not go to the tuya servers — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#60034 (comment) https://github.com/home-assistant/core/issues/60034#issuecomment-981530937 > , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCKXAW4N2FEWQ5WSM4L7S3UONNHNANCNFSM5IOGRFUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 &mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub &referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . … -- Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware. https://www.avast.com/antivirus

true, like said before in the comments

60034 (comment) https://github.com/home-assistant/core/issues/60034#issuecomment-980035053

Just want to attend that we need to try independently and not depend on the tuya server.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/60034#issuecomment-981540111 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCKXAR3B2C7T2MRG4GWKQ3UONORTANCNFSM5IOGRFUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

Tamas-Toth-ebola commented 2 years ago

'Sadly' the IoT Core resubscription had corrected my case also.

I did not found where can I check the current status of the subscription so I simply mad a 'resubscription'. After it status reports seems valid and instant.

Currently (as more people wrote it) I have only 1 month expiration time what will be more than uncomfortable (this is why I wrote 'sadly'). image

I registered for a 6 month extension but based on the true goal of the Tuya developer console I don't think I will get it. image

Thanks for everybody for the information.

zlinoliver commented 2 years ago

I now notice that the IoT Core trial is only available for 1 month 🤷‍♂️(other subscriptions are also time-limited). Guess I'll be trying Tuya local and/or move away from it.

If your 1 month IoT Core API Service trial edition expired, you can go to Cloud > My Services on the Tuya IoT Development Platform to request extending your API service by up to 6 months for free. 001 002

You will get the result within one day. 003

muddy79 commented 2 years ago

So, please fix me if I'm wrong: the goal of the new, official TuYa integration was to make its user to pay for it, eventually?

titiviking commented 2 years ago

Exactly the question I asked during the live stream presenting the new Tuya... I didn't got any reply then... I think I'll start looking into the Local Tuya and be able to isolate my Tuya devices from the Web...

Tuya is fine with cloud connection, but I refuse to pay for a device that runs locally just for the sake of having the status updates... Hence local integration it would be...

frenck commented 2 years ago

ℹ️ We've opened up an alert here:

https://alerts.home-assistant.io/#tuya.markdown

I'm locking down this issue at this point, as it is going all over the place. The issue is known and being worked on.

Additionally, this unlucky is combined (apparently) with trail subscriptions expiring. Make sure yours isn't expired and see the above screenshots by @zlinoliver.

Discussions on the Tuya platform becoming paid or not in the future is NOT relevant or related to this issue. Please take such discussions to the community forums (or even better), contact Tuya directly with such questions by submitting a support ticket with them.