Jenny and I divided our prioritized tasks for the week. I drew the short straw and ended up with all the Helios related tasks. Thus begins this tale of woe.
Helios (the version running on upod-dev) currently is unable to communicate with Hue lights, and the OpenWeather functionality is also down. While the Hue light logging is working on the local version of Helios — suggesting that the problem is more on the system admin side — the OpenWeather feature is not working on upod, upod-dev and local instances, hinting that the problem is code-centeric.
T-staff says that all the ports we requested to be opened, were already open and functional. The situation is at somewhat of an impasse, and until we learn of new ports to open/configurations to change the Hue problem will likely remain unresolved. The OpenWeather problem hopefully will be simpler to fix (their API is extremely straightforward).
Now for some good news! (Transitions between emotions are abrupt when working on Helios.)
The Helios master branch merged with the multisensor branch bringing about the long-awaited version 2.0 of Helios. This also made it easier to test the door-sensor model for Helios which is also slated for merging. Even better, the door sensor logging is now live and fully functional. By writing a custom SmartApp we were able to make the necessary HTTP requests to get SmartThings and Helios talking. This alliance allows for fairly rapid device addition, and the number of devices available to us will only continue to grow as does the SmartThings platform.
Further, given our new understanding of APIs it will be possible to design an API that taps into the device control functionality of SmartThings, allowing for end-user interface prototyping (getting there will be time-consuming, but it is certainly now in the adjacent possible).
Jenny will be posting later in the week (or to be more accurate — next week) with the progress on the other priority items.