Almond device value conversion to homebridge

[pablopoo]

There are 2 instances where the almond device value for a switch property fails to sync with homebridge.

1. The first time homebridge load
2. After a device is updated.

This makes the home app to not get the real device value when it refresh the device state (after the home app is in background state).

Found one line where the almond value is not converted from string and another line where conversion from true/false to 1/0 is wrong.

I will share my findings and solution after I tested it.

[jedimdan]

How's your attempt to find a solution? I'm keen to try and fix this too.

[pablopoo]

The first one, I think was a bug in the code, I don't have that behaviour anymore on my fork.

The second one, I found that the hombridge plugin won't try to reconnect if, for example, I reboot the almond, until I do something on the homekit app (like turning a light on, that force a reconnect). This one is not completely solved right now on my fork. I think it need a reconnection mechanism to try indefinitely until can reach the almond again.

[jedimdan]

Found one line where the almond value is not converted from string and another line where conversion from true/false to 1/0 is wrong.

@pablopoo are you referring to this, this and this?

I'm proposing to changing them all to

if(typeof state != 'boolean') {
    state = state == 'true';
}

What do you think?

[jedimdan]

The first one, I think was a bug in the code, I don't have that behaviour anymore on my fork.

The second one, I found that the hombridge plugin won't try to reconnect if, for example, I reboot the almond, until I do something on the homekit app (like turning a light on, that force a reconnect). This one is not completely solved right now on my fork. I think it need a reconnection mechanism to try indefinitely until can reach the almond again.

Ah okay. This part I'm quite clueless about right now.