@jody.albritton, finally I have some better internet connection and managed to log in to the developer workspace. My concern was the “organization” assignment. Previously (months ago) when I logged in, I had to assign myself to an organization. I see that restriction has been removed, and I can create project, device profiles etc. It is indeed really impressive. (Maybe we should move this discussion to a different topic.)
By looking through the developer workspace menus and at the functions it makes more sense the integration to the new app. Indeed, I am really impressed. It feels a bit awkward after the groovy way, but makes sense and probably gives at the end a better end user experience. I am away from home, but I have a NodeMCU with me, so I will try to build a basic project with the example what you have linked above.
The only disappointment what I have is the list of capabilities and the documentation. There are capabilities what are in use by some of the official new integrations, ie. Audio Notification, by the new Sonos LAN Websocket DH, but it is neither documented nor listed on the place where the device profile has to be defined.
Actually most of the capabilities of the Sonos DH are not documented in the developer workspace documentation, but listed in the old SmartThings documentation pages only, and that is obsolete, I guess.
And just for @Automated_House, Jimmy, you need to log in and start to build a device profile. It gives you the new UI options how it will look like the integration in the new app. You are going to like it.
Thanks again for the heads up! If you can give some details how is the Zwave/Zigbee integration can be done with the new capabilities and device profiles that would be great. (I had just limited time now, and I would really appreciate a pointer how could I integrate my DH of window shade/rolett controllers and some iTRVs)
Really great work! Thanks!
@jody.albritton what I dont quite understand is that you have MQTT supported as both the broker and the client in Smartthings, but why cant we use MQTT to talk to any MQTT device? why are we restricted to just the specific Device SDK?
I thought the point of MQTT was to be device independant so we can then manage the message and do something with it!
If you are restricting MQTT to just your own client, then your missing the point of it.
Tasmota has MQTT built in, so why couldnt we just use MQTT to talk to it and controll it?
@DrJon there are several solutions to the problem you have. If you have Sonoff switches and dont want to flash them, you can use MQTT as explained by @Tech_GFam
BUT there are other solutions. Many people flash Sonoff with Tasmota, and there are some good videos on how to do this. Along with an extensive community and support. The wiki is very clear on how to do this.
There is also so custom F/W someone wrote with a specific ST application which creates the drivers. I personally didnt like this route because it was only a subset of the devices out there. BUT it might suit some people.
There is also Betts device drivers which some people are happy with… Personally I use this and have it working with touch switches, minis, ifan03, and the shelly 1 which was flashed with tasmota.
BUT if I had found the MQTT solution sooner I might have only used this option. Instead I will be going down this path in the future as I have a Shelly 4 pro which wont work with tasmota.
Our implementation is a direct cloud connection scenario that does not require any middleware. Our design is such that you do not need a cloud based device handler. All of the knowledge of or capabilities is baked into the firmware. This is just one way of using MQTT. I think your broader question, (correct me if I am wrong), is can you subscribe to our MQTT service and get events and then can you send command events in from a non-device source.
Ok so I get what you are saying
And so Yes my question is why can’t you subscribe to topics from Non ask devices to get status and send commands? Which you are implying we can’t.
Therefore isn’t saying you are using mqtt misleading, because all you have done is provided a device client you can easily discover and communicate to; and users have a customisable client they can install. the communication protocol just happens to be mqtt but could have been anything.
MQTT is just the transport in any case even Tasmota. Tasmota could be used to create a generic client where you configure the MQTT server of your choice. Our device-sdk is meant specifically for directly connecting devices to the SmartThings cloud in an easy fashion. The SDK is the sum of all of the parts you would otherwise need to assemble yourselves to build the same thing. In the generic messaging scenario you would send arbitrary messages to the bus and then need to interpret them in some handler, our SDK has a specification for pub/sub in a way that is specific to the SmartThings cloud, removing the need for a separate device handler. There is nothing preventing you from making your device available to other systems.
Sorted, bought one, installed and much better than using the tasmota flashed version.
One thing I’m struggling to sort is, I have the sonoff connected to my kitchen Light which is a tube light. I want to set a timer for it so it automatically turns off after a certain time, say 30 mins. How can I do this pls??
then you need to add a virtual device to your smartthing put on your virtual device your device IP address, and the port
then go to your phone add things to discover your device
Hey, could you please eloborate on how to create a virtual device? No matter how hard i google only results a get is “how to create virtual switch” I guess that doesn’t help me right?
In my app, (i’m using the new one) it seems impossible to create a virtual device, again no matter how hard I google all results are guides on how to do it in the old app. TBH that’s fair if it is actually not even possible to do in the new app, what’s not fair is that they didn’t provide that feature… Anyway I’ve also tried to look in the web IDE under “My Devices” > “New Device”… but here I am met with a form, that doesn’t seem to allow me to create what I need:
I guess Name is a wildcard, Label and Zigbee id no need. But Device Network id what is that? Is it the device network name ? i.e. tasmota-4456 or is it the mac address of the device? perhaps the ip that it is currently on? It’s not clear to me, but I might just not know the term “Network id”. As for Type , what do you chose there? There is neither any sonoff or tasmota options to select, what should I chose instead?
Were you able to get Tasmota flashed to your Sonoff mini? I spent about 2 1/2 hours with a learning curve flashing Tasmota OTA to 9 Sonoff mini’s last night, making me think putting 8 wyze bulbs in all of the light fixtures a much better idea than all of the wiring still ahead of me. Oh well, right.
