I have a Windows-based Java program that calls a PHP file passing to it several parameters. This same PHP file takes the parameters and generates the appropriate URL to send to a ST endpoint device to turn it on/off. The created URL is logged (for debugging purposes) then sent such as "http://graph.api.smartthings.com/api/smartapps/installations/…"
The state of this ST device never changes when called via the Java program, however, I can take the same URL from the log, plunk it into the browser address bar and the device state changes accordingly. In fact I can manually call the PHP files with the appropriate parameters identical to that passed by the Java program and the ST device responds accordingly.
My first reaction was to assume that the problem lies with the Java program even though I confirmed that the URL generated through this method is working properly when passed via browser. However, to confirm there was a problem using the Java program method, instead of calling “http://graph.api.smartthings.com/api/smartapps/installations/…” I changed the URL to several different sites (i.e. http://homeAppache.server.com/event/OfficeOff) and noticed that each of these worked as expected.
After several days of trying everything under the sun to get this to work I have come to the conclusion that the “problem” (maybe some security thing?) lies at the ST end. I base this conclusion on my work over the past week AND some very similar behaviour I found using Alex ActiON Dashboard". In the case of the latter, the Dashboard will not load the video of 2 of my cameras showing the typical “broken link” icon. If I right click either of these and “Inspect the element”, copy the URL found inside the source file, paste it into a browser address bar then refresh ActiON Dashboard, it will now display the video for that camera. Like in my case with the Java–>PHP problem, ActiON Dashboard file generated the correct URL but ST does not respond accordingly. That same URL can be copy and pasted into a browser address bar and the end result is as expected.
This one problem is the only obstacle in my way of totally integrating Wemo device into ST. I am lost at what to do next. Anyone have any idea where I can look for a solution to this or who I can contact regarding this issue.