Add support for machines that doesn't require encryption about home-assistant-candy

[ofalvai]

I made encryption key optional in b2fa7c4. You can update via HACS to the latest version. After a restart, you'll need to re-add the integration and on the config page you can uncheck the "Use encryption key" checkbox.

[ofalvai]

I'm curious, does your machine work with encrypted=1 too? Because my machine accepts ecrypted=0, but it also works with an encryption key, and it's easy to get the key using https://github.com/MelvinGr/CandySimplyFi-tool

Not saying I won't make it optional to use encryption, but currently it uses the key to make it compatible with both encrypted and non-encrypted devices.

[d3m3trius]

Yes, it works also with encryption.

I think a plain text may be simpler, requires less computing power on the tiny esp chip, and may give less trouble.

Not indispensable, but I think useful.

[NoNaMoe]

EDITED - maybe should make a new issue for this?

Hi, i think i found a quirk related to this.
I have a Hoover washer dryer that uses this api and doesnt require encryption key as such, but doesnt spit out pure json...

http://x.x.x.x/http-read.json?encrypted=0 returns {"response":"BAD REQUEST"}
http://x.x.x.x/http-read.json?encrypted=1 returns 7B0D0A09227374617475734C6176617472696365223A7B....

This is hex encoded json, but it isnt XORed/encrypted (I tryed leaving encryption key blank and using "\0" but no luck).

As a workaround/for testing I changed line 35 in candy\client_init_.py to resp_json = json.loads(resp_hex). and the the integration works for me now.

[ofalvai]

Yes, please open a new issue. This will require a bit more investigation, and others will find the ticket easier with a more relevant title.

I'm not sure how to overcome this behavior, because we can't detect the kind of response from the response alone, and I don't see any API endpoint that would reveal the exact model of the machine.