Device losing it's state on some certain actions. AS50S2SF1FA-B #75

New Issue

2023-06-17T00:55:29+02:00

utegental commented

2023-06-17 00:55:29 +02:00

(Migrated from github.com)

Describe the bug
Switching between modes disables Silent / Mute / Health modes. Switching on Health mode doesn't have any effect.

To Reproduce

Switch on mode Cool.
Set desired temperature.
Select program 'UV + Cool'. That will activate Health mode.
See that temperature reseted to a default 22 value.
Set again desired temperature.
See that program disappeared from combobox and device switched to mode Cool(without UV).
Enable Mute mode.
Change mode to any (Fan only, for example)
See that Mute mode became disabled.

Expected behavior
Entity should preserve it's state fully, not randomly resetting some features.

Additional context
Looks like requests to api should be sending all the flags related to modes every time, not just when we switching them.

**Describe the bug** Switching between modes disables Silent / Mute / Health modes. Switching on Health mode doesn't have any effect. **To Reproduce** 1. Switch on mode Cool. 2. Set desired temperature. 3. Select program 'UV + Cool'. That will activate Health mode. 4. See that temperature reseted to a default 22 value. 5. Set again desired temperature. 6. See that program disappeared from combobox and device switched to mode Cool(without UV). 7. Enable Mute mode. 8. Change mode to any (Fan only, for example) 9. See that Mute mode became disabled. **Expected behavior** Entity should preserve it's state fully, not randomly resetting some features. **Additional context** Looks like requests to api should be sending all the flags related to modes every time, not just when we switching them.

Andre0512 commented

2023-06-21 23:59:43 +02:00

(Migrated from github.com)

Hi, thanks for reporting! This was helpful to reproduce the behavior 🙂
We have some unfortunate dependencies there between the startProgram and settings commands. Please check the latest beta, I tried to improve it, but I think it still isn't perfect...

Hi, thanks for reporting! This was helpful to reproduce the behavior :slightly_smiling_face: We have some unfortunate dependencies there between the `startProgram` and `settings` commands. Please check the latest beta, I tried to improve it, but I think it still isn't perfect...

Andre0512 commented

2023-07-01 17:03:43 +02:00

(Migrated from github.com)

With the latest beta it should work a bit better again.

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: xiconfjs/hon#75