When using GH device integrated with Dialog Flow, while conversation starts from google home and back to webhook requests, can we get the the GH device details, like the speaker name, IP, WAN IP if used?
No, the data that would identify an individual device are not provided to your Dialogflow agent.
Related
So I was messing around with the nearby share feature that google launched last year and I noticed that if you connect your Gmail and have a profile picture , when you try the nearby share feature the other person can see your profile picture. How is this possible if you haven't made a connection between you and the other person yet? Does google save the MAC address of the user and then pulls it off a server or something? I'm pretty confused. I found this post (How is Google's nearby share implemented? ) that is broadly talking about the implementation but only thing mentioned is that they tried to bring more of an identity to this feature. So how does the contact info show without connecting? Is it that when someone is on your contact list google has just saved their device name or MAC address and that's how it knows what profile pic and Gmail to use/show on the nearby devices?
Each device generates a certificate (containing the device's name, photo, etc) and uploads them to a Google server. The device then uploads a list of contacts who are allowed to download that certificate.
Devices periodically download certificates they have access to. Other than the start/end timestamp, the data in the certificate is encrypted. You need to see the decryption key over Bluetooth in order to parse the certificate, after which you can now attach a name to the Bluetooth advertisement you just saw.
I am using google cloud functions to execute the node.js code which creates a payment-intent and passes the client-secret to the client (i.e browser) in this case. However when a payment is completed i am getting ip address of google's server which are most likely hosting the code of google cloud functions.
I need to pass the ip address of the browser somehow so that client who is making the payment's ip address is visible and not the ip address of google's server.
I tried looking into stripe's documentation but cannot find any way on how to achieve this.
Note: It is recommended to create payment intent on server side and not on client side by stripe.
The reason you're seeing your server's ip address is likely that you are creating the PaymentMethod server-side. This means your server gets that raw card details which puts you in the highest scope for PCI compliance, SAQ D.
The IP address here should instead come from the browser where you would collect card details securely via Stripe.js client-side. The idea is that you would be using Elements, collect their card details and then create a PaymentMethod (or a Token for legacy integrations) and then use that id server-side to confirm a PaymentIntent or create a Charge.
If you have to pass raw card details server-side, you should talk to Stripe's support team instead to discuss your integration.
Is there a way to identify unique google home device under same user account from dialogflow webhook request?
Currently i identify the user from dialogflow webhool request using the following parameter:
originalDetectIntentRequest>payload>user>userId
But under same account they are same.
No, you are able to identify the user of the request, but not the device itself.
Is any android API support for the following status of the nest smoke and carbon monoxide detect:
(1) When the device is on
(2) when the device is off (the batteries are removed)
Yes, if you follow the instructions provided by Nest Labs in their github account, you should be able to receive information from any nest device associated with your home.nest.com account. Create a nest developer account in console.developers.nest.com and add all devices you would like permissions for. then follow steps to receive a nest access token. with the token you can authenticate your account and initialize listeners. the smokeCo alarm listener should give you all the current info regarding the smoke alarm, last test, status etc.
Good luck.
I am creating a j2me application for mcommerce, which uses mobile internet(gprs). I wanted make it more secured by binding the application to the SIM card and the device. That is a user should be able to login to the system, only using his/her SIM card or from the registered mobile number.
To achieve this I need to fetch the mobile number.
So, on login i thought of Triggering an SMS from the server with a key, which the application reads and uses the key for the entire session. Here the challenge is, that sms should not go to the inbox.
Any suggestions pls?
Yes it can be achieved using the Wireless Messaging API. Have the MIDlet set up a server connection on a chosen port number, then send the SMS to that port number. It will go straight to your app, bypassing the inbox. If you use the Push Registry, you can even make the SMS start your app if it is not running.
It doesn't matter if the user sees the number in his/her inbox.
As long as the key is only used that session, it is her/his responsibility to not share the key with others.
The one thing you make sure is that ONLY the person who owns the SMS phonenumber gets the key and is able to log on.
This doesn't take care of the phone being stolen though.