I am using sample application control-jquery-master provided on developer.nest.com. I can access first device for e.g. thermostat as written in the code. It shows on the html page http://localhost:8080 with status "INSIDE" and two buttons "UP" arrow and "DOWN" arrow. Now, I want to add my own device instead of "thermostat" something like "mysensor" with different properties that can be set or retrieved. Is it possible to do that? If yes, what are the API, If not does it mean we can only use thermostat, smoke detector sensors which are provided by nest?
My question is how to access and modify the JSON document? Where is it stored?
Best Regards,
Sonal
The only way to add your own sensor(s) to the devices JSON payload is to make use of the Product data read/write permission.
This Nest API doc outlines the steps necessary to reach a working implementation.
The only way to add more physical Nest devices to an account is by doing so on their site or with their app. You can add virtual devices using their Chrome extension: Nest Home Simulator
Related
When using the API to communicate with a Nest Learning Thermostat (in this case using the nest home assistant integration), when a request is made to change the nest thermostat to the "OFF" mode, I can see the mode show as "OFF" on the home.nest.com website, however the thermostat doesn't register it at all and just stays in whatever mode it was already in. Curiously, when I select "OFF" on the home.nest.com site the OFF mode that's displayed on the site has a leaf icon under it, while when I do it via the API it does not. When selecting it on the site the thermostat does switch to "OFF" with a leaf icon displayed under that on the thermostat as well. It seems like the API is sending an "OFF" state that the home.nest.com site can see but that the thermostat itself just doesn't respond to at all for whatever reason. It's like there are two different off commands here and only one of them (whatever the nest.home.com site is using) is working, and whatever the API is using is not. Seems like a bug but I wasn't sure if I'm just doing something wrong here or what. Just wanted to mention it here so that it will hopefully have some visibility from the devs. Thanks.
API bug confirmed, seems to be fixed here: https://github.com/home-assistant/core/issues/60941
If you see the leaf icon on the home.nest.com site, then the thermostat is in Eco, and the ThermostatMode.SetMode command doesn't work when the thermostat is in Eco: https://developers.google.com/nest/device-access/traits/device/thermostat-mode#setmode. You have to use the ThermostatEco trait instead.
I have a long-standing account with 2 nest thermostats in it, that I use to test my Nest device access integration. I recently added a Nest Hello to the same account, which works and displays fine in the Nest app.
I used my Nest device access integration to query the devices, and the nest hello is not reported.
I re-oauth authorized, and the nest hello doesn't show in the choices of devices to enable access to (see attached screen shot).
Is there some setting in my device access project to enable doorbell access that I've missed? Any other ideas what could be wrong?
Faced the same problem with a nest camera. The image was showing in the nest app but the device was not listed. I added the nest device as a new product and it started to be listed properly.
i have page in which i have image of watsapp icon. What i want is when i tap on that image it go to watsapp to specific number which will be our company number, so client can text us or send any image or file through watsapp
The easiest way would be through the custom URL scheme as described here: https://faq.whatsapp.com/en/iphone/23559013
Which basically tells you to open a URI like this: whatsapp://send?text=Hello%2C%20World!. You can simply open it by calling to the Device.OpenUri method of Xamarin.Forms. This should work cross-platform for iOS and Android.
If you want to share a photo immediately this isn't possible as far as I know. It is possible to someone that is in your recent chats, by the sharing API, but to my knowledge you can't send it to a random number. At least not for iOS, it might be different for Android.
I am currently working on a receiver app through Google Cast SDK Developer Console, and when trying to style the default receiver app created by google, through my own CSS file, in order to preview these changes it asks for a URL to my CSS, I can't figure out what exactly it's asking for in that part so I can't preview my own styles.
I know the question is old, but answering for people looking for a solution to this question.
Question posted has as lot wrong in terms of understanding the google cast receivers.
So basically the user is trying to create a style for the styled media receiver.
Google cast provides 2 ready made receivers : Default and styled. You cannot do anything to the default receiver to customize it. Its just plain default receiver.
In case you want the receiver to show your logo, splash screen as well as watermark while starting the cast then you use what is known as the styled media receiver.
Now going back to the question. It is asking for a URL is because google style media receiver when invokes, needs a css input so that it can show the logo, splash screen etc. basically the UI of the receiver which is playing the cast stream.
Why the URL? Because the URL is a direct downloadable link of the css which the style media receiver downloads and projects.
You can use your own google drive account to host the css file and provide the URL.
Refer to this link for details:
http://www.oodlestechnologies.com/blogs/Building-Styled-Media-Receiver-Application-for-Chromecast
In my Apple Watch app, I need to have a way to be able to notify the user that they must first set something from within the iPhone version of my app before they can use the Watch App. Obviously, I need to do to this through a few labels and images, however the layout of these is different to the layout of the main views in my app.
How can I present the user with a different view based on the status of the iPhone app, that they cannot see unless required? The way I would do something similar in a normal app would be to just push to a different view controller, but obviously this is not possible in a watch app.
Any ideas?
You could always present a modal interface controller. Alternatively, you could create a separate group in your root controller's view and show/hide that as necessary.
To check the status of the iPhone app, the easiest solution would likely be to use a shared NSUserDefaults suite between the iPhone app and the Watch app. Set a value to true/YES when your criteria has been met and check that value in the Watch app.