Automation failure of Tuya bulb with "network error: (-9999999) sign invalid"

[hl1234]

The problem

I have a light group with 3 Tuya and 2 Sengled bulbs. Tuya are wifi via cloud and Sengled are Zigbee. At random times when I run my automation to turn them on, the automation is triggered fine but occasionally one or more of the Tuya bulbs does not come on due to a network error causing the automation to abort. The message is that the automation stopped due to an error. Specifically "network error: (-9999999) sign invalid". If I follow up with another triggered automation or directly through the device, the offending bulb nearly always responds correctly without restarting. If it does not immediately work, it does after 30 seconds or so. Sometimes it happens when turning the commanding the bulb off and sometimes the problem interrupts more than on bulb from being controlled.

I've seen references to similar problems but not with this error message specifically. Some have suggested that Tuya local might be more reliable. Others suggest the contrary.

Is there a way to catch error in an automation and retry a step?
It seems like a hacky bandage but do I need to try the on or off command twice in every automation. Yuck!

In the screenshot the offending bulb is not listed.

This obviously points to the superiority of Zigbee devices in this situation but I'd like to avoid replacing all my Tuya bulbs that I had before I started this HomeAssistant journey. I am definitely avoiding any more going forward.

Thanks!

What version of Home Assistant Core has the issue?

core-2024.11.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tuya cloud

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

alias: Laundry_button_toggle
description: ""
triggers:
  - trigger: state
    entity_id:
      - binary_sensor.flic_80e4da7e0a1e
    from: "on"
    to: "off"
    id: flic_pressed
  - trigger: state
    entity_id:
      - input_button.laundry_lights_on
    from: null
    id: dashboard_button_pressed
conditions: []
actions:
  - if:
      - condition: state
        entity_id: light.laundry_lights
        state: "off"
    then:
      - action: light.turn_on
        metadata: {}
        data: {}
        target:
          entity_id: light.laundry_lights
      - condition: trigger
        id:
          - flic_pressed
      - action: timer.start
        metadata: {}
        data:
          duration: "00:15:00"
        target:
          entity_id: timer.laundry_timer
    else:
      - action: timer.cancel
        metadata: {}
        data: {}
        target:
          entity_id: timer.laundry_timer
      - action: light.turn_off
        metadata: {}
        data: {}
        target:
          entity_id: light.laundry_lights
      - action: switch.turn_off
        metadata: {}
        data: {}
        target:
          entity_id: switch.bench
mode: single

Anything in the logs that might be useful for us?

Additional information

This is running directly on an older NUC. Works fine in general.
Devices are all using DHCP.
Host has dedicated IP

[home-assistant]

Hey there @tuya, @zlinoliver, mind taking a look at this issue as it has been labeled with an integration (tuya) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tuya can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tuya Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

tuya documentation
tuya source
_{^{(message by IssueLinks)}}

[hl1234]

Here is a typical traceback of the error

2025-01-23 10:32:41.259 ERROR (MainThread) [homeassistant.components.automation.laundry_button_toggle] While executing automation automation.laundry_button_toggle
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 743, in async_trigger
return await self.action_script.async_run(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1801, in async_run
return await asyncio.shield(create_eager_task(run.async_run()))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 464, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 528, in _async_step
self._handle_exception(
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 558, in _handle_exception
raise exception
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 526, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1075, in _async_if_step
await self._async_run_script(if_data["if_then"])
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1274, in _async_run_script
result = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 727, in _async_run_long_action
return await long_task
^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1801, in async_run
return await asyncio.shield(create_eager_task(run.async_run()))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 464, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 528, in _async_step
self._handle_exception(
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 558, in _handle_exception
raise exception
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 526, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 764, in _async_call_service_step
response_data = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 727, in _async_run_long_action
return await long_task
^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2802, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2845, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1007, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 628, in async_handle_light_on_service
await light.async_turn_on(**filter_turn_on_params(light, params))
File "/usr/src/homeassistant/homeassistant/components/group/light.py", line 179, in async_turn_on
await self.hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 2802, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2845, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1032, in entity_service_call
raise result from None
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1612, in async_request_call
return await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 628, in async_handle_light_on_service
await light.async_turn_on(**filter_turn_on_params(light, params))
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1687, in async_turn_on
await self.hass.async_add_executor_job(ft.partial(self.turn_on, **kwargs))
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 644, in turn_on
self._send_command(commands)
File "/usr/src/homeassistant/homeassistant/components/tuya/entity.py", line 293, in _send_command
self.device_manager.send_commands(self.device.id, commands)
File "/usr/local/lib/python3.12/site-packages/tuya_sharing/manager.py", line 93, in send_commands
return self.device_repository.send_commands(device_id, commands)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/tuya_sharing/device.py", line 180, in send_commands
self.api.post(f"/v1.1/m/thing/{device_id}/commands", None, {"commands": commands})
File "/usr/local/lib/python3.12/site-packages/tuya_sharing/customerapi.py", line 192, in post
return self.__request("POST", path, params, body)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/tuya_sharing/customerapi.py", line 121, in __request
raise Exception(f"network error:({ret['code']}) {ret['msg']}")
Exception: network error:(-9999999) sign invalid

[jchevin]

I have an identical issue with my tuya lights.

Same error received.

tuya-01JG2Z9M1242Y6YRPPBTJ28KKY-GLD381HA-6e20c1752a0e3a9331045f45b54d35b9-1.json

[kevinbackhouse]

I have had similar issues with my Shelly relays, but I'm pretty sure that it's caused by the devices briefly losing WiFi signal, not by a bug in home assistant. I use the continue_on_error feature as a workaround. It means that I have to call "light-off" in a loop which adds an annoying amount of extra complexity to the automation, so I've started putting that kind of logic into reuseable blueprints instead. Here's an example:

https://github.com/kevinbackhouse/home-assistant-blueprints/blob/d3410d5392f3e01d3c6c73b56e8ef5e2b9eff7c1/blueprints/automations/timer-light-off-with-retry/timer-light-off-with-retry.yaml#L28-L33

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.