Rexabyte Posted January 11, 2014 Share Posted January 11, 2014 Yes, another WeMo driver. This one, however, is different.Features:UPnP subscriptions for real time notification of WeMo state changesRelay ConnectionLight ConnectionNO PollingKeypad Connections (On, Off, Toggle)Drag and drop installationState variable, "ON" or "OFF"Programmable commands to turn the WeMo On and OffOn and Off event notificationDetects IP and Port changesFully featured 21 day trialInstallation is easy. Once your WeMo's have been setup on the network add the WeMo Controller to the project, it will scan the network for all belkin devices (this may grab motion sensors as well) and create bindings by name for each of them. Don't worry about changing the names of WeMo devices either, the underlying map for them is the UUID of the device. After that simply add WeMo Endpoints to the project and bind them to the WeMo Controller bindings. If any WeMo devices are missed simply run the "Generate Bindings" action and the controller will pick them up and add a connection. You can find all information here, as well as the download link:https://bitbucket.org/rboucher/control-4-drivers-release/wiki/Driver/Belkin%20WeMo Known Issues:Currently there doesn't seem to be a way to receive broadcasts from Control4's DriverWorks API. So, if you move your device to a different outlet the subscription will be killed and won't be reinstated unless you send a command from Control4 to it, or until the next Subscription renewal period elapses which could be up to an hour.If anyone knows how to receive multicast broadcasts to 239.255.255.250 (UPnP) I'd like to know. Note:I decided to use the WeMo device to test out my UPnP subscription stuff for the Sonos, the ice storm in Toronto delayed Sonos development a bit. I figured I'd work on the WeMo since I needed to polish up some of the UPnP subscription stuff anyway and the WeMo had a simple protocol to go along with it. Link to comment Share on other sites More sharing options...
Rexabyte Posted January 14, 2014 Author Share Posted January 14, 2014 If anyone has downloaded and is using the driver with version 1.0.26 update to 1.0.27 there was an issue in 1.0.26 that causes most of the bindings not to be generated.Be sure to completely replace the driver and not just update it, this issue has to do with the Persistent Data of the driver.Sorry to everyone that has already downloaded it. Link to comment Share on other sites More sharing options...
Ramorous Posted January 14, 2014 Share Posted January 14, 2014 Good work! Link to comment Share on other sites More sharing options...
Rexabyte Posted January 14, 2014 Author Share Posted January 14, 2014 Good news! The driver supports the motion as well. Due to the UPnP subscription and the motion sharing the same UPnP action as the switches, you can use the endpoint and program against the "Turned On" event to detect movement across the motion. It will also update the relay bindings accurately as well, and in real time.The only thing I did notice is that the motion sends a rather frequent notification every 20 seconds to the subscribers saying it hasn't sensed any motion.Note: If WeMo devices continue to use the same UPnP actions, most devices should inherently work. Link to comment Share on other sites More sharing options...
mt104 Posted January 14, 2014 Share Posted January 14, 2014 I've installed v1.0.27, put a Wemo switch on my LAN, configured it via the iOS app, and can control the switch from my iPhone. The driver doesn't seem to discover the switch. If I press "Generate Bindings" then, in the LUA window, I see: [01/14/14 23:44:11]: ExecuteCommand[LUA_ACTION] [string "Lua Code"]:1220: attempt to index global 'WeMoDevices' (a nil value) (ExecuteCommand) Did I miss a step? Or is there a problem with the driver? Cheers, Mark. Link to comment Share on other sites More sharing options...
Rexabyte Posted January 14, 2014 Author Share Posted January 14, 2014 Taking a look now.Thanks for the heads up.UPDATE: The driver was not working on versions older than 2.3 due to a call to "GetControllerNetworkAddress" this is now resolved, the driver will now acquire the address another way if it is unable to find API call.Latest version is now 1.0.28, however, you only need to update if you're deploying on something older than 2.3 Link to comment Share on other sites More sharing options...
mt104 Posted January 15, 2014 Share Posted January 15, 2014 Thanks for the superb support and speedy fix Ryan! Link to comment Share on other sites More sharing options...
Rexabyte Posted January 16, 2014 Author Share Posted January 16, 2014 Another issue was brought to my attention this morning with the light proxy binding, which is now resolved.See: https://bitbucket.org/rboucher/control-4-drivers-release/downloads for the latest WeMo files. Link to comment Share on other sites More sharing options...
jbat Posted January 17, 2014 Share Posted January 17, 2014 Great work and thanks for the fix - this works a charm! Tested with light and relay proxies. Good work. Link to comment Share on other sites More sharing options...
msgreenf Posted January 29, 2014 Share Posted January 29, 2014 How do you purchase this? Link to comment Share on other sites More sharing options...
cdepaola Posted January 29, 2014 Share Posted January 29, 2014 How do you purchase this?It's a free download Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
msgreenf Posted January 29, 2014 Share Posted January 29, 2014 my understanding is that there is a charge. Link to comment Share on other sites More sharing options...
cdepaola Posted January 29, 2014 Share Posted January 29, 2014 Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Rexabyte Posted January 29, 2014 Author Share Posted January 29, 2014 There is a cost to this driver, it is not free.It comes with a 21 day trial that is activated as soon as it is added to the project, once the 21 days elapse the driver will stop functioning and a key will need to be purchased for further use. Link to comment Share on other sites More sharing options...
THEORY Posted January 30, 2014 Share Posted January 30, 2014 The retail cost of the driver is $100, this would include remote installation of the driver. I understand many endusers here have Composer Pro, but please don't contact us wanting dealer pricing when you are not a dealer, or asking to install the driver on your own. This is the only way we can insure the driver is working and installed properly. It is not cost effective to spend time teaching end users how the whole process works and educated them about the driver. When they are not a dealer and won't install beyond their own system or make any further driver purchases the time invested doesn't make sense. So if you don't want to pay $100 for us to install, find a dealer to buy the driver and work out pricing with them if they choose to sell for less. Link to comment Share on other sites More sharing options...
bk Posted February 6, 2014 Share Posted February 6, 2014 Where does a dealer go to purchase this after a trial, I can't see it mentioned here? Thank you Link to comment Share on other sites More sharing options...
THEORY Posted February 6, 2014 Share Posted February 6, 2014 Pm or email me Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.