I have a ChromeCast device that I use for development. I have whitelisted the device and have received an AppId.
I am also developing an application for another company. Does the whitelisting support multiple AppIDs per device? Should I have them add my device to their whitelist request, or should I update the URLs associated with my AppID to the other company's receiver url(s)?
If you want to share your device with them, you can request for more app-id/urls to be added to your device. Obviously, if you want them to use their own device, you need to get the serial number of their devices to whitelist theirs for your app or have them whitelist directly.å
Related
I have an IoT device which I wish to implement:
A mobile app - where the phone is the master when communication is initiated by the user's phone
A remote key - where a click on said key should make the iot device do something. The remote key should be paired one time with the iot device.
Now, the issue that I'm experiencing is that I can not communicate with both. I would like to enable connection with the mobile app at all time, but I would also like to listen for a click on the remote key at all time (unless I'm connected to the app).
What would be the best architecture for such communication? Who would be the master and who would be the slave? Should I use a beacon device for the remote key? What's the best practice here?
Depending on the BLE stack, a device can certainly be a Central and a Peripheral at the same time (the use of 'Master' and 'Slave' is inaccurate here).
If I understand correctly, you have 3 devices - a phone, a key, and an IoT Device. There are several options here:
Phone is Central, and is connected to both Key and Device as Peripherals. A click on the Key will notify the phone, which in turn will send some message to the Device. Pros - easy pairing. Cons - the phone app must run all the time.
Phone is Central, Key is both Central and Peripheral, Device is Peripheral. Phone connects to the Key Peripheral, Key connects to the Device as Central. Pros - Key controls Device even with no phone. Cons - probably harder to setup and pair Key with Device (depends on their I/O capabilities)
I'm just starting out writing Google Actions for some home automation projects. I can't seem to find information on how to write an action that will POST to an API on the local network. I don't want to go outside the firewall to automate devices and services located on the local LAN. I have provided an image of what I'm looking to do.
You can't do this. The Google Home device doesn't (generally) have access to the local network and aside from basic voice processing, your Actions run in the cloud rather than the local device itself.
Most devices that appear to act locally all contact a cloud-based service to do what they want. This allows your Assistant to act on them, even when the Assistant device (such as your phone) isn't on the LAN.
Your options are pretty narrow:
See if IFTTT supports what you're trying to do and either use an API with IFTTT or use IFTTT directly from the Home.
Setup a tunnel between an endpoint on the public Internet and your LAN.
Setup a cloud-based service your local device checks for state changes (there are a variety of approaches you can take here).
A variant on that last one (inspired by #Nick's comment) is to have a single local hub that listens for changes in some cloud service and dispatches those changes locally. (Again, a variety of approaches.)
If you use Google Smart Home actions you can use:
Local Execution
I do not know if they plan to extend this to Dialog Flow type actions.
I just want to know from which device logged in our website and where from (Location)
I'm currently working on azure mobile service API
Per my understanding, Azure mobile service APIs provided functions to approach resources on Azure but collect devices information.
If you want to detect device on website, I think How to detect mobile device and get user agent info send and save that information to database on server, only once maybe the similar thread on SO.
And to get the location of mobile devices on Web apps, I think How web apps ask location of mobile device will be the similar thread.
If you are creating a mobile application, and a Azure Mobile Apps with node.js as a backend for your application. We can create a custom API, and hit the API to send device information and location when your user login the app. For different platform, there are built-in functions in their SDKs to collect devices information and location.
I am working on a Windows Phone 8 app which is connected to Azure Service Bus Relay. Since i cant add Microsoft.ServiceBus.dll to the WP8 project, I had to go with BasicHttpBinding which works fine.
Now I want to use the service bus relay with topics in WP8. Is this even possible? I cant use NamespaceManager which is discussed here: http://www.windowsazure.com/en-us/develop/net/how-to-guides/service-bus-topics/ , because its not supported by WP8.
My question is simply, is this possible to do? And what approach should i choose?
We do not have any libraries that target Windows Phone at this point but are working on producing these. You can make direct http calls to the REST APIs and send/receive messages etc. Samples for these are available:
http://code.msdn.microsoft.com/windowsazure/Brokered-Messaging-569cff88
https://github.com/WindowsAzure/azure-sdk-for-java/tree/master/microsoft-azure-api/src/main/java/com/microsoft/windowsazure/services/ServiceBus
http://msdn.microsoft.com/en-us/library/hh780762.aspx
Zeezer,
"Now I want to use the service bus relay with topics in WP8"
Not sure if you are conflating two separate issues...
We do not have an SDK for Service Bus Relay for the Windows Phone. However, if your service is using any of the *HttpRelayBinding's, you can use a regular HTTP client from the Windows Phone app to communicate with the Relay endpoint for your service. You will need to include the ACS token for authenticating to Service Bus Relay in a custom HTTP header called ServiceBusAuthorization.
Lets say I have a device which my cell phone can connect to via bluetooth (it can be any device on the market...)
For being able to connect this device using a J2ME application on my cell phone, I need to discover the device first, and then discover the service which the device lets cell phones connect to.
My problem is that I don't know how to discover that service.... the device is being discovered with no problems by the J2ME application, but for discovering the service of this device, I need service's UUID and Attributes (J2ME API requirements), which I have no idea where and how to get.
Does anyone know how can I still connect the device's service using a J2ME application, without knowing service's UUID and Attributes ?
Thanks!
As far as I know, there is nothing in the API to directly do "remote service discovery", but I found this, which I think is about that:
Service discovery allows you to find
nearby services, regardless of what
devices are offering them.
DiscoveryAgent provides methods to
discover services on a Bluetooth
server device and to initiate
service-discovery transactions. Before
a service can be discovered, it must
first be registered or advertised on a
Bluetooth server device. The server is
responsible for a number of things,
including creating a service record
that describes the service offered,
accepting connections from clients,
and adding a service record to the
server's Service Discovery Database
(SDDB). In general, it works like Web
services.