Safe keyfile to /opt/iobroker

[jpawlowski]

After pairing with LGTV, the keyfile is currently saved to ~/.lgtv2.
However, it would be better to have this in /opt/iobroker instead because that directory is usually part of regular backups (or with Docker containers, it is usually the one you would have as an external volume outside of the container).

Without this file being part of backup, a restore will be incomplete, requiring to re-pair the device.

[SebastianSchultz]

Hello,

can you help me with that?
I can't find the place in the code were the keyfile is stored?!

[jpawlowski]

The reference point is here:
https://github.com/SebastianSchultz/ioBroker.lgtv/blob/c098a4ef48a20d83df47f637ce61af7fe6102780/lgtv.js#L323

However, i think there must be a separate attribute to control the destination directory.
Didn’t look into the external LGTV library but likely you will find something in there.

[jpawlowski]

It seems this behavior is intended by the fork author:

https://www.npmjs.com/package/lgtv2

With v1.4.0 the location and filename of the keyFile is changed, so you likely will have to accept the connection on your TV again after upgrading to 1.4.0.

I believe what you wanna do is to upgrade the dependency to version 1.4.0 and implement to store the key inside of ioBroker itself, avoiding the file system. saveKey and clientKey API options sound like they were specifically implemented for this.

[instalator]

#56