I tried to receive desired properties update notifications by subscribing topic "$iothub/twin/PATCH/properties/#" (reference) and also by sdk (refernece). Both went okay and I did get notifications when I changed the desired properties by back-end services, but with all the desired properties in response. Is there a topic or a function in sdk to just get the properties that where changed? Or to know witch properties were changed without looking through all the desired properties?
Appreciate your help!
You should use a PATCH request to update a desired property in your back-end service. The following screen snippets show an example of the updating only one desired property such as color. For quick demonstration purpose, the Azure IoT Hub Tester is used:
Creating two desired properties (color, abc):
device8 received a changes notification (version=2):
In this step, we need to update only one desired property (color):
device8 received a changes notification (version=3) such as the preperty color:
As you can see in the above pictures, the device8 subscribed on the topic like you mentioned it. You didn't describe how your backend service updating your desired properties.
Note, that the above example using the REST PATCH call for updating a desired properties.
Related
I'm using the mattermost-plugin-gitlab. I know i can subscribe to labeled issues.
But is it possible to get only messages for custom events like issue creation?
E.g. i want to subscribe to messages if a new issue is created (and maybe closed) with a custom label like Bug.
But i don't want to get all other issue events like state changes from ToDo in Doing etc.
/gitlab subscriptions add someone/repox issues, label:some
or
/gitlab help
What I'm currently trying to get my head around is the ability to integrate the modelId from an Azure Digital Twin instance within Time Series Insights. I understand that Time Series Insights (Gen2) accepts the datatype of a string, however when I try to initiate that state, it doesn't appear within TSI when a connection is successfully established between Azure Digital Twin and Time Series Insights.
Streaming logs showing the modelId being recognised but not parsed into TSI:
Is there potentially a way to define this modelId so that it can be viewed as an instance or even as a hierarchy within Time Series Insights, so that I don't manually have to this step?
Many thanks,
Matas
Device id / some meaningful attributes from event source to be mapped as timeseriesid. TSI will automatically map with the event source once we set the attribute. We can set multiple attributes. This should be done during the creation of TSI. Once created, you cannot change the timeseriesid.
Add modelId as timeseriesid. It should solve your issue.
I am assuming you are trying to insert modelID as one of the instance field of an instance in TSI through its ingestion service.
If that is the case, unfortunately we cant insert instance fields through ingestor service. Instead you can call the API to insert instance field and its values. The API could be called from your Translator function or using upload JSON option in TSI model page.
TSI has its own syntax please refer to the attachment for details
Screenshot showing syntax for inserting instance field with its value:
Please refer to the following documentation for information about TSI model, Patch Syntax and API details!
https://learn.microsoft.com/en-us/azure/time-series-insights/concepts-model-overview
https://learn.microsoft.com/en-us/rest/api/time-series-insights/dataaccessgen2/timeseriesinstances/executebatch#instancesbatchput
Please let me know if I could be of further help!
I was asked to create a custom event in Policy Center. A GuideWire employee said that I should see the GuideWire docs. I searched the documents that I had and all I could find was how to add a new event for something in Billing Center. It seemed to suggest that I should add the new event to the type list. There doesn't seem to be a type list for the other types of events that I am monitoring, so that doesn't seem to be an option.
This should be as simple as calling
.addEvent("CustomeEvent")
on any entity object.
What you probably should read is the Messaging section of the Integration Guide in the documentation. This new event - whatever you call it - has to be mentioned in Messaging part of the configuration on the particular destination and then appropriately filtered/handled in Event Fired Rules.
I have been looking at the sample code provided by Google for casting videos and am not able to figure out from where is the metadata being gotten from for the Notification. Below are the liks I am looking at.
Links: https://github.com/googlecast/CastVideos-android/blob/master/src/com/google/sample/cast/refplayer/CastOptionsProvider.java
https://github.com/googlecast/CastVideos-android/blob/master/AndroidManifest.xml
I did some research and my assumption is that it gets the metadata from the TargetActivityClass which is ExpandedControlsActivity but I am not able to get it even there. Any help is appreciated.
When your app creates a MediaInfo to load on the receiver, you provide all the required metadata (title, image, etc) and that is how the framework handles the rest for you. Note that the framework also listens to the messages and status updates from the receiver so it stays up to date with what is playing on the receiver, hence can update the metadata for the notification, if necessary.
I have an Azure Logic App that sends a message to a Topic using the Azure Service Bus Connector. I even use the Properties field and the values are indeed propagated together with the message.
But for some reason filtering doesn't work on these properties, though the filter works when sending a message with another tool (like Service Bus Explorer).
SB Connector, that sets Properties:
Message send to Topic in SB and visible in Subscription without Filter. (Rule 1=1)
But this message is never available in a Subscription with Filter.
Though messages sent with other "Publishers" (e.g. Test with SB Explorer) do appear in this subscription if they match the filter criteria.
Any ideas what's going wrong?
My guess right now (and I'll verify this later today) is that the current Service Bus Connector is casting all properties as "strings" and not detecting when it is an Int32, so the rule isn't successfully working. Can you try either modifying your rule to detect the string "1" or modifying the property to send a string and see if that works? If so we should be able to add the work to deal with integers better when in properties. Let me know
EDIT: After looking into it, this appears to be the case. If you can verify treating it as a string works I'll know for sure where we have the gap and can work on prioritizing the fix.