|
Meredith W Posts: 10
10/11/2015
|
So weird. I have 3 of them and it doesn't see any of them. I can see them in my network from my computer and within the WeMo app....just isn't appearing in CastleOs. I'm on Windows 10, would that be an issue?
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
10/11/2015
|
Not that we're aware of...
|
|
|
0
link
|
|
Meredith W Posts: 10
10/11/2015
|
Chris Cicchitelli wrote: Not that we're aware of... Well maybe one of these days it will suddenly appear.  Thank you for taking the time to try to help Meredith
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
10/11/2015
|
I'll continue to do some digging, there's a bock somewhere, we just need to find it
|
|
|
0
link
|
|
Meredith W Posts: 10
10/11/2015
|
Awesome, thank you
|
|
|
0
link
|
|
Josh Posts: 3
10/11/2015
|
Are you able to ping the wemo device(s) from your CastleOS computer? If so I'd expect disabling AV and Firewall temporarily would at least get them in and working temporarily. Not sure how often CastleOS polls for new devices but it may need to sit for a little while after the firewall is turned off. If it doesn't work to ping them, maybe they're on a guest wifi network or something isolated from the network the computer is plugged into?
You can find the IP address to ping them from your router DHCP lease table or if your phone is on the same network, Fing is a great network discovery tool. The wemo(s) will show up as Belkin in that list and you should see your castleOS computer as well. My wemo outlets start with EC:1A:59 for the MAC address.
For anyone looking to add specific firewall rules for Wemo after they're working, I had to allow outgoing TCP ports 49152-49154 for CastleOS to send on/off and check status. I turned the firewall off while discovering devices so there might be additional ports needed for adding new ones.
|
|
|
+1
link
|
|
Josh Posts: 3
10/11/2015
|
Looks like 49155 may be used too... If CastleOS just checks port 49153 that could part of the issue, it sounds like newer wemo versions tend to wander to a few ports (49152-49155)? If you're using Fing on a smartphone, you can add these ports to the scan via tools (gear icon) -> edit tcp services -> add service. Then in your list of discovered devices, you can select a wemo device and hit service scan to see which ones are currently active. Josh wrote: Are you able to ping the wemo device(s) from your CastleOS computer? If so I'd expect disabling AV and Firewall temporarily would at least get them in and working temporarily. Not sure how often CastleOS polls for new devices but it may need to sit for a little while after the firewall is turned off. If it doesn't work to ping them, maybe they're on a guest wifi network or something isolated from the network the computer is plugged into?
You can find the IP address to ping them from your router DHCP lease table or if your phone is on the same network, Fing is a great network discovery tool. The wemo(s) will show up as Belkin in that list and you should see your castleOS computer as well. My wemo outlets start with EC:1A:59 for the MAC address.
For anyone looking to add specific firewall rules for Wemo after they're working, I had to allow outgoing TCP ports 49152-49154 for CastleOS to send on/off and check status. I turned the firewall off while discovering devices so there might be additional ports needed for adding new ones. edited by Josh123 on 10/11/2015
|
|
|
+1
link
|
|
Meredith W Posts: 10
10/16/2015
|
I was so hopeful, but opening those ports didn't help. I have their IP address and they appear on my router along with my CastleOS computer. The WeMos are just not seen within CastleOS itself. Thanks for the suggestion.
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
1/15/2016
|
Hey Meredith and others, we've done quite a bit of work on WeMo and have results to report back. There are a couple of distinct things going on.
WeMo devices use the UPnP protocol, and as part of fixing our Sonos issue and preparing for a Linux port, we decided to swap out our UPnP driver for a new one that will work on both Windows and Linux, which we successfully did. However, in doing so, WeMo broke. In investigating why, we learned quite a bit about WeMo and the issues we've been seeing.
WeMo has two distinct bugs that were causing issues. First, it had network discovery bugs, even on the best day. Meaning, network discovery has never worked as intended. Meredith, I think this is why WeMo was never detected on your network. Just before Christmas, WeMo released an update that specifically addresses this. We were never able to replicate this specific discovery issue on our end, so Meredith I'll have to ask you try with the latest WeMo firmware and see if CastleOS can see them now.
Now the second issue is related to why we're not able to use the new UPnP driver with WeMo. In short, WeMo is using a malformed version of UPnP, and our new code is a "strict" processor. WeMo is aware of this issue and promises to fix it, and we hope that the workaround put in place (the old UPnP driver is running side by side with the new one for Sonos etc) means no one will notice an issue.
Please let us know how you make out!
Thanks,
Chris
|
|
|
0
link
|
|
Dominique Garcia Posts: 55
3/23/2016
|
So I have been away for a little while. I reinstalled CastleOS and went through the setup configuration. However, my Wemos and sensors are not being detected. My Nest is, but that is about it.
Anyone have any ideas?
I have 2 Wemo switches, 1 Wemo motion, 1 first gen Wemo plug, 1 Wemo insight
SmartThings hub, 2 ST sensors (which are zigbee I believe) and 1 zigbee plug.
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
3/23/2016
|
Hey Dominique, welcome back! Were they detected with your previous CastleOS trial, or have they never been detected?
|
|
|
0
link
|
|
Dominique Garcia Posts: 55
3/24/2016
|
Chris Cicchitelli wrote: Hey Dominique, welcome back! Were they detected with your previous CastleOS trial, or have they never been detected? They were detected a while ago. That was on another computer and like a year ago. If you look on page 1 of this thread I mentioned that it worked with my setup. However in 2016 it doesn't. edited by dominique on 3/24/2016
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
3/24/2016
|
Any chance you replaced your router in that timeframe?
|
|
|
0
link
|
|
Meredith W Posts: 10
3/31/2016
|
Chris Cicchitelli wrote: Hey Meredith and others, we've done quite a bit of work on WeMo and have results to report back. There are a couple of distinct things going on.
WeMo devices use the UPnP protocol, and as part of fixing our Sonos issue and preparing for a Linux port, we decided to swap out our UPnP driver for a new one that will work on both Windows and Linux, which we successfully did. However, in doing so, WeMo broke. In investigating why, we learned quite a bit about WeMo and the issues we've been seeing.
WeMo has two distinct bugs that were causing issues. First, it had network discovery bugs, even on the best day. Meaning, network discovery has never worked as intended. Meredith, I think this is why WeMo was never detected on your network. Just before Christmas, WeMo released an update that specifically addresses this. We were never able to replicate this specific discovery issue on our end, so Meredith I'll have to ask you try with the latest WeMo firmware and see if CastleOS can see them now.
Now the second issue is related to why we're not able to use the new UPnP driver with WeMo. In short, WeMo is using a malformed version of UPnP, and our new code is a "strict" processor. WeMo is aware of this issue and promises to fix it, and we hope that the workaround put in place (the old UPnP driver is running side by side with the new one for Sonos etc) means no one will notice an issue.
Please let us know how you make out!
Thanks,
Chris I meant to respond to this earlier and then forgot. Sorry! I updated my WeMos and nothing changed. My computer sees the WeMos but CastleOS still cannot.
|
|
|
0
link
|
|
Chad Sims Posts: 1
4/10/2016
|
I am having the same issue with wemo devices not being detected by CastleOS. I can ping and see the devices listed in Windows Networking so the devices are discoverable via Windows 10. I am running a demo of CastleOS version 1.3.2212 (merrimac). Not sure if it helps but I have the following wemo devices:
WEMO smart switch - model: F7C027 - firmware: WeMo_WW2.00.10062.PVT-OWRT-SNS
WEMO smart switch - model: F7C027 - firmware: WeMo_WW2.00.10062.PVT-OWRT-SNS
WEMO Insight - model: F7C029 - firmware: WeMo_WW2.00.10062.PVT-OWRT-Insight
WEMO Insight - model: F7C029 - firmware: WeMo_WW2.00.10062.PVT-OWRT-Insight
WeMo Link - model: F7C031 - firmware: WeMo_WW_2.00.10114.PVT-OWRT-Link
Belkin netcam - model: F7D7601V1 - firmware: WeMo_WW_2.00.10062.PVT-OWRT-
Belkin netcam HD - model: F7D7602v1 - firmware: WeMo_WW_2.00.10062.PVT-OWRT-
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
4/23/2016
|
Just wanted to let you guys know we're still working this issue. Unfortunately we're on edge cases here, so it's proving difficult for us to reproduce internally in various tests despite confirming it externally...
|
|
|
0
link
|
|
Elgato Inthapants Posts: 10
6/4/2016
|
Just wanted to add my 2 cents. Wemo insight plug can't see it in castle OS,but can see in wemo app.
Windows 10 homemade hub.
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
6/4/2016
|
Which model?
There is an improvement in the upcoming beta for WeMo.
|
|
|
0
link
|
|
Elgato Inthapants Posts: 10
6/11/2016
|
F7C029fc the model of wemo plug in my above post
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
9/7/2016
|
The WeMo driver has been updated and will be in tonight's release. The Insight will now self-report it's current power status to CastleOS.
|
|
|
0
link
|