-
Notifications
You must be signed in to change notification settings - Fork 23
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
HA not on same vlan as Gecko in.touch2 ? #6
Comments
We could add the capability to specify an IP address, but I'm not sure that would work if UDP traffic is unable to flow between your VLANs (which seems to currently be the case). Do you have any way to allow UDP traffic between your HA instance and your intouch2 module? |
Yes, there is no problem with permitting UDP unicast traffic between the vlan's. But multicast UDP-traffic is not routed between vlan's, and I think you are using multicast in this case to find the intouch2-module? |
Yep, specifying an IP address would be a great option as I also have VLANs causing it to not find my hot tub |
+1 for this requirement if its possible - my Gecko also sits on a separate LAN. |
+1 to specify IP address. |
The option to specify an IP address for a specific Gecko unit may also help with ignoring the Steamlinx Gecko unit in #20 |
+1 to specify an IP address. |
+1 to add the ip manually. |
Yes, I'm most interested in this feature as well. I keep devices like this on a separate VLAN, so being able to specify it would be great! |
+1, have the same issues with Multicast UDP traversing over VLAN:s.....When putting the module on the same VLAN it works like a charm, but when switching back to IoT VLAN it looses connection again |
+1 for manually adding IP. |
+1
Johan
… On Nov 7, 2021, at 17:08, simonk1969 ***@***.***> wrote:
+1 for manually adding IP.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
+1 Same for me, my Unraid VMs are on a seperate VLAN traffic can be permitted. Thanks |
v0.0.8 should fix this |
I stiil can't add my SPA to HA. Get this in the logs: Cannot find spa from name Kotten10 |
Reopening to allow investigation |
Can you try from an command prompt?
Then post client.log? (This off the top of my head 😀, so there might be syntax errors … ) |
Hi Yes, here is the logfile. |
Thanks, can you remove the <> around the IP address and try again. I expect that the shell will find your spa then. |
That did the trick:
Starting discovery process...Found 1 spas (Gecko) |
I had the exact same issue as @PaulMalmqvist, and the solution provided by @gazoodle basically worked. Here's the syntax that I had to use:
|
Ok, that’s good news. Basically the library can handle the topology but the integration can’t. I’m pretty sure I know why and I’m just setting up an environment to replicate what you’ve got so I can be sure of a fix. I’ll do my best to get it done this weekend. |
Thanks for your patience folks, this should now be fixed. I assumed that passing a static IP was going to be the same as when that IP was on a different sub net that had peer routing working, just not broadcast, but I was wrong, the way the code was structured lead to the locator still trying to do a broadcast which of course didn't work. The shell doesn't do this which is why I asked @PaulMalmqvist to try that way just to be sure that was the problem. I ended up building a whole new vlan at home and making sure that my dev box was on that lan to make sure ... in hindsight it would have been much easier to shove the in.touch2 module there instead and then test but hey ho, I had a heap of fun with my networking gear so it was a nice learning experience ... every day's a school day right? Anyway, fingers crossed that this works for you folk. |
I'm in a similar situation with this library. From the GeckoShell.run, I can find the Spa by specifying the IP, but when trying to integrate with a python3 script, I'm unsure of how I can specify the IP on the other subnet to be included in the discovery. |
Version of the custom_component
2d3e2d7
Configuration
None
2021-01-09 12:50:51 INFO (MainThread) [geckolib.locator] Discovery process started
2021-01-09 12:50:51 DEBUG (Thread-13) [geckolib.locator] Locator retry thread started
2021-01-09 12:50:51 INFO (MainThread) [custom_components.gecko.config_flow] Async step user, we have GeckoLocator(age=0.00041642598807811737,has_had_enough_time=False,spas=[])
2021-01-09 12:50:51 DEBUG (Thread-14) [geckolib.driver.udp_socket] Sending b'1' to ('', 10022)
2021-01-09 12:50:52 DEBUG (Thread-14) [geckolib.driver.udp_socket] Sending b'1' to ('', 10022)
2021-01-09 12:50:53 DEBUG (Thread-14) [geckolib.driver.udp_socket] Sending b'1' to ('', 10022)
2021-01-09 12:50:54 DEBUG (Thread-14) [geckolib.driver.udp_socket] Sending b'1' to ('', 10022)
2021-01-09 12:50:55 DEBUG (Thread-13) [geckolib.locator] Locator retry thread stopped
2021-01-09 12:50:55 INFO (Thread-14) [geckolib.driver.udp_socket] GeckoUdpSocket thread finished
2021-01-09 12:50:55 WARNING (MainThread) [custom_components.gecko.config_flow] No spas found on the local network
The text was updated successfully, but these errors were encountered: