Conversation
for more information, see https://pre-commit.ci
cdnninja
left a comment
cdnninja
left a comment
There was a problem hiding this comment.
Few thoughts. As well were is state for each chamber? Maybe I missed that.
| @@ -12,32 +12,33 @@ | |||
| necessary to maintain state, especially when trying to `pause` or `resume` the device. | |||
| Defaults to 60 seconds but can be set via: | |||
|
|
|||
There was a problem hiding this comment.
Should this file be called fryer vs kitchen?
There was a problem hiding this comment.
Yea, should be separate from ovens or other kitchen devices.
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
| class_name='VeSyncDualAirFryer', | ||
| module=vesynckitchen, | ||
| dev_types=['CAF-TF101S-AEU', 'CAF-TF101S'], | ||
| setup_entry='CAF-TF101S', |
There was a problem hiding this comment.
Tested: The newer CAF-TF102S (Dual Blaze TwinFry 10L, EU) also works with VeSyncDualAirFryer — status, dual chambers, cook modes all confirmed. Suggest adding 'CAF-TF102S' here.
|
Added CAF-TF102S (Cosori Dual Blaze TwinFry 10L) support on top of this branch: lackas/pyvesync@e86d102 We also built a custom HA integration component with dual-chamber sensor entities (per-zone cook status, temperature, remaining time) based on this refactor: https://github.com/lackas/ha-core/tree/vesync-air-fryer Both have been running in production. Happy to help get this over the finish line if needed. |
3 participants
No description provided.