This repository has been archived by the owner on Dec 12, 2020. It is now read-only.
Releases: Azure/azure-iot-remote-monitoring
Releases · Azure/azure-iot-remote-monitoring
Release Notes v1.5.0
Remote Monitoring Release Notes | Version 1.5.0
Refactoring
- Introduced strongly typed DeviceModel, Command & Parameter types
- Updated all internal repositories, services and controllers to accept and use strongly typed models.
- Updated Simulator.WebJob to use strongly typed models for generating simulated devices.
- Updated EventProcessorHost to use strongly typed models.
- Removed old REST implementation of DocumentDB client in favor of client provided by DocumentDB SDK
- Unified unit test project.
- Expanded unit test coverage for Web, EventProcessorHost and Infrastructure.
- General code cleanup.
Bug Fixes
Remote Monitoring v1.4.1
Remote Monitoring Release Notes | Version 1.4.1
Bug Fixes
- Fixed bug to set default language to English instead of Czech if not detected by browser
- Fixed bug in deployment if there was space in path
- Updated Storage and Iothub RP versions in templates to current version
- Added Tag to storage now that new version supports it
Remote Monitoring v1.4.0
Remote Monitoring Release Notes | Version 1.4.0
Breaking Change
- Azure Storage API has changed in the latest version. This release supports that change and now requires Azure Powershell SDK 1.4.0 or later
Remote Monitoring v1.3.0
Remote Monitoring Release Notes | Version 1.3.0
New Features
- Support Multiple Azure Environments (AzureGermanyCloud and AzureCloud)
- Added additional Regions where you can deploy your solution (Germany Central, Germany Northeast, Japan East, Japan West, Australia East, Australia Southeast)
Remote Monitoring Solution Portal Improvements
- Added Globalization support for selected language in solution portal
- Added Localized string support in solution portal:
- Czech (Čeština)
- German (Deutsch)
- English
- Spanish (Español)
- French (Français)
- Hungarian (Magyar)
- Italian (Italiano)
- Japanese (日本語)
- Dutch (Nederlands)
- Polish (Polski)
- Portugese (Português)
- Russian (ру́сский)
- Swedish (svenska)
- Turkish (Türkçe)
- Chinese simplified (中文(简体))
- Chinese traditional (中文(簡體))
- Added support to specify Bing Map Api key (manually put key in [solutionname].config.user MapApiQueryKey setting) for shared map key, local deployments, or for Germany datacenter which does not have Bing Maps available (see documentation on how-to here)
Refactoring
- Update dependency libraries to latest versions
- Removed Dependency on Microsoft.WindowsAzure.Diagnostics and Microsoft.WindowsAzure.ServiceRuntime, which means we now do not have a hard dependency on Azure SDK
- Moved AAD auth model from WSFederation to OpenIDConnect
Bug Fixes
- Fixed bugs in Powershell for users with multiple accounts and multiple subscriptions
- Fixed bug with AAD Applications created via commandline deployments that were missing permissions for non-AAD admins
Remote Monitoring v1.2.0
Remote Monitoring Release Notes | Version 1.2.0
Breaking Changes
- Upgraded powershell support to 1.0.3
New Features
- Added 3 more regions: West Europe, West US, Southeast Asia
- Added version check for powershell compatibility
- Added ability to select option number instead of typing guids
Bug Fixes/Minor Changes
- Added Version.txt to track solution version
- Set default web app to premium
- Back ported changes from Predictive Maintenance deployment and standardized between them
- Fixed small spelling mistakes
Remote Monitoring v1.1.0
Remote Monitoring Release Notes | Version 1.1.0
New Features
• Cellular Connectivity Registration
○ API Registration
○ Device to SIM Association for new or existing devices
○ SIM details for devices with a SIM association
○ Ability to remove a device to SIM association
Remote Monitoring Solution Portal Improvements
• Added Advanced Tab
• Added views for Cellular Connectivity: API Registration and Device Association
• Added UI elements to attach SIM ICCID when creating a new device
• Added Cellular Connectivity view for devices with SIM association in Device Details pane
• Added link to remove a device to SIM association
Refactoring
• DocDB REST util (merged #79)
• Use LastOutputEventTime from Azure Stream Analytics instead of a manually set custom time
Bug Fixes
• Fixed bug where ExecuteLogicAppAsync was unreachable (Fixes Issue #82)
• Fixed bug to now take latest version of any imported library (Fixes Issue #95)
• Azure services are now tagged with IoTSuiteType
Remote Monitoring v1.0.0
Remote Monitoring Release Notes | Version 1.0.0
Deployment improvements
- Provision all local and cloud deployment resources in their own resource group
- Added support for uploading zip packages to storage for deployment and generated connection string for zip packages with symmetric key
- Unique name generation based on suite name for resources
- Azure ARM-based template deployments for local and cloud for all resources
- Auto-provisioning of Azure Active Directory application and assignment of user to admin role
- Auto-start of stream analytics jobs upon provisioning
- Use IoT Hub instead of Event Hub for direct input to Azure Stream Analytics jobs
- Respect Sku's of resources for existing deployments
Runtime improvements
- Separate web jobs from the web site for independent scalability
- Update simulators to run in single instance in web job and event host processors run in n instances
Remote Monitoring Solution Portal improvements
- Added ability to delete a pending device
- Added ability to delete a rule
- Added visual status indications to rules grid
- Added Apple Mac-specific copy text message
- Fix a bug where mixed case event hub name would break actions flow
- Refactored query for Stream Analytics rules job to fix some bugs and simplify logic
- Color-code devices on dashboard map based on how recently they have had an alert
- Improve display of DeviceID on dashboard map when clicked
- Clicking a device on the dashboard map displays the telemetry data and the summary data for that device
- Selecting a device on the dashboard highlights alarm rows for that device in the alarm history
- Globalization bug fixes and improvements, including adding a pseudo-localized tt resource for testing
- Add FxCop rules for Globalization and minimum rules to help prevent globalization regressions
- Font size consistency improvements
- Hide “Previous” and “Next” paging buttons on device grid and rules grid when only one page of data exists
- Stream Analytics reference data reliability improvements
- Fixed some minor visual and labelling issues
- Add logic to try to prevent race conditions and unexpected behavior during one-time data initialization in the WebJob
- Fixed a minor bug where concurrent edits on rules were not handled well
- Improved error handling and reporting in REST API
- Fix possible issue where caching around device enable/disable may have caused issues
- Fix a bug with multiple collections in the same DocumentDB
- Clarify local and UTC dates and times in user interface
- Clarify lack of localization and local timezone support for device properties
- Fix a bug on the dashboard where the static map image broke the alert history grid
- Updated code so that OAuth could be more easily used with the REST API
- Fix a bug where datetimeoffset command parameters were not formatted correctly
- Fix a bug where the simulator would return success for unknown commands
- Fix a bug where upgrading a solution would cause the alerts on the dashboard to fail due to a data format change in the blob storage
- Fix a bug where the map always included the Seattle area, regardless of device location
- Fix a bug with multiple collections in the same DocumentDB
- Fix a bug that allowed resending commands to disabled devices and devices that no longer support the command
- Fix some visual issues with the navigation bar images, especially in Edge browser
- Fix a bug where the DocumentDB would sometimes return an HTTP 401 error, especially during debugging, due to timestamp mismatch issues
- Fix a bug where some or all simulated devices would sometimes send identical telemetry data (due to issues around the random number generator’s seed)
- General code cleanup
- Refactor the styles using BEM (Block Element Modifier) convention
Known Issues
- IoTHub skus are not currently respected (always switches to default of template). This will be fixed when we switch to Azure Powershell 1.0.