Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Object "HeaterMode" doesn't show the correct state/value #266

Closed
janku-88 opened this issue Apr 22, 2024 · 8 comments
Closed

Object "HeaterMode" doesn't show the correct state/value #266

janku-88 opened this issue Apr 22, 2024 · 8 comments
Labels
bug Something isn't working Fixed Fixed in development branch

Comments

@janku-88
Copy link

janku-88 commented Apr 22, 2024

At first: Thank you for this very good working adapter!

I found a little bug in combination with my "Puryfier Hot+Cool"

The Object "HeaterMode" is always on Value "Off(false)"

Writing to the Object is possible and the transmission to the device is also working.
--> When the Object "HeaterMode" is switched to "ON(true)" the heating mode in the device is switched on and depending on the room temperature and the target temperature the heater starts working.
But the object value is still "Off(false)"
Respectively is directly changed back to "Off(false)
--> When the Object "HeaterMode" is written with "Off(false)" the heating mode in the device is turned off.

When the heater mode is changed via dyson App or directly at the device, the device also starts heating, but the Object "HeaterMode" is not changed and stays at value "Off(false)"

System:
Node.js: v18.20.2
js-controller: 5.0.19
NPM: 10.5.0
dysonairpurifier: v3.1.1

BR
Jan

@Grizzelbee
Copy link
Owner

Hi Jan,

thank you for creating this issue. Since I don't own a Hot+Cool device I can't test the related code myself.
I have a first rough idea - but not enough information.

Please - write a debug log with the adapter:

  • start the adapter
  • change HeaterMode from false to true
  • Change the HeaterMode with the remote control
  • stop the adapter.

Than post the log here. I hope to see the described beaviour of heaterMode inside the log file.

@Grizzelbee Grizzelbee added the bug Something isn't working label Apr 24, 2024
@janku-88
Copy link
Author

Hi Grizzelbee,

done like described.

  1. Adapter log level "debug"
  2. Start Adapter
  3. IOBroker Object "HeaterMode" --> "True"
  4. IOBroker Object "HeaterMode" --> "False"
  5. Activate Heating Mode via Dyson App
  6. Deactivate Heating Mode via Dyson App
  7. Stop Adapter

iob_dysonairpurifier_log_debug.txt

I removed a few credentials and the device name from the log, because i was not shure if this can be a security issue.

@Grizzelbee
Copy link
Owner

Hi Jan,

I just pushed v3.1.6 to the latest (beta) repo. Please test it and drop me a notice whether it's working as expected or not.

@Grizzelbee Grizzelbee reopened this Apr 24, 2024
@janku-88
Copy link
Author

Hi Grizzelbee,

Version 3.1.6 is not yet available in the beta repo (http://download.iobroker.net/sources-dist-latest.json)
But i tested the Version directly from GitHub.

The described behavior is still the same.

And maybe there is a new issue.
Seems that the chooseable values for the Object "HeaterMode" don't match to the possible values of the object. Screenshot_1
When i write "ON" or "OFF" the Heating Mode is disabled in both cases and in both cases the log entry is:
| 2024-04-24 15:18:13.069 | debug | MANUAL CHANGE: device [A1A-EU-MNA5135A] -> [HeaterMode] -> [false], id: [dysonairpurifier.0.A1A-EU-MNA5135A.HeaterMode]
Due to that turning the heating mode on via manual writing the object is not possible
When i write the Object via Script (with values true/false) the behavior is identical to the initial issue.

When in install Version 3.1.6 without a rebuild of the adapter objects (delete all Objects an restart the Adapter) i have 4 possible values to choose in the for the Object Screenshot_2

Please let me know if you need more tests/logs.

@Grizzelbee Grizzelbee added Fixed Fixed in development branch and removed Fixed Fixed in development branch labels Apr 24, 2024
@Grizzelbee
Copy link
Owner

🤦 Your right. My change made it worse instead of better.
Let's give it another try.

@Grizzelbee
Copy link
Owner

Okay - second service!

Please try again directly from github. Version number is still the same.

@janku-88
Copy link
Author

Now it's working fine in Both directions.
Thank you!!!

@Grizzelbee
Copy link
Owner

You're welcome!

Thank you for helping getting this bug found and fixed. Your help is highly appretiated.

@Grizzelbee Grizzelbee added the Fixed Fixed in development branch label May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Fixed Fixed in development branch
Projects
None yet
Development

No branches or pull requests

2 participants