Ok, but what to do with icon and partial open position?
icon will need OCF metadata updated to ocfDeviceType: "oic.d.blind"
Has anyone figured out what OCF device type to use with zigbee temperature sensors (Xiaomi)? I tried MultiFunctionalSensor but that didn’t work, and the sensor kept getting stuck at “checking status” in the new Smartthings App.
Also, has anyone figured out how to get an already installed device in the new app to reflect the changes when I change its device handler code? The old Smartthings app updates almost instantly, but the new app just does not, regardless of me force closing, clearing cache etc. Thanks!
Swap the DH to something else. And back to your updated DH. Or make a copy of your current DH and update that. Then swap to the updated DH.
The SmartThings temperature sensor uses ocfDeviceType: "oic.d.thermostat"
@mvevitsis, Unfortunately, yes at the moment. It will change during the next few months.
But look at this post and you might will be able to find a vid which fits for your needs:
No. That is still work in progress (for years now).
Sign up for the SmartThings Developer newsletter to get updates regarding these details. The last one had the update about the Vid-selector.
Where do I sign up for this newsletter?
@mellit7, you can find it somewhere here, or just register for a developer account.
Thanks, but I have a developer account and have searched, but haven’t located a place to sign up for a newsletter, which I would love to see. Not sure what I’m doing wrong, but no luck do far.
I am really sorry but I cannot find it neither.
This is what the email says at the bottom.
Connect with #SmartThingsDev
You are receiving this email because you attended our events, answered our survey, entered a raffle, or opted into our program.
Thanks for trying. Appreciate it!
The best I could find is the generic blob links: https://smartthings.developer.samsung.com/blog/en-us/
The newsletter is a mystery to me too.
Something I did notice today is that when you just ‘update’ a device in the IDE, it runs its installed() and configure() methods (if you have the Configuration capability). If you actually change something before updating, the updated() method is run too. That seems to correspond with metadata changes becoming visible to the mobile app. So rather than mess around changing the device handler away and back again, just changing the device name might suffice.
That said I can’t get the app to refresh reliably and even if it does I don’t know what it is displaying. It would be useful if the device ‘information’ page said what profiles / plugins / guesswork it was using.
I’m actually trying to use an organisation device profile. I’m not even sure if I am spitting in the wind or if it is sort of working.
Update: I have now received version 1.7.44-21 of the Android app, and I am finding that if make a change to the device in the IDE and then update it, the app picks up any metadata without any need for clearing of caches or forced closures. However what it doesn’t do, in my case, is immediately detect changes to the device profile I am using. Those changes seem do seem to work through eventually. On the other hand maybe I am misinterpreting what I am seeing.
maybe @erickv knows how to get signed up for the SmartThings Developer Newsletter?
interesting. You happen to find one with presence and switch?
I understand your idea, but will that work when you try to re-connect your rewritten stuff? -I mean the Nest authentication.
So which vid has presence and switch?
Hello, @Automated_House
Here’s the link to sign up for the SmartThings newsletter.