Lost access to Deta 6904HA quad switch

[AussieSusan]

A few months ago I installed a Deta 6904HA quad touch light switch and connected it to HA via Tuya Local successfully. Some of the switch states were incorporated into a HA automation.
Just recently I noticed that the automation was failing because the device in HA was 'unavailable'.
I can still access and control the switches using the SmartLife application on my phone. I can also see the device listed in the Tuya developer web site.
The 'tinytuya' python app can see the device and can retrieve information from it.
I deleted the device from the HA integration and tried to re-add it but it only offered some rather incompatible options as to the 'standard' device type'
The Tuya Local integration also listed the device as 'Needs Attention" with the text "Failed setup, will retry: tuya-local device offline".
Rather than being offline, I can see the device in my access point and I can ping its IP address.
I have also created a new yaml file (based on the 'simple_triple_switch_timer.yaml' file) and when I deleted and re-added the switch it correctly identified the new yaml file and added the device.
However it immediately showed the device as needing attention a with the same error message as above.
(As I said, the tinytuya app can see both the device and pick up the information from the Tuya web site. However when I try to add the device with the 'SmartLife cloud assisted device setup' option, it tells me 'Unable to find any unregistered devices for the account'. I can add the device manually providing the device ID, local key and local IP address)

My questions:

• has some standard device file/entry been removed from a recent release (all of the yaml files in /config/custom_components/tuya_local/devices have a date of 30/4/2026) that stopped my device being known
• what else could be stopping the integration from correctly accessing the device

I'm happy to provide whatever other information is required.

Susan

[make-all]

No files have been removed recently, but there does seem to be a race condition in HACS where if you restart HA too soon after installation, the new release might not be fully unpacked yet so files are missing. I always try to wait at least 30 seconds after the restart notification shows up (the exact timing will depend on the speed of your storage device, and may be longer if you run HA from an SD card).

[AussieSusan]

I'm not quite sure that I understand: are you saying that when the integration shows as being installed 100%, that it is not really complete?
In that case, what do I need to do to redo the update (without waiting for the next release)?

Also, how can I tell which yaml file was used previously that sis recognise my device?

Finally, (to repeat my question above in different words) what does the 'Needs Attention' message really mean and what do I need to do? (I know the last part of the message says it is offline, but I know that it isn't as mentioned in my original post).

(BTW I run HA on RPI4 using an SSD drive)

[make-all]

Since there is a new release now the question is kind of moot, but there is a Redownload option in the HACS menu.

The "Needs Attention" message means the device failed to initialise, you need to check the logs to find out why (in normal operation, the device being offline is the most likely explanation, but in cases like this where it happens immediately after an installation, the likelihood of a different cause is higher).