What would cause this issue? LAN vs WAN access?

[Teken]

There is a Insteon user who is having a very unique issue where he is able to control all of his Insteon devices via the LAN and WAN. Though he has a specific device which is a I/O Linc which controls two GDO which operate just fine over the LAN but can not do the same over the WAN?

 

I can tell you from all the years doing this I have never seen just a single device not accessible from remote control??

 

Does anyone have ideas or possible faults that could be present that would be so specific to this issue??

 

The one thing I've asked the user is to try the same with a iPhone vs Android. The reason being is some of the iterations of Windows / Android certain features or products were not present or supported vs the iOS platform.

 

Has anyone ever seen where a single device was not accessible via the WAN but yet controllable by the LAN??? The user has affirmed local access does in fact control all other Insteon devices and prior to installing the HUB II it worked perfectly with his HUB v1.

 

The only other thing I can think is there is some kind of *cloud* issue where the command is not being sent from the new HUB II?

 

http://forum.smarthome.com/topic.asp?TOPIC_ID=16718

[paulbates]

Teken

There is an instance of the device definitions in the hub and one in the cloud. There are some subtle differences on being local to define devices and set them up (at least in hub 1).

 

I agree that the apple vs android makes no sense, but there is a way to eliminate that, have them log in at: https://connect.insteon.com/Account/Loginand see if they can see it there. If its not visible at the cloud account, then somehow its known locally but not on the cloud (and not a problem with mobile apps).

 

Its been over a year since I used it, but I think that the credentials are the same ones you set up in the mobile app. 

 

I believe your last advice is best. Delete, and re-add it, see what happens. Somehow the cloud account lost track.

 

Paul

 

 

[Teken]

Teken

There is an instance of the device definitions in the hub and one in the cloud. There are some subtle differences on being local to define devices and set them up (at least in hub 1).

 

I agree that the apple vs android makes no sense, but there is a way to eliminate that, have them log in at: https://connect.insteon.com/Account/Loginand see if they can see it there. If its not visible at the cloud account, then somehow its known locally but not on the cloud (and not a problem with mobile apps).

 

Its been over a year since I used it, but I think that the credentials are the same ones you set up in the mobile app. 

 

I believe your last advice is best. Delete, and re-add it, see what happens. Somehow the cloud account lost track.

 

Paul

 

Hello Paul,

 

I appreciate the insight and also believes this high lights some of the issues that can arise from using cloud hosted services. This assumes this is the culprit in this situation.

[shannong]

How bizarre....

 

If I were said person, I'd run Wireshark to do a packet capture and see if the request is even making it in the router and to the Hub2. That would divide the problem in half at least. He has a 24-port switch so it's likely it has port mirroring capabilities.

[Teken]

Well so far the OP has changed out to another router with the same results. He has already deleted and added back one of the I/O's and its still the same??

 

I find it extremely hard to understand and believe one single device is not controllable??? Its obviously not a *normal* COM issue because he is able to control everything via the LAN. While over the WAN he can control everything except the GDO I/O's which makes no sense to me??

 

There must be some kind of cloud association that is impacting this. I asked him to use another OS (assuming he has one) because all three smartphone OS's seem to support or not support devices, features, etc.

 

I just wanted to rule out this was the cause as I know all three OS Apps were just updated and this might be a simple bug. What doesn't make sense is that everything worked and was accessible with the older HUB v1.

 

So I just don't know . . .

[shannong]

Strange indeed. Packet capture is the most definitive way to divide the problem in half. Does the request even arrive to the Hub?

 

I don't see how "cloud" comes into play. I thought the app on the phone was making a direct connection to the Hub over the internet via port forwarding on the router.

[Teken]

The OP hasn't done any packet sniffing via wire shark so can't say. I am sure there are lots of dependencies in the cloud which very few people realize are in place.

 

It comes down to how much Smartlabs wants to share with the customer which we all know is zero!

 

 

Ideals are peaceful - History is violent