I’m having an unexpected error when adding and removing devices. It seems to think I still have a weather sensor that I had removed. How can I fix this without uninstalling? Is there a way to force remove phantom devices? Or is there a way for me to find out what the device ID was and re-add it manually from the IDE to see if it can then be removed again? Every time I try to add or remove a device now I get sorry, there was an unexpected error.
or maybe there is a way to create a device from the IDE and manually associate it with nst manager?
Unfortunately I couldn’t even access the settings to turn on logging, so I’ve cut my losses and ordered an ecobee, but not before I figured out how to fix the weather and Presence DTH for all of you still using this.
For simple presence, use
vid: “generic-arrival”
For the weather
vid: “generic-motion-7”
If you’d like to change the icon, you can try ocfDevicetype: “oid.d.thermostat”
I had a really awesome version of the presence sensor working with a button to set home and away using the vid generic-arrival-4 but now that my installation is broken and I can’t login again I can’t test it further, if any of you are interested I’ll post to my github (it works, but may have bugs)
I’d really like to see a port of the homekit solution since we still haven’t heard anything from Google and early 2020 is almost over.
If you want to give it a go, here’s my presence DTH. The code is basically a mashup of the original DTH from this thread, plus the Virtual Presence Plus DTH by ajpri
I can’t help you if you have problems with it because I can’t test it anymore. But it should work for you.
My NST Manager and Nest Thermostat are still working perfectly as I never migrated to a google account. If developer or anyone wants me to doing any test to see what we can figure out I am more than happy to help?
Don’t worry I suspect we’re all going to lose access when Google forces two factor Auth later this year.
There’s nothing for ‘a developer to test’ it works if you haven’t migrated and have not updated your signin token. The minute you change one of those… Done. It’s not really worth putting any time to ‘fix’ anything until Google announces the replacement API, at which I suspect you see a mad dash tk update this and others…
Personally I hope to have found a better solution for my smoke detectors by then.
I am fortunate that currently my NST Manager is still working.
@mvevitsis You mentioned using the HomeKit solution. I presume you are referring to the fact that (somehow) HomeBridge is able to access Nest devices.
HomeBridge is available for Smartthings although you still need a HomeBridge server. I am surprised no-one has used this as the basis for adding Nest to Smartthings so far. (There is also the StarlingHome hub.)
Not knowing exactly how HomeBridge achieves this I wonder whether 2FA when Google turn it on will break this as well.
Whilst I already plan to replace my Nest Thermostat as there plenty of UK alternatives for that I would be devastated regarding my Nest Protect units as nothing else matches those.
Note: Ecobee are utterly useless unless you are American. They also don’t do smoke sensors. The only good thing I can say about Ecobee is that they support all the main smart home platforms, however sadly they clearly fall in to the too large group of US companies who feel that if you leave the USA you fall off the edge of the world.
Google and Amazon have their faults but at least they have never been so stupid and blinkered as to only address the USA and ignore the rest of the world. Amazon as an example has taken Ring and Eero and made them available globally after they acquired those companies. To those misguided US firms - Amazon and Google would never have become so big and dominant if they had solely addressed the USA.
Homebridge doesn’t allow you to add homekit devices to smartthings. It’s a one way street. In theory the web api that starling and nest for homekit use can be used with smartthings but no one has written such an app yet. I got an ecobee and I find it superior to my nest.
There has always been an alternate API to access Nest that basically imitates a mobile app.
When we decided to build out NST we had the goal of getting it certified by Nest (We almost did get certified) so we used the Works With Nest API.
We wanted to avoid any unofficial API’s because they can be disabled at any moment.
That’s sad news