Thanks for the quick response. I’ve already taken option C myself with a custom DeviceHandler successfully (coming from Domoticz myself, I should way that I was surprised how easy and flexible it was) .
I understand there’s an agreement between the different vendors and providers, but I don’t agree with you in that “limbo” thing. IMHO, I see more (if not all) responsibility in the SmartThings side. Let me explain myself.
Hardware vendors provide different solutions including actuators and sensors (also more complex devices but that’s another issue). This vendors don’t necessarily tie an it’s sensors and actuators with the usecase they are going to be used for (i.e. I’m using philio PAN06 to control my 12v blinds, but I could be using it also to control an electrovalve, a garage door, etc). IMHO it’s the hubs responsibility to provide the user with the tools to take that low level actuators and sensors and turn them into top level concepts. At this point if for some reason blinds, is not the same as shades for any functional reason, then both “capabilities” should be present in the hub. So if they are not, there are only two possible responses there:
- SmartThings has taken the decision that blinds and shades are the same from the functional perspective, and thus has offered a single capability for both.
- SmartThings is lacking the blinds capability.
On the other hand we have the “user agent” provider, in this case the google home. Here there’s indeed an agreement in terms of which one is responsible of developing the bridge between both devices. In this case (may be due to the “power” of the google home devices in contrast to the SmartThings hub, or because Google can’t develop bridge for every device in the market), AFAIK it’s SmartThings’s responsibility to develop that bridge.
So assuming the first option in the list above, the bridge is lacking the mapping between the SMT shades and the GH blinds. Or, if assuming the second point, there’s a lack of a Blinds capability and it’s mapping in the bridge. In any case the SmartThings bridge lacks the mapping and there might also be a lack of a capability.
In either case… Given that Google Home already provides an API for Blinds, I think it is SmartThings’s duty to provide us users with the convenient tools to map our actuators with that API.
Any way, I understand it’s not possible to have every single functionality implemented from day one. I was just expecting some roadmap on this matter (or a workaround if any, that doesn’t imply writing my own google home commands or having to say “switch on/off” to my blinds).