Project:Sandbox

CLM 2.0 - January 2019 0 688 2570 2018-09-16T08:51:11Z Vanya 2 started writign CLM 2.0 release notes wikitext text/x-wiki == HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provifioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

Technician mode


[null ·        C&amp;M + E -] Removed temperature value and temperature chart from hub’s device details screen. Also, temperature anomalies will not be registered as events in the cloud, the hub will blink in red in case of high or low temperature for itself. Removed temperature information from Monitoring Station on Dashboard.

[null ·        C&amp;M + E -] Changes high temperature threshold from 50°C to 55[null °C]. Now, the hub will blink in red when a device’s temperature in the system reaches 55°C. Mobile app will notify the user via push notification, SMS or email in case the same threshold is reached.

[null ·        C&amp;M -] Cloud support for 3&lt;sup&gt;rd&lt;/sup&gt; party Smoke and Magnetic sensors.

·        C&amp;M - Water shutoff is automatically registered as a “Water” shutoff. There is no pop up when adding a device with serial number starting with 0006, 0007, asking the user to choose between “Gas” or “Water”.

·        E - All devices will blink in red (same as for leak event) instead of orange, in case of an alert, such as:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

·        E – Shutoffs will stay in their position after OTA. After the update finished, a shutoff will not perform BIT and stay in OPEN position.

·        C&amp;M – suggest language automatically when a user installs Customer Application for the first time – after installation, Triple+ app detects user’s OS language and suggests in what language, the application will be. Options:

o  English

o  Russian

o  Hebrew

o  Other – application will detect “English” and will suggest it as a language for the application

[null ·        C&amp;M + E -] Support for up to 128 devices in a system with HUB 2.0 [null – not tested]

·        C&amp;M - Email notifications have new text– not completely tested (tested only English versions):

o  Old - Dear Username,

your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

o   New - Dear Username,

Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.

·        MS – Added information for device’s schedule – if it is disabled, enabled and what are the tasks set by the customer.

·        MS – Event log will not load before the customer clicks on filter’s “Apply” button.

·        MS – Added “Device Type” column in Monitoring Station’s Event Log.

·        MS – Added functionality for exporting parts of the event log. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release

·        C&amp;M – removed “Notification Log” in Customer application. Replaced with “Event Log”. The new log shows the user the last 50 events which has occurred in all account’s systems. Makes it easier for a customer to keep track of what is happening with all systems.

[null ·        C&amp;M –] customer receives an email for a successfully completed installation done via Customer Application

·        C&amp;M – cloud sends a mail to a predefined email address for a completed system installation done either with Installer app or with Customer app. Email address is configured from Portal’s Configuration menu. “Installation type” is either “Installation” from Installer App and “Kit Installation” from Customer App. Example email:

Successful System Installation

[null ·        C&amp;M –] added field in Customer App for entering phone number.

·        C&amp;M – redesigned “Login” and “Create New Account” screens for Customer and Installer applications

[null ·        C&amp;M –] SMS notifications

·        C&amp;M + E – update hub before installation. After scanning a QR code for starting an installation, an update will start if there is an available newer version activated in the cloud. The process takes approximately 4 minutes. After the update is completed, the installation process continues. qq9v115pcyhp5imunupb1znxcuv6ikt 2577 2570      2018-09-16T09:37:57Z Vanya 2 still in progress. just savn wikitext text/x-wiki == HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provifioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



[null ·        C&amp;M + E -] Removed temperature value and temperature chart from hub’s device details screen. Also, temperature anomalies will not be registered as events in the cloud, the hub will blink in red in case of high or low temperature for itself. Removed temperature information from Monitoring Station on Dashboard.

[null ·        C&amp;M + E -] Changes high temperature threshold from 50°C to 55[null °C]. Now, the hub will blink in red when a device’s temperature in the system reaches 55°C. Mobile app will notify the user via push notification, SMS or email in case the same threshold is reached.

[null ·        C&amp;M -] Cloud support for 3&lt;sup&gt;rd&lt;/sup&gt; party Smoke and Magnetic sensors.

·        C&amp;M - Water shutoff is automatically registered as a “Water” shutoff. There is no pop up when adding a device with serial number starting with 0006, 0007, asking the user to choose between “Gas” or “Water”.

·        E - All devices will blink in red (same as for leak event) instead of orange, in case of an alert, such as:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

·        E – Shutoffs will stay in their position after OTA. After the update finished, a shutoff will not perform BIT and stay in OPEN position.

·        C&amp;M – suggest language automatically when a user installs Customer Application for the first time – after installation, Triple+ app detects user’s OS language and suggests in what language, the application will be. Options:

o  English

o  Russian

o  Hebrew

o  Other – application will detect “English” and will suggest it as a language for the application

[null ·        C&amp;M + E -] Support for up to 128 devices in a system with HUB 2.0 [null – not tested]

·        C&amp;M - Email notifications have new text– not completely tested (tested only English versions):

o  Old - Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

o   New - Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.

·        MS – Added information for device’s schedule – if it is disabled, enabled and what are the tasks set by the customer.

·        MS – Event log will not load before the customer clicks on filter’s “Apply” button.

·        MS – Added “Device Type” column in Monitoring Station’s Event Log.

·        MS – Added functionality for exporting parts of the event log. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release

·        C&amp;M – removed “Notification Log” in Customer application. Replaced with “Event Log”. The new log shows the user the last 50 events which has occurred in all account’s systems. Makes it easier for a customer to keep track of what is happening with all systems.

[null ·        C&amp;M –] customer receives an email for a successfully completed installation done via Customer Application

·        C&amp;M – cloud sends a mail to a predefined email address for a completed system installation done either with Installer app or with Customer app. Email address is configured from Portal’s Configuration menu. “Installation type” is either “Installation” from Installer App and “Kit Installation” from Customer App. Example email:

Successful System Installation

[null ·        C&amp;M –] added field in Customer App for entering phone number.

·        C&amp;M – redesigned “Login” and “Create New Account” screens for Customer and Installer applications

[null ·        C&amp;M –] SMS notifications

·        C&amp;M + E – update hub before installation. After scanning a QR code for starting an installation, an update will start if there is an available newer version activated in the cloud. The process takes approximately 4 minutes. After the update is completed, the installation process continues. ht98b5uxondypik0dpwh22kbfu1fuv2 2589 2577      2018-09-16T10:19:37Z Vanya 2</id> not completed. just savin' wikitext text/x-wiki <text xml:space="preserve" bytes="7631">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provifioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: Home and Pool
Customer app has backword compatability. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version. kzb1mzp3sonbdpclafv5fviefgsvbvu 2592</id> 2589      2018-09-16T10:27:22Z Vanya 2</id> finished, I hope wikitext text/x-wiki <text xml:space="preserve" bytes="8610">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provifioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: Home and Pool
Customer app has backword compatability. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. heicgyr61hi6ux6h4ecxzb3hxphya8a 2593</id> 2592      2018-09-16T10:27:47Z Vanya 2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="8610">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provifioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: Home and Pool
Customer app has backword compatability. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. f19m3ox1nvhv2pzhtmn2geir77gzp36 2594</id> 2593      2018-09-17T14:56:08Z Vanya 2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="9154">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provifioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: Home and Pool
Customer app has backword compatability. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exaclty, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. 0qhq1z6cyq4lyde8yv09o9urc6ztd33 2817</id> 2594      2018-12-21T08:59:47Z Vanya 2</id> sniffer mode is edited wikitext text/x-wiki <text xml:space="preserve" bytes="10333">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network.



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: Home and Pool
Customer app has backword compatability. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exaclty, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. mikjxhx87jlbtorsdxsa6mfj39hj0ym 2821</id> 2817      2018-12-21T09:42:55Z Vanya 2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="11603">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: Home and Pool
Customer app has backword compatability. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exaclty, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. rz17cl4cl64fcrat8d7nwg8ehh61g1i 2822</id> 2821      2018-12-21T09:43:30Z Vanya 2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="11668">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.



7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: Home and Pool
Customer app has backword compatability. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exaclty, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. tuhx1i6ln0juagn8jnvpiz85gsssb7a 2823</id> 2822      2018-12-21T09:47:48Z Vanya 2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="12104">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: Home and Pool
Customer app has backword compatability. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exaclty, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. flmvcnu4anzt90j66ekg446ne2kvy8r 2825</id> 2823      2018-12-21T10:10:37Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="12611">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: House with no garden
Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exaclty, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. 73jufmzlf5wb961uwbss5jrqzisdpm4 <id>2826</id> 2825      2018-12-21T10:11:16Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="12649">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: House with no garden
Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exaclty, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. cm6japxnudp5xb07yxlrt5x7y1ru63t <id>2834</id> 2826      2018-12-21T10:17:19Z Vanya <id>2</id> /* Residence Type: House with pool &amp; large garden */ wikitext text/x-wiki <text xml:space="preserve" bytes="12922">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximatly 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exaclty, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. jzf01e0dcar6b12on7qwtzpo4j1ov0f <id>2835</id> 2834      2018-12-21T10:23:29Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="12977">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. ojhhlmgja3gx9d95u4t3547tb7d65jg <id>2836</id> 2835      2018-12-21T10:25:05Z Vanya <id>2</id> /* Residence Type: Flat */ wikitext text/x-wiki <text xml:space="preserve" bytes="12987">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. a1a8fafj52dtdryb7uu5cbgn2sdwneq <id>2837</id> 2836      2018-12-21T10:25:19Z Vanya <id>2</id> /* Residence Type: House with pool &amp; large garden */ wikitext text/x-wiki <text xml:space="preserve" bytes="12989">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. 7czx0ow58dh9oqmftravjyjlg6b9sz5 <id>2840</id> 2837      2018-12-21T10:28:26Z Vanya <id>2</id> /* Residence Type: House with garden */ wikitext text/x-wiki <text xml:space="preserve" bytes="13103">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 20 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. bgf6uxfvt28afmz8b1whkwvj7nia3d6 <id>2843</id> 2840      2018-12-21T10:31:08Z Vanya <id>2</id> /* Residence Type: House with no garden */ wikitext text/x-wiki <text xml:space="preserve" bytes="13234">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. nzdd8dxoaol4b9d7ko0b9daerbwe05v <id>2844</id> 2843      2018-12-21T10:31:32Z Vanya <id>2</id> /* Residence Type: Flat */ wikitext text/x-wiki <text xml:space="preserve" bytes="13234">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. 5fouqhm7ngvnwua9yyoga4lok85l4ou <id>2845</id> 2844      2018-12-21T10:33:30Z Vanya <id>2</id> /* Default - without setting anything from the app. With these settings, the devices come out from production: */ wikitext text/x-wiki <text xml:space="preserve" bytes="13309">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exaclty how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name suach as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events. 0p4ys6afdztelj7712tq5h3xs5dcn2t <id>2846</id> 2845      2018-12-21T12:52:23Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="13382">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s. jouco5xf1yklwfkmbvckhcbqmzozhra <id>2847</id> 2846      2018-12-21T12:54:41Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="13438">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider. 1jv7jwniihbx9s7t5vr7707psuuk6bc <id>2848</id> 2847      2018-12-21T13:01:38Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="14015">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Existing issues
3o2nx3hkhzpafj98yjburdlrfy18mh9 <id>2849</id> 2848      2018-12-21T13:06:45Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="14379">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment.

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Existing issues
qrkwvsycwxn7wvf6kv0ptdqmyl9b37v <id>2850</id> 2849      2018-12-21T13:07:59Z Vanya <id>2</id> /* Support for 128 devices */ wikitext text/x-wiki <text xml:space="preserve" bytes="14528">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Existing issues
nyr98ih765kbrxzpvdjpe3yp00sl954 <id>2851</id> 2850      2018-12-21T13:08:46Z Vanya <id>2</id> /* Custom flow detection settings */ wikitext text/x-wiki <text xml:space="preserve" bytes="14528">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Default:
Without setting anything from the app. With these settings, the devices come out from production:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Existing issues
khbds2gwzx4n8t8app3xf4flbha6efk <id>2852</id> 2851      2018-12-21T13:16:26Z Vanya <id>2</id> Vanya moved page CLM 2.0 - September 2018 to CLM 2.0 - January 2019 without leaving a redirect wikitext text/x-wiki <text xml:space="preserve" bytes="14528">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



CC1310 end units
I don't know what to write here I just want to remember that with CLM 2.0 we got these devices. CC1310 devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Default:
Without setting anything from the app. With these settings, the devices come out from production:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Existing issues
khbds2gwzx4n8t8app3xf4flbha6efk <id>2856</id> 2852      2019-01-03T09:41:32Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="14599">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



Zigbee
Hub 2.0's hardware supports Zigbee. Firmware is not done, but hardware is ready.

CC1310 end units
With CLM 2.0, new hardware for the flood detector is user, baed on CC1310. The devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Default:
Without setting anything from the app. With these settings, the devices come out from production:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Existing issues
l1pffhachn6zwa8wlt3fgf7qvzegb74 <id>2858</id> 2856      2019-01-04T11:50:35Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="14647">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:
 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



Zigbee
Hub 2.0's hardware supports Zigbee. Firmware is not done, but hardware is ready.

CC1310 end units
With CLM 2.0, new hardware for the flood detector is user, baed on CC1310. The devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Default:
Without setting anything from the app. With these settings, the devices come out from production:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Existing issues

 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Redmine export
gug13p8ju2kanj9uq9e0v3qj4566moa <id>2863</id> 2858      2019-01-08T09:38:32Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="15197">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



Zigbee
Hub 2.0's hardware supports Zigbee. Firmware is not done, but hardware is ready.

CC1310 end units
With CLM 2.0, new hardware for the flood detector is user, baed on CC1310. The devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Default:
Without setting anything from the app. With these settings, the devices come out from production:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Show Flow Configuration Settings in MS
MS shows current information about flow sensor's flow detection settings. Work on the same way as the &quot;Schedule&quot; - it can only be previewed. Where there is a flow sensor, an additional button is shown on its row. Clicking the button, opens a pop up. The pop up contains the name of the residence type and the settings:







Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Existing issues

 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Redmine export
mv0bk9tcddrxysiavony8srp7z382kq <id>2864</id> 2863      2019-01-08T14:01:48Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="15438">== HUB 2.0 == A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



Zigbee
Hub 2.0's hardware supports Zigbee. Firmware is not done, but hardware is ready.

CC1310 end units
With CLM 2.0, new hardware for the flood detector is user, baed on CC1310. The devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Default:
Without setting anything from the app. With these settings, the devices come out from production:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Show Flow Configuration Settings in MS
MS shows current information about flow sensor's flow detection settings. Work on the same way as the &quot;Schedule&quot; - it can only be previewed. Where there is a flow sensor, an additional button is shown on its row. Clicking the button, opens a pop up. The pop up contains the name of the residence type and the settings:







Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Terms and Conditions
- Changed text for Terms and Conditions in Customer and Installer apps

- Added sections in &quot;About&quot; menu in MS - for &quot;Terms of Use and Privacy Policy&quot;

- Added sections in &quot;About&quot; menu in MS - for &quot;User Manual&quot;

Existing issues

 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Redmine export
26boqg2lgv8282rxbpkyn0mfywwwx7b <id>2869</id> 2864      2019-01-10T14:07:50Z Vanya <id>2</id> wikitext text/x-wiki <text xml:space="preserve" bytes="16671">== Release Date - 09.01.2019 ==

HUB 2.0
A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



Zigbee
Hub 2.0's hardware supports Zigbee. Firmware is not done, but hardware is ready.

CC1310 end units
With CLM 2.0, new hardware for the flood detector is user, baed on CC1310. The devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Default:
Without setting anything from the app. With these settings, the devices come out from production:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Show Flow Configuration Settings in MS
MS shows current information about flow sensor's flow detection settings. Work on the same way as the &quot;Schedule&quot; - it can only be previewed. Where there is a flow sensor, an additional button is shown on its row. Clicking the button, opens a pop up. The pop up contains the name of the residence type and the settings:







&quot;About&quot; menu
Added two new sections to the existing &quot;About&quot; menu - &quot;Terms of Use and Privacy Policy&quot; and &quot;User Manual&quot;. Below are the files:



Note: RDT and Rectorseal have only &quot;Terms of Use and Privacy Policy&quot;. There is no &quot;Support &amp; Troubleshooting&quot; and &quot;User manual&quot; for them.

Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Terms and Conditions
- Changed text for Terms and Conditions in Customer and Installer apps

- Added sections in &quot;About&quot; menu in MS - for &quot;Terms of Use and Privacy Policy&quot;

- Added sections in &quot;About&quot; menu in MS - for &quot;User Manual&quot;

Existing issues

 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Redmine export
3nbjdo374plfgmstre4uzvdqfbby75m <id>2870</id> 2869      2019-01-10T14:08:19Z Vanya <id>2</id> /* &quot;About&quot; menu */ wikitext text/x-wiki <text xml:space="preserve" bytes="16665">== Release Date - 09.01.2019 ==

HUB 2.0
A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



Zigbee
Hub 2.0's hardware supports Zigbee. Firmware is not done, but hardware is ready.

CC1310 end units
With CLM 2.0, new hardware for the flood detector is user, baed on CC1310. The devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Default:
Without setting anything from the app. With these settings, the devices come out from production:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Show Flow Configuration Settings in MS
MS shows current information about flow sensor's flow detection settings. Work on the same way as the &quot;Schedule&quot; - it can only be previewed. Where there is a flow sensor, an additional button is shown on its row. Clicking the button, opens a pop up. The pop up contains the name of the residence type and the settings:







&quot;About&quot; menu
Added two new sections to the existing &quot;About&quot; menu - &quot;Terms of Use and Privacy Policy&quot; and &quot;User Manual&quot;. The files are:



Note: RDT and Rectorseal have only &quot;Terms of Use and Privacy Policy&quot;. There is no &quot;Support &amp; Troubleshooting&quot; and &quot;User manual&quot; for them.

Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Terms and Conditions
- Changed text for Terms and Conditions in Customer and Installer apps

- Added sections in &quot;About&quot; menu in MS - for &quot;Terms of Use and Privacy Policy&quot;

- Added sections in &quot;About&quot; menu in MS - for &quot;User Manual&quot;

Existing issues

 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Redmine export
ehnqr6hi0n8x2b5p8681xtrwixyth7b <id>2923</id> 2870      2019-02-26T14:39:19Z Vanya <id>2</id> /* Release Notes */ wikitext text/x-wiki <text xml:space="preserve" bytes="16973">== Release Date - 09.01.2019 ==

HUB 2.0
A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



Zigbee
Hub 2.0's hardware supports Zigbee. Firmware is not done, but hardware is ready.

CC1310 end units
With CLM 2.0, new hardware for the flood detector is user, baed on CC1310. The devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Default:
Without setting anything from the app. With these settings, the devices come out from production:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Show Flow Configuration Settings in MS
MS shows current information about flow sensor's flow detection settings. Work on the same way as the &quot;Schedule&quot; - it can only be previewed. Where there is a flow sensor, an additional button is shown on its row. Clicking the button, opens a pop up. The pop up contains the name of the residence type and the settings:







&quot;About&quot; menu
Added two new sections to the existing &quot;About&quot; menu - &quot;Terms of Use and Privacy Policy&quot; and &quot;User Manual&quot;. The files are:



Note: RDT and Rectorseal have only &quot;Terms of Use and Privacy Policy&quot;. There is no &quot;Support &amp; Troubleshooting&quot; and &quot;User manual&quot; for them.

Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Terms and Conditions
- Changed text for Terms and Conditions in Customer and Installer apps

- Added sections in &quot;About&quot; menu in MS - for &quot;Terms of Use and Privacy Policy&quot;

- Added sections in &quot;About&quot; menu in MS - for &quot;User Manual&quot;

Existing issues

 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Redmine export
t60tgnwxgkk36jdcx3j8jclr2vu1rwd <id>3126</id> 2923      2019-06-18T07:29:54Z Vanya <id>2</id> /* Release Notes */ wikitext text/x-wiki <text xml:space="preserve" bytes="17169">== Release Date - 09.01.2019 ==

HUB 2.0
A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



Zigbee
Hub 2.0's hardware supports Zigbee. Firmware is not done, but hardware is ready.

CC1310 end units
With CLM 2.0, new hardware for the flood detector is user, baed on CC1310. The devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Default:
Without setting anything from the app. With these settings, the devices come out from production:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Show Flow Configuration Settings in MS
MS shows current information about flow sensor's flow detection settings. Work on the same way as the &quot;Schedule&quot; - it can only be previewed. Where there is a flow sensor, an additional button is shown on its row. Clicking the button, opens a pop up. The pop up contains the name of the residence type and the settings:







&quot;About&quot; menu
Added two new sections to the existing &quot;About&quot; menu - &quot;Terms of Use and Privacy Policy&quot; and &quot;User Manual&quot;. The files are:



Note: RDT and Rectorseal have only &quot;Terms of Use and Privacy Policy&quot;. There is no &quot;Support &amp; Troubleshooting&quot; and &quot;User manual&quot; for them.

Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Terms and Conditions
- Changed text for Terms and Conditions in Customer and Installer apps

- Added sections in &quot;About&quot; menu in MS - for &quot;Terms of Use and Privacy Policy&quot;

- Added sections in &quot;About&quot; menu in MS - for &quot;User Manual&quot;

Existing issues

 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Redmine export
p3vcjlujqdscyfyny9o9tbjwa7n0nhb <id>3127</id> 3126      2019-06-18T07:31:13Z Vanya <id>2</id> /* Release Notes */ wikitext text/x-wiki <text xml:space="preserve" bytes="17362">== Release Date - 09.01.2019 ==

HUB 2.0
A new Triple+ hub with a Marvell processor. The device works on Wi-Fi only using two provisioning methods known as &quot;Easy mode&quot; (Sniffer mode) and &quot;Technician mode&quot; (Access point mode). Below are shown screenshots from Triple+ Customer application for both methods:

Easy mode
After starting the installation, the application gives you instructions on how to continue. The user can also watch HUB's LED while making the provisioning. The steps are the same as for during installation and Wi-Fi Configuration (after initial installation). The steps are the following:
 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. The next screen shows a field in which is written the Wi-Fi network to which the mobile phone is connected to. If another network is desired, the user should connect the mobile phone to it. The application will automatically detect the change and show the new network. After clicking &quot;Connect&quot; button, the provisioning process starts. HUB's LED will start blinking blue once it starts getting information for the Wi-Fi network. If the HUB successfully receives the needed information and connects successfully to the Wi-Fi network, HUB's LED will be steady green for 3 seconds. If the process wasn't successfull



4. Once the provisioning process finishes successfully, the user will see the screen below and the installation will continue.



Technician mode

 * 1) The first screen instructs you to restart the HUB, so it can enter provisioning process. While waiting to receive data for the Wi-Fi network, the LED of the HUB is steady blue.

2. The second screen shows that the mobile phone should be connected to the same Wi-Fi network that the HUB will be provisioned with. HUB's LED is still steady blue.



3. Press &quot;Technician Mode&quot; button



4. At first, the application is checking if all needed permissions are given, so the mobile app can proceed with the provisioning.



5. The app shows you a pop up instruction to connect to a Wi-Fi network called &quot;Triple+XXXXXX&quot; where XXXXXX represent the last 6 numbers of HUB's serial number.



6. Open the Wi-Fi settings of your mobile phone and connect to the network shown in the instruction pop up.

7. Go back to the mobile app and wait to see a pop up telling you that the app is successfully connected to the HUB



8. Closing the pop up shows you the list with available Wi-Fi networks



9. Choose a network and tap on it. A pop up for entering the password is shown. Enter the password and click &quot;Connect&quot;



10. Wait until the app shows you the screen below. This means that the hub has connected to the chosen network and now, the mobile phone is waiting to connect to a regular Wi-Fi network (the one that the phone was previously connected to).



Zigbee
Hub 2.0's hardware supports Zigbee. Firmware is not done, but hardware is ready.

CC1310 end units
With CLM 2.0, new hardware for the flood detector is user, baed on CC1310. The devices are fully compatible with hub 1.0 and hub 2.0. They can also be used in older version systems.

Custom flow detection settings
This feature allows the customer to create own settings for a flow sensor. The flow value cannot be changed, so all options use the same flow values. Available options:

Default:
Without setting anything from the app. With these settings, the devices come out from production:

Residence Type: House with no garden


Customer app has backward compatibility. If the device is with an older version than CLM 2.0, the application doesn't show this option to the user. Only after the device updates with CLM 2.0 version or newer, the option will appear in &quot;Device details&quot; of the Flow Sensor.

Update hub before installation
With starting an installation of a CLM 2.0 system, the controller will check if there is an available update in the cloud. If there is, the hub will start downloading and update itself. The process takes approximately 4 minutes. If an update is available also for Zigbee and Wi-Fi (for hub 2.), the update process will take more time (for now we don't know how much exactly, since these functionalities are not developed yet). Only after the update finished, installation process will continue. &quot;Updating Hub's firmware&quot; is added as a first step of the installation.



SMS notifications
An SMS notification will be sent to the user in case of an alert. The mechanism for receiving SMS notifications is the same as the emails - only once per event.

By default SMS notifications are disabled. For enabling them, the user must enter also phone number, which can be later edited using the newly added phone number field in &quot;Edit your details&quot;. SMS notifications can be enabled and disabled any time.



Email to a Triple+ employee after completeing an installation
From Portal's Configuration menu can be set an email to which after a successful system installation is sent. The email consists all information regarding the system installation. &quot;Installation Type&quot; points if the installation was done using Installer App (Installation) or with Customer App (Kit installation).



Email for completed installation to the customer
The customer receeves an email for completing a kit installation with his cstomer application. Before CLM 2.0, the customer received an email for a completed installation only if the installation was done with Installer App.

There is a new Triple+ application for internal use only - everyone can change the text of all emails in all languages. For now, the application supports only 001 and 003. Soon, it will work also for 003re and production environments.

Event log in Customer Application
Instead of &quot;Notification Log&quot; in Customer App, now there is an &quot;Event Log&quot;. It shows to the customer the last 50 events for all systems in an accout.



Hub's temperature
Triple+ hub will no longer blink in red if its own temperature is above or below the thresholds. Respecively, cloud will no longer show hub's temperature and its chart inside &quot;Device details&quot; screen. No notifications will be sent for hub's temperature. No records will be kept.

High temperature threshold
Threshold is changed from 50 degrees Celsius to 55 degrees Celsius for a device types, In case a device measures such temperature, it starts blinking red, the hub will start blinking red, the cloud will start sending notifications.

3rd party Magnetic and Smoke sensors
Cloud now recognizes 3rd party Magnetic and Smoke sensors



Red LED intead of orange LED
With CLM 1.3 was implemented a new colour - orange (or funny red) showing anomalies such as:

o  High temperature

o  Low temperature

o  Low battery

With CLM 2.0, this colour is removed from the devices and now it will be red. A device and the hub will blink in red in case of:

o  High temperature

o  Low temperature

o  Low battery

o  Flow alarm – low, medium, high

Automatic language detection
Customer app suggests language for the application after automatically detecting the language of user's OS. The pop up apppears when a user installs Customer Application for the first time,, after agreeing with &quot;Terms and Conditions&quot;.

o  English

o  Russian

o  Hebrew

o  If phone's OS is in a different than the above languages – application will detect “English” and will suggest it as a language for the application



New text for email notifications
Old implementation:

Dear Username,

'&lt;nowiki/&gt;'''your &quot;System name&quot; system has detected an &quot;event&quot;. Please, check your mobile application for more details.

New implementation:

Dear Username,

'&lt;nowiki/&gt;Event “TYPE” - *SystemName*, *DeviceName*, *DeviceLocation* at your system.'

For more info - http://192.168.1.221/redmine/issues/2454



Support for 128 devices
Original requirement - A system installed with hub 2.0 supports up to 128 devices (including the hub). FUNCTIONALITY IS NOT TESTED.

Update - because of problems in the cloud and the hub, the requirement changed to 64 devices. FUNCTIONALITY IS NOT TESTED.

Shutoff will not perform BIT after OTA
Old implementation:

After a shutoff finished an update it performs BIT and stays in OPEN position. The device didn't care if it was closed before the OTA.

New implementation:

All shutoff types will remain in the same position as they were before the update is completed. This feature will work even and an old version device is getting updated with CLM 2.0 version.

Show device's schedule
MS shows current information for a device's schedule - if it is enabled or disabled and what are the tasks that were set by the user:



Show Flow Configuration Settings in MS
MS shows current information about flow sensor's flow detection settings. Work on the same way as the &quot;Schedule&quot; - it can only be previewed. Where there is a flow sensor, an additional button is shown on its row. Clicking the button, opens a pop up. The pop up contains the name of the residence type and the settings:







&quot;About&quot; menu
Added two new sections to the existing &quot;About&quot; menu - &quot;Terms of Use and Privacy Policy&quot; and &quot;User Manual&quot;. The files are:



Note: RDT and Rectorseal have only &quot;Terms of Use and Privacy Policy&quot;. There is no &quot;Support &amp; Troubleshooting&quot; and &quot;User manual&quot; for them.

Event log
MS will show to the user a pop up showing exactly how many records will be exported. After clicking on “Export” button, a pop up will appear showing exactly how many events will be recorded in the export. Clicking “Download export” will start downloading process of a .csv file with name such as EventLog_16_09_2018, 10_44_14.csv, where 16_09_2018 is the date when the export was generated and 10_44_14 is the time when the export was generated. Export works both in English and Russian – functionality will be redesigned with the next release so the export will consist all events.
 * 1) Event log will not load until the user clicks &quot;Apply&quot; button.
 * 2) Added &quot;Device Type&quot; column
 * 3) Added &quot;Export event log&quot; functionality

FTP
FTP's download speed limit is increased from 5KB/s to 100KB/s.

RectorSeal
RectorSeal as a VIP Service Provider.

Write here Portal and MS addresses.

Important note: At the moment of writing this article, RectorSeal's mobile apps are considered not ready, because we still don't have Terms and Conditions.

Load
With current release, the cloud can support up to 10 000 systems.

Terms and Conditions
- Changed text for Terms and Conditions in Customer and Installer apps

- Added sections in &quot;About&quot; menu in MS - for &quot;Terms of Use and Privacy Policy&quot;

- Added sections in &quot;About&quot; menu in MS - for &quot;User Manual&quot;

Existing issues

 * Michael Attali - every 19 minutes HUB 2.0 becomes Online. Every offline duration is different and varies between 3 minutes - 18 minutes.
 * On 28.11.2018 - mass OTA was started in PRD with hotfixes for Gray Shutoff, Flow Sensor and HUB - for the issues about hard water treatment. With receiving the Update command, around 40 systems became offline. Every day different amount of systems were getting back online. The reason is unknown, in progress is testing and trying to reproduce the issue
 * On 28.11.2018 - with starting the mass OTA, the FTP died several times for unknown reasons. For the update to continue, the FTP had to be restarted.

Redmine export
nbfr0crd9uyvbajjmvr93pqecw8za7j