Routing on IOT Edge
Hi, I have a problem that I have been dealing with for quite some time. Trying to put a "where" in a routing for AZIOT edge hub. have tested this which works. FROM /messages/* WHERE $connectionModuleId = 'noded' INTO BrokeredEndpoint("/modules/testjob/inputs/edgehub") . But what I want to do is a "where" against appProperties. I have tried every conceivable "syntax" for this?? Inserts an example message. { "message": { "systemProperties": { "contentType": "application/json", "contentEncoding": "UTF-8", "iothub-message-source": "deviceMessages", "iothub-enqueuedtime": "2017-05-08T18:55:31.8514657Z" }, "appProperties": { "processingPath": "{cold | warm | hot}", "verbose": "{true, false}", "severity": 1-5, "testDevice": "{true | false}" }, "body": "{\"Weather\":{\"Temperature\":50}}" } } Thanks for any help I can get. Can't find any documentation for this?
IoT Edge certificate renewal
Hi all, We are currently implementing an IoT Edge on a lot of Devices which will be at remote locations. We have cleared out that IoT Edge can use up to 3 certificates: Certificate to perform the TLS communication with IoT Hub Device certificates for internal use with modules, leave devices, etc. DPS (Optional is you use certificates) We are currently looking for a solution for point 1 and 2. 1. We understand that this can be solved with keeping IoT Edge up-to-date, but how do perform this is these devices are Remote and we have a lot of them? I know this will not happen that often that this certificate will expire but still it can, so we want to be prepared. 2. Device certificates should also be renewed from time to time. How can you also orchestrated form IoT Hub? We currently where thinking of building a module, but when the device comes online again after some time and in the main time, the certificate has expired, than the module is not able to talk to IoT Hub. Or do you just install a device certificate a installation which will have an expiration date longer then the expected device lifetime? Thanks for the help and insights on this topic. Kr, StevenVision AI Dev Kit solidifies after launch
I started the VisionAIDevekitGetStarted module in the Vision AI Dev Kit. However, the operation does not proceed. If you check the log with docker with the following command, it is fixed in the following place. I want to know how to deal with it. command: docker logs AIVisionDevKitGetStartedModule result: iotccsdk-INFO-ipcprovider-connect: 263-API: http://172.17.0.1:1080/login data: {'username': 'admin', 'userpwd': 'admin'}
