I am integrating a simulated service with a Raspberry that sends temperature signals to an Azure IOT-Hub service, where I process the events through Azure Stream Analytics and display them in a Dashboard in Power-BI. So far so good.
I have problems when deploying them in Power-BI. Shortly after the service starts, the Dashboard begins to have delays in the refresh rate. I would like to know why this happens?
Is it necessary to have a larger Stream cluster?
Is Power-BI an issue with refresh rate?
It can be fixed?
From already thank you very much.
Regards
Related
I'm building an app in which one component is uploading/downloading data from an azure blob. I have been looking for ways to make this run in the background so that the processes aren't interrupted when the app is minimised or the phone is put to sleep. I don't need to support these processes when the app is killed. Is there a way to do this?
https://github.com/Azure/azure-storage-ios/issues/81 was the only relevant thing I could find, and it doesn't offer much.
Does anyone know how this can be done?
I am building local teams chat integrated with a product using Microsoft graph API toolkit. I am using mgt react Get Component to pull the messages from the channel . I am using polling rate as 3 seconds as I want to pull the messages from teams near real time .
I am also using cache for 24 hours invalidation period for the Get component
By any chance this will lead to throttling issues or graph API toolkit manages this internally?
Attached is the screenshot.
screenshot (https://i.stack.imgur.com/UqaZ9.jpg)
I'm working on something where my iOS app will give 2 input parameters to some server side setup. The server side will periodically run a google API network call and get its result response X. When this X is the right answer, I want the server side to send my iOS app a push notification. This needs to happen for every app user individually.
I know the iOS coding part, and also know how to setup a iOS push notification.
But what’s the best way to setup this server side code? Are there some free cloud instances that I could use?
I’ve looked into Firebase and Google Cloud console that I can combine with a cron job to make regular network calls, but they seem to have a fair bit of complexity involved (especially since it’ll be inputs from per app install so it'll become one cron job per app install).
Is there a better way to achieve this?
figured it out.
for future visitors, i’m writing how i achieved it -
the client sends inputs to the firebase DB, and a firebase cloud function scheduler periodically reads those values to calculate output from google api call. when the output is right, the firebase cloud function sends notification to the client
I am trying to integrate smart home devices with Google home and Alexa but I am facing following issue.
Communication between Google Home/Alexa and our device cloud server is HTTP.
Communication between smart home device and our device cloud server is MQTT.
How do I keep track of synchronous request-response? Is there a better way to implement this system?
Perfectly possibly to do with HTTP to MQTT and back again.
I've done it for both Alexa & Google Home for my Node-RED nodes.
You just need to keep track of on going requests and include a unique id in the request/response MQTT messages while also running a timer to handle no response from the device.
The project gBridge (https://github.com/kservices/gBridge; https://about.gbridge.io) basically implements plain Google Assistant/ Alexa to MQTT bridging.
Regarding your questions, there are two points that help to implement these solutions:
Think in terms of devices or endpoints, rather than requests. When you just want to "translate" HTTP to MQTT, you are inducing a lot of issues like you've figured out. You probably want to implement a logic that allows MQTT topics to control/ query your actual deviecs - not ones that respond to HTTP requests. This makes thing a whole lot simpler.
Caching is essential. Allow your bridge to have a local copy of your device's states. When having the properly implemented cache, you won't need for any response. Just use the cached data.
Hi iCoders currently i'm working on an app for live streaming using OpenTok/TokBox iOS SDK.My doubt is how many number of subscribers can subscribe to a stream published by a publisher.I have searched about this in openTok forums but no where found about this.If anyone know about this please share your answer.
Thanks,
ravi.
I believe there is no limitation in how many subscribers you have on a published stream. The only thing you need to consider is using relayed or routed sessions, see doc.
If you are using relayed sessions you are limited with the bandwidth on the device. And you will open a stream to each subscriber. I guess that is not something you would like.
If you switch to routed sessions you will only have one stream to the servers of TokBox and this server replicates to all subscribers and this server is not limited to the amount of subscribers.