I just did the firmware upgrade in Z2M to whatever latest OTA upgrade was offered. Did not fix anything…
I did the firmware upgrade in tuya as I have tuya zigbee hub and to be honest i think its fixed. have not had any drop outs today that i have seen and been notified. Ill keep monitoring
Yet another OTA update available today in zigbee2mqtt - and guess what, it’s finally fixed for mine (2x _TZ3000_5f43h46b) after updating!
1 Like
Has anyone been successful in updating the firmware via ZHA?
2 Likes
FYI, ZHA does not out-of-the-box come with any OTA provider(s) for Tuya so you have to manually create the folder and copy the correct OTA image file then enable in YAML → https://www.home-assistant.io/integrations/zha#ota-firmware-updates
2 Likes
I’ve configured as per that link, but no update appears to have occurred (current_file_version (id: 0x0002) reports 74)
I’m wondering if this is because a mismatch on the image_type
The debug log says
DEBUG (SyncWorker_7) [zigpy.ota.provider] ImageKey(manufacturer_id=4417, image_type=54179): /config/ota/1662545193-oem_zg_tl8258_plug_OTA_3.0.0.bin, version: 192, hw_ver: (None, None), OTA string: Telink OTA Sample Usage
but the device reports image_type_id (id: 0x0008) of 65535… as opposed to the 54179 in the image file
I gave it a go using the ZHA OTA instructions and it updated fine.
The app_version (id: 0x0001) went from 77 to 192
Sorry I didn’t check the initial image_type_id (id: 0x0008), but after the upgrade it was 65535
It did take a few minutes with periodic ‘OTA upgrade progress’ log entries.
I will keep an eye on it and see if it resolves the issue.
Device details: TS011F (_TZ3000_ky0fq4ho)
2022-10-05 17:59:43.223 DEBUG (SyncWorker_5) [zigpy.ota.provider] ImageKey(manufacturer_id=4417, image_type=54179): /config/zigpy_ota/1662545193-oem_zg_tl8258_plug_OTA_3.0.0.bin, version: 192, hw_ver: (None, None), OTA string: Telink OTA Sample Usage
...
2022-10-05 18:02:40.750 DEBUG (MainThread) [zigpy.zcl] [0x7B38:1:0x0019] Decoded ZCL frame: Ota:image_block(field_control=<FieldControl.MinimumBlockPeriod: 2>, manufacturer_code=4417, image_type=54179, file_version=192, file_offset=1800, maximum_data_size=64, minimum_block_period=0)
2022-10-05 18:02:40.750 DEBUG (MainThread) [zigpy.zcl] [0x7B38:1:0x0019] Received command 0x03 (TSN 79): image_block(field_control=<FieldControl.MinimumBlockPeriod: 2>, manufacturer_code=4417, image_type=54179, file_version=192, file_offset=1800, maximum_data_size=64, minimum_block_period=0)
2022-10-05 18:02:40.751 DEBUG (MainThread) [zigpy.zcl] [0x7B38:1:0x0019] OTA image_block handler for '_TZ3000_ky0fq4ho TS011F': field_control=FieldControl.MinimumBlockPeriod, manufacturer_id=4417, image_type=54179, file_version=192, file_offset=1800, max_data_size=64, request_node_addr=Noneblock_request_delay=0
2022-10-05 18:02:40.752 DEBUG (MainThread) [zigpy.zcl] [0x7B38:1:0x0019] OTA upgrade progress: 0.6
...
2022-10-05 18:18:01.257 DEBUG (MainThread) [zigpy.zcl] [0x7B38:1:0x0019] OTA upgrade progress: 100.0
...
2022-10-05 18:18:01.344 DEBUG (MainThread) [zigpy.zcl] [0x7B38:1:0x0019] OTA upgrade_end handler for '_TZ3000_ky0fq4ho TS011F': status=Status.SUCCESS, manufacturer_id=4417, image_type=54179, file_version=192
1 Like
If it helps when i updated these plugs via the Tuya App it says the latest version is V1.0.13.
My device is “TS011F by _TZ3000_typdpbpg”, not sure if that is the issue. (i.e. not _TZ3000_ky0fq4ho)
Can you post the relevant part of your configuration.yaml to make sure I’m not making a silly mistake. Below is mine.
zha:
zigpy_config:
ota:
otau_directory: /config/ota
Sure here it is:
zha:
zigpy_config:
ota:
otau_directory: /config/zigpy_ota
ikea_provider: false
ledvance_provider: false
logger:
default: info
logs:
homeassistant.components.zha: debug
zigpy: debug
Unfortunately I am still seeing the same issue (possibly worse) after the update.
I have powered the device off then on again and will monitor further.
Thanks, and I take it you didn’t have to issue any commands…Zigbee Home Automation - Home Assistant suggests that some zigbee commands need executing, e.g. for Philips Hue.
Oh yes I did have to issue a command. It was a copy and paste from the instructions, with the ieee attribute updated.
The ieee can be found in the “Zigbee info” drop down in the “Device info” panel
service: zha.issue_zigbee_cluster_command
data:
ieee: "xx:xx:xx:xx:xx:xx:xx:xx"
endpoint_id: 1
cluster_id: 25
cluster_type: out
command: 0
command_type: client
args:
- 0
- 100
1 Like
Hmm yeah the upgrade has not fixed the issue I have. I’m not sure if this is the same problem as other people have though.
Mine seems to be the voltage drops to zero and amperage spikes to well above 16A to about 35A, resulting device automatically switching off.
Here is the voltage graph before and after the upgrade:
Ok this thread has been talking abut the same issue I have been having. Seems like it is a hardware issue, not resolvable with firmware. Tuya TS011F (TZ3000_typdpbpg) powers off · Discussion #13343 · Koenkk/zigbee2mqtt · GitHub
OK, seems there are 2 different issues as the issue I’ve been having that fits both this thread description and the other one is fixed with the new firmware. I have 2 devices that are both fixed with the new firmware.
@Kenneth_Dixon thanks for tips on how to do the upgrade via ZHA. Sorry that it hasn’t fixed your issue.
2 Likes
Weirdly enough cant seem to update the firmware through ZHA.
I managed to update some of my Hue bulbs but cant get ZHA to pick up the Tuya firmware. When I send in the command, nothing happens.
Recommend submit a new bug-port about that to → https://github.com/home-assistant/core/issues
See ZHA docs about debug logging https://www.home-assistant.io/integrations/zha#reporting-issues in order to be able to submit debug logs → https://www.home-assistant.io/integrations/zha#debug-logging
Suggest you also post a new issue about that to zigpy repo and ZHA depends on the zigpy library for Zigbee and OTA and it is developed by ZHA developers → https://github.com/zigpy/zigpy/issues
Where do you source the OTA image files for Tuya TS011F?
1 Like
There seems to be some repository
Here is a tip, not sure if that’s accurate.
1 Like