SmartThings services were shown off a bit. Hard to talk to these since Air and Energy don’t exist in the USA (that I know of. They may be hidden since I don’t own any Samsung appliances). Overall it’s a nifty way for Samsung to use the data that their appliances are generating in a way to provide benefit to the owner
Here’s some slides from the UI presentation. Before you ask, no details on how to customize the UI plugin for hub connected devices. I even asked her after the presentation if that was coming, but she way strictly UI design, so no idea on implementation details for hub connected devices
Now two options for a WASH product: embedded or a dongle. Here’s the new SmartThings Link Dongle. I know Vodafone will be using it, not sure if Nvidia will switch to it or not.
hardware requirements for a WASH product. Note that the ST hub piece is on a separate container so that in theory it can be updated separately from the host device and be kept up to date.
Not at all, the slide obviously had the input of some marketing scholars
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
60
Another platform initiative that was already being officially talked about (in Session) at SDC’s 2 (or even 3) years ago, and which already manifested itself in the NVIDIA Shield and ADT Security Hub products.
So the only consumer facing news here is that there are a “few” additional actual partners implementing it (without mentioning that ADT abandoned their implementation).
The Hub is such a critical piece of the infrastructure, I’m not sure if consumers actually get practical benefit from WASH. Sure - it’s one less device to plug in, and a small cost savings, but a boatload of additional support issues, inconsistent firmware, etc… (My Samsung SmartThings WiFi system already receives firmware updates significantly later than standalone Hubs!).
As an idea - WASH is great. Reality may be different. The time spent since the initial discussions probably ironed out some concerns.
One of the WASH guys mentioned that they’ll be able push patches for just the WASH part of the device on some of the newer integrations. He likened it to a containerized infrastructure where you could update just one container without having to update everything else (eg. update the WASH part without updating the whole device firmware).
A very similar to approach to what they are using with the Samsung SmartThings Wifi.
It kind of reminded me of how Google learned this lesson with Android. They started breaking out key parts of Android so they could push smaller patches to critical components rather than having to wait for major OS patches.
Was anything mentioned at the conference regarding Z Wave S2 security? I know they’ve been working towards that but I haven’t heard anything in a few months.
Yeah, so at the moment, our hubs are going through Z-Wave certification, we are hoping to have that completed as soon as possible, and after that we would then have to coordinate the release of the mobile app release and the firmware.
I may sound like a broken record, but the great aspect of Z-Wave is that they really focus on interoperability, so when we do release Z-Wave S2, we are going to interoperable with all Z-Wave S2 devices and other devices.
Just to be clear, though, “interoperable” does not mean “support all features of all zwave commandsets,” right? It’s just interoperating at the Basic level (which is all that protocol certification requires for most device classes).
We’ve already discussed a couple of commands in the forums that are not going to be supported in the future.
Unless I’m misunderstanding what Jody meant, and he was just saying that it wouldn’t be available as part of the official features, not that the commandset itself would not be supported.
@Kianoosh_Karami what @JDRoberts is referencing is that there are some ZWave command classes that we do not have capabilities for. Specifically 4.113.3 User Code Get Command. While we do technically have a way to send any custom command we do not have a capability or official API support for it.
