sibowler

@jmcollin78 - Those recent Timeout errors (including the one on 4.0.2) seem to indicate a connection failure. Could the key have changed? IF those devices have been updated OTA possibly...

@AFumi39 That error occurs further up the stack than this change. Can you check if the switch entity for your dyson is assigned to DPS 1? The other thing to...

@AFumi39 - do you have logs for those devices that aren't working correctly?

> There error is this: > > ``` > Logger: custom_components.localtuya.common > Source: custom_components/localtuya/pytuya/__init__.py:707 > Integration: LocalTuya ([documentation](https://github.com/rospogrigio/localtuya/), [issues](https://github.com/rospogrigio/localtuya/issues)) > First occurred: 19 ottobre 2022 18:03:46 (11 occurrences) > Last...

Hi @AFumi39 - Unfortunately I'd say this looks like a different type of error. The errors are during the connection procedure and seem to be either a) not being able...

Can you see if the change in PR #1022 fixes your issue? It seems to be related to the RESET call which that PR changes the behavior of.

Hi @Merril-r - no it won't appear yet. I'd like to get a few people to test the change, which essentially involves manually updating the code in their HA to...

Hi @Merril-r - Essentially you take the modifications identified in the PR (https://github.com/rospogrigio/localtuya/pull/1022/files) and apply them to the files in your Home Assistant install. From my experience you can do...

You'll get a -1 for any of the manually added DPS, until the DPS are refreshed (i.e. after you've finished setting it up as a device). I've made a further...

> @sibowler I copied and pasted code as per my question above. Still not working. I don’t get an option to select passive mode. Hi @Merril-r - Yep, that's one...