I wanted to take a bit of time to respond to each of these points with my own views on them. Again, these are my (not SmartThings - unless specified) timeline estimates for each (now w/bullets):
- Android still doesn’t have persistent image access, which means cameras are useless
It appears that some cameras behave differently with this and we will investigate the behavior — especially as we add new cameras to the platform. I think we’ll be adding several more cameras before the end of the year.
- Can’t send MMS or email with or without an attachment either
No timeline that I know.
- No user level support, so I have to annoy my wife with all my alerts
Before end of year we should be rolling this out.
- No official Nest support, I get 5-10 requests a week to make my device “Official”
We have to change the way our platform handles data retention before can officially support Nest. This has also held u some unofficial releases that 3rd party developers have submitted as we didn’t want to “blur the line”. Expected Q4.
- IDE is a mess… It has become a slow, annoying pile of lack of debug logging because the response is too big, it doesn’t feel like it or somewhere my code is wrong, but it doesn’t know where…
The Developer Tools project has kicked off in earnest and is getting greater visibility as it is clear that we need to improve in this area. Incremental changes should be seen throughout the next few months.
- Sure, promises for a better IDE are thrown around, but no timelines given.
See above.
- SmartAps that spawn child devices can’t even be logged properly
This should be a part of the IDE and logging improvements mentioned above.
- Temp sensors are so random, I’m not sure what climate I live in.
Need more data to go on. I am under the impression that these are much better now (especially with v2 devices) and of there are consistent variations they can be addressed with user over-riding offsets.
- Local IP support for devices / SmartApps is non-existent… The answer is write it yourself…
Not sure what this means. We have several LAN-based integrations. Additional sockets and communication options are available with latest and upcoming firmware updates. 3-6 weeks.
- The SmartApp UI sucks, no real way to get a users input unless they are configuring the App. Even then, its a mess of dynamic pages.
We are looking at ways of addressing SmartApp display though the use of “HTML Tiles” where HTML, CSS, and even JavaScript can be used to get the appearance desired. Perhaps some of this will spill out into the configuration options available to developers. Q4
- Android presence is broken, every time I reboot it says I’m gone then back…
As we discussed on the call, I am not sure the behavior manifesting for you is a bug. We can certainly look at ways to cache last event state but that seems a bit like overkill. If you will, please write up the way you would prefer this behave and we can look into it.
- Andorid ChartTile doesn’t work, but promised another method, no timelines
Still no timeline because I need more insight into this. @tonyc what say you?
- No way to dynamically create, modify or hide tiles in a device type
Perhaps this will be a part of the HTML tiles mentioned above. Please define your desired use cases?
- UI for the Things area constantly resets.
Need more info/screenshots/videos.
- No support for streaming video
Unlikely in Q3/Q4. I would expect it soon after.
- No UDP support for local hubaction
I lose track of this one as I have gone back and forth to developers on it a bunch. Maybe @doug-st knows something about the timeframe for this.
- No response from Raw socket sends
Ditto - @doug-st or @scottvlaminck
- Truncated responses from local hubactions, its a mystery as to how big a response can actually be.
Maybe we are getting out of my realm of comfort here. Unsure on scope/timeframe.
- Have to create a smartapp or device just to browse other sample apps/devices
This should get much better as a part of IDE improvements. Additionally, for me, a goal is to get addressable SmartApps and Device Types that can be shared by URL Likely 2015.
- No tablet version, iOS or Android
1st half of 2015
- No Windows mobile
Next week.
- No windows app
Before the end of 2014
- No web interface for end users
Near and dear to me but not likely to get built until first half of next year.
- No list view in devices for showing data in a response
- No scene support
I am not convinced that scenes are needed. I am NOT saying that they could not be valuable but I do think their advantages can be achieved with current methods without the need to add ANOTHER construct to the world of SmartThings. The more we add the more complicated it is. I would rather see Hello, Home actions have more context awareness, for example, and act as a traditional scene.
- No offline or cached mode if internet connection is down…
Hub v2. Q1 2015.
- No ability to sort devices in IDE also in Apps, etc.
Hopefully in the next few weeks with the new Developer Tools-focused sprints.
Ok, I am going to bed.