Closed elockman closed 1 year ago
Test # 2 was resolved by updating my install with:
python3 -m pip install --upgrade tinytuya
Tests # 3 and # 4 are still failing.
Ok, I think I see what's going on. There are 2 different firmware versions: one which uses low-resolution temperatures on one set of DPs, and the other which uses high-resolution on a different set of DPs. Until it receives a .status() response it has no idea which set it needs to use. So, simply move that tstatdev.status()
to above the tests.
Thank you @uzlonewolf. That worked!
As a side note, I've found that these thermostats get very confused if you send certain commands too quickly. For example, a .setMode(...) followed immediately by a .set____Setpoint(...) will result in it reporting and displaying that new setpoint, however internally it will still be using the old setpoint. In my program I ended up waiting for the status update before sending another command after either a mode change or setpoint change.
Is this a bug related to issue #327?
Doesn't look like it. Are any of those tests still failing?
the tests work with the status call ran first
I'm going to close this one out as it looks like everything has been fixed. @elockman please re-open if you're still having issues.
I am having trouble with local thermostat calls again.
This is my test code with DeviceID and LocalKey redacted:
Tests were ran one at a time by uncommenting the associated lines of code.
The first test works with setMiddleSetpoint() The second test fails with:
The last 2 tests fail similarly with:
I'm not sure why the keys are not found, when they are clearly in the table.
@uzlonewolf, I know you've used the thermostats before. Have you ran into this, or have any insight?