Alert is not triggered when rule is set to “Equals zero” for Remote Monitoring solution.

Repro steps:

1. Create a Remote Monitoring solution.




2. Create a alert rule for Engines Device group that is set when the fuel level is zero for 1 minute. Please see ruledetails.png.




3. Select engine-01.0 and run emptytank method




4. Check the fuellevel is set to zero to make sure emptytank method succeeded. Please see devicedetails.png




5. This alert is expected to trigger since fuellevel is set to zero but no alerts are triggered after 1 minute.

I am getting the error "login.microsoftonline.com refused to connect" when trying to connect to https://www.azureiotsolutions.com/Accelerators#sdssolutions/new/predictive-maintenance

I use Edge Dev and my personal MSC account to connect. Please see the attached pic.

Thanks.

I'm unable to sign in to my demo Connected Factory SA instance as it does not think I have the required Admin rights

Steps to reproduce:
1.Simulations
2.New simulation
3.Add the faulty connection string for your IoT Hub
4.Click "Start simulation"
5.Try to fix connection string
6."Start simulation" button will never activate

Only way to workaround is to create new simulation.

Dashboard and Device Explorer continue to show indications of 'Error: Unexpected token K in JSON at position 0'.

No data loaded by Packages, Deployments and Maintenance

Please correct these issues, as they significantly diminish the applicability of this solution accelerator...

It's not possible to upload second javascript file, even basing on Microsoft tutorial: "Create an advanced device model". "Browse" button stops to work after uploading first file.

Is anybody testing this product ? There is a really many problems in most basic operations.

Page = https://azure.microsoft.com/en-us/features/iot-accelerators/ Provision the service for Azure IoT for connected factory succeeds, but Provision the service for 'Azure IoT for device simulation' fails. I have tried two different subscriptions with the same bad results (spinning icon at https://www.azureiotsolutions.com/Accelerators#sdssolutions/new/device-simulation).

For me, it will work for some days and then at some point, I can no longer start a simulation and I have to delete the entire solution accelerator and create a new one and then the simulation will start in seconds. I've been through this 3 or 4 times now.

Either the solution is broken or the documentation is wrong. Creating an advance device will only send the initial values as telemetry.

Either the solution is broken or the documentation is wrong. Creating an advance device will only send the initial values as telemetry.

We used the accelerator to generate IOT data and then can view the data in TSI. However when we try to view the data view PowerBI , no 'raw' data can be viewed in PowerBI when using the TSI connector to PowerBI approach.

Here is a link to the details on how I am trying to view TSI data in PowerBI:

https://docs.microsoft.com/en-us/azure/time-series-insights/how-to-connect-power-bi

As per the documentation, admins can add a new OPC UA URI in the Browse tab. https://docs.microsoft.com/en-us/azure/iot-accelerators/iot-accelerators-connected-factory-customize#data-sources

However In my solution, I dont see that option. I have installed the Industrial IoT Gateway on my Iot Edge Server and is listed under the Connected factory Iot Hub edge servers with opctwin and opcpublisher modules in it.

When I try to open the ML workspace of the prediction maintenance accelerator, it give me this error messgae!!

I am in need to deploy to see the functionalities and services needed for this type of project and also in need to know if the backend is on c#

not working for me. I get "Please correct input errors below." but no errors were shown

1. When uploading a custom device model, the uploader would not allow my behavior script to be named anything except "drone-state.js" which is the file name from the tutorial (https://docs.microsoft.com/en-us/azure/iot-accelerators/iot-accelerators-device-simulation-advanced-device#behavior-script-files).




2. If the IoTHub connection string doesn't work when creating a simulation, there's no way forward except canceling and starting over.




3. The inputs relating to messages per second really need to be labeled.

Telemetry chart does not support local date format. Show always MM/DD/YYYY format. The portal localisation format of date setting does not apply for this control.

For Azure Remote Monitoring, Replicate from Contosa. The logo and name cannot change

Very pathetic performance.Connected factory template does not work.