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

Simplify not working when not on the same VLAN #15

Open
HermesHonshappo opened this issue Nov 23, 2022 · 1 comment
Open

Simplify not working when not on the same VLAN #15

HermesHonshappo opened this issue Nov 23, 2022 · 1 comment

Comments

@HermesHonshappo
Copy link

HermesHonshappo commented Nov 23, 2022

Hello

Been trying to use the HA integration as well as the command-line tool.
It worked a long time ago, maybe a yea, back when we had to get the key manually. I remember doing this.

About 8 months ago, I re-did all my LAN infra to separate IoT into a different VLAN, it stopped working. I didn't make the connection at the time.

Since then, I reinstalled HA on a new machine recently, and that HA now has 2 interfaces (one on LAN, one on IoT LAN). So HA is now connected again directly to the IoT LAN, without going through the router.

Out of curiosity, I tried again today to install the HA integration. To my surprise, it worked, whereas it failed repeatedly in the past.

I noticed that the values returned by the integration were wrong (time left in the cycle, etc.), so I wanted to send the JSON. I reinstalled and compiled on two different machines, which are on the regular LAN, and the command line tool refuses to work:

% ./simplyfi 192.168.107.31 getkey
## Candy Simply-Fi tool by Melvin Groenendaal ## 
error: find_xor_key_list, could not find key

So in a nutshell: HA on IoT VLAN, integration works and sicovers key on its own. command-line tool tested on 2 machines not directly connected to IoT VLAN, and command-line fails on both machines.

So I'm wondering if there could be an issue in the code where if the machine running the code and the Candy device aren't on the same LAN, it fails. Does that sound possible?

@Robertiano
Copy link

The same issue here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants