Roomba on different subnet issue

[apostolakisl]

@bpwwer  I have an i7.  I keep all of my iot stuff on a different subnet that is firewalled from my important stuff.  When needed, I open a path between two devices, which I have done between polyisy and roomba. I had the pg2 roomba node working, except it really doesn't work on the i7 very well at all.  I also have polyisy talking to my blue iris server using the same firewall hole technique . . . so I am confident there is no firewall problem.  I was hoping to use your pg3 node which appears to be expressly made for i7, amongst others.  But the autodiscover does not seem to be looking across subnets, the node server log lists it as giving up after several tries and not discovering. 

Anyway I can tell it where to look or set the ip address manually?

Thanks.

[bpwwer]

There isn't any option to set the IP address manually.  That would have to be added.

[apostolakisl]

3 hours ago, bpwwer said:

There isn't any option to set the IP address manually.  That would have to be added.

Would it keep the ip address if I moved polisy to the Roomba subnet and then back again?

[bpwwer]

It does save the discovered Roombas, but I have no idea if that would work.  Seems like your router wouldn't allow that.

[apostolakisl]

1 minute ago, bpwwer said:

It does save the discovered Roombas, but I have no idea if that would work.  Seems like your router wouldn't allow that.

The router wouldn't have any issues.  I have set it to allow com between polisy and roomba bridging the two vlans.  The only question is if the node server will try to re-discover roomba when (if) it senses that its subnet has changed after I return it to the more secure vlan.

[bpwwer]

It only tries to discover if there aren't any saved or you manually start the discovery process.

[apostolakisl]

Success.  I moved polisy to the other vlan, it found Roomba, I moved Polisy back to the secure vlan and it was able to maintain connection.  

Thanks.