Thinking about this further, I’m going to set up a 2nd HomeAssistant to run the 2nd TUYA account, and then use the “Home Assistant Remote” Integration to integrate the devices seemlessly into my main instance - well that’s the hope.
I have 3 Tuya lights and 1 Tuya switch on WIFI and the core Tuya integration, and several second delays are normal. It’s because the commands pass thru a China server, nothing to do with the number of accounts.
I don’t have delays, I have timeouts , lots of them.
requests.exceptions.SSLError: HTTPSConnectionPool(host=‘apigw.tuyaeu.com’, port=443): Max retries exceeded with url: /v1.1/m/thing/vdevoxxxxxxxxxxx/commands (Caused by SSLError(SSLEOFError(8, ‘[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1028)’)))
My 2nd instance of H.A is up and running with my 2nd TUYA account, that was painless. I will join them this evening and then start the lengthy process of moving devices between accounts/zigbee hubs and editing all the automations & helpers to use the new IDs
I had quite a few Tuya devices before I started using H.A, some are Virtual devices and some of my automations were more reliable staying in the smartlife app, so it just made more sense to keep it simple in H.A
By giving the entities in the 2nd / remote Home Assistant the same Entity ID that they had in the original Home Assistant, they slotted seemlessly into all the automations/dashboards/helpers etc that they were in before. I was expecting remote-specific Entity IDs so I’m pleased with that outcome.