alarmdecoder.com

Hi,

I had this set up and running pretty flawlessly for several months, integrated with Smart Things as per the instructions. I did some network surgery and changed some subnets around, and now unable to discover the AD Appliance with either ST Simulator or the app installed on my phone. I see the "discover" debug logs being sent to ST, but nothing is found and no other log messages. I tried uninstalling and reinstalling multiple times.

What mechanism does ST use to discover devices? Is there any way I can manually enter the IP of the AD appliance instead of relying on discovery?

Andrew

It relies on a subset of upnp for discovery - not aware of a manual way to input ip address

Unfortunate because my firewall doesn't do upnp and they're on different subnets. Can the code be modified to allow manual input of an IP? Not necessarily asking you to, just if it is possible before I sink time to research.

Andrew

Honestly, I'm not sure - I believe the discovery happens on port 1900, maybe you can add a firewall rule to allow that between the subnets.

They will need to communicate on certain ports anyway, what's one more? (https etc)

I actually added bidirectional * access between both without any success. I ended up moving the AD appliance to the same subnet as the ST box and the discovery is working.

Now though I get "deviceNetworkId must be unique" when I try to hit "done" after selecting the AD device. Any advice?

Make sure you've uninstalled and removed any previous attempts from SmartThings