http://wiki.hsyco.com/3.5.0/index.php?title=Special:NewPages&feed=atom&hideredirs=1&limit=50&offset=&namespace=0&username=&tagfilter=&size-mode=max&size=0HSYCO - New pages [en]2024-03-29T06:10:34ZFrom HSYCOMediaWiki 1.33.0http://wiki.hsyco.com/3.5.0/index.php/Notifications_UtilityNotifications Utility2015-11-19T10:55:57Z<p>Giampiero: /* Log */</p>
<hr />
<div>This plugin provides an application for monitoring and configuring notifications for installations comprising heterogeneous sensors and I/O devices managed by several users possibly divided into groups. <br />
<br />
The application allows for the specification of alarm conditions with different levels, generates logs and notifies users via e-mail and/or SMS text messages.<br />
<br />
Before using the plugin, configure all the I/O Servers needed and make sure they all communicate correctly with HSYCO. <br />
<br />
To view the Notifications Utility interface go to the URL of the "notif" project on your server; for instance <nowiki>https://192.168.0.50/hsycoserver/notif</nowiki>.<br />
<br />
The application is divided in the following sections:<br />
<br />
== Groups ==<br />
A group represents a set of users that should receive the same notifications.<br />
<br />
[[File:plugin_notifi_utility_groups.png|border|500px]]<br />
<br />
<br />
Create/delete groups using the '''+'''/'''-''' buttons at the bottom of the list and enter a name.<br />
<br />
For each group you can select the days it is active and, for each day, up to 2 time intervals in which it is active. When a group is active, the users belonging to the group will receive alarm notifications targeted for such group.<br />
<br />
Currently active groups display a "&#149;" symbol next to their names.<br />
<br />
== Users ==<br />
[[File:plugin_notifi_utility_users.png|border|500px]]<br />
<br />
Create/delete users using the '''+'''/'''-''' buttons at the bottom of the list and enter a name.<br />
<br />
*'''E-Mail''': if specified, alarms notifications for the user will be sent to the specified address<br />
*'''Tel.''': if HSYCO is provided with a [[GSM | GSM I/O Server]] you can specify the phone number of the user that will be used to send SMS text notifications to. Use the same number format described in the GSM I/O Server documentation<br />
*'''Group(s)''': select the group(s) the user belongs to<br />
<br />
== Conditions ==<br />
This section is where you define the datapoints to be monitored by the application and specify the conditions that will trigger a notification.<br />
<br />
A datapoint can be either an I/O Served datapoint or a system variable. <br />
<br />
To add a datapoint click on the '''+''' button at the bottom of the list and specify the datapoint ID and a descriptive name.<br />
<br />
[[File:plugin_notifi_utility_conditions_add_dp.png|border|500px]]<br />
<br />
To add an I/O Server datapoint just specify its ID, for variables use the upper-case name prefixed by '$'.<br />
<br />
After you added a datapoint you can optionally specify a unit of measure and upper/lower boundaries for its value to discard error values.<br />
<br />
[[File:plugin_notifi_utility_conditions.png|border|500px]]<br />
<br />
Then you can add notification conditions:<br />
<br />
[[File:plugin_notifi_utility_conditions_add_notif.png|border|500px]]<br />
<br />
* '''Condition''': select among the available comparisons, i.e. equals (=), different from (!), lower than (<) or greater than (>) and enter the reference value<br />
* '''Groups''': select the groups the notification is targeted to<br />
* '''Message''': enter the notification message. You can use the "$val" placeholder that will be replaced with the value that triggered the notification<br />
* To avoid repeated notifications you can specify a time interval after an alarm condition is exited in which new notifications will be suppressed<br />
* '''Level''': select the level of the condition. The level "Log only" will cause the condition to be added to the log when occurring, but no alarm will be displayed and no notification will be sent. The other levels are customisable and must be specified in the file "notifications_utility/config/levels.ini" as follows. <br />
: Add a single line listing the levels values (1 ... N) and the corresponding names. Here is a valid configuration: <br />
: <pre>1=warning; 2=danger; 3=system</pre><br />
<br />
Datapoints for which alarm conditions have been defined show a "&#149;" symbol next to their names in the list. If one of the conditions is active, both the condition and the device name turn red.<br />
<br />
== Alarms ==<br />
[[File:plugin_notifi_utility_alarms.png|border|500px]]<br />
<br />
The main page of the application shows the ongoing alarms.<br />
<br />
When an alarm condition occurs, it is listed in this table and its message will be displayed in red. To acknowledge the alarm click on the entry and confirm the reset.<br />
<br />
If the alarm has been acknowledged, but the condition that triggered it is still persisting, then its message will turn yellow, otherwise it will be removed from the list.<br />
<br />
== Log ==<br />
[[File:plugin_notifi_utility_log.png|border|500px]]<br />
<br />
This page lets you browse and filter the log database. <br />
<br />
The database contains alarm events and reset actions on alarm notifications.<br />
<br />
To perform a search specify a date range and, optionally, the other filter options and click on '''Refresh'''. The result of the query can be sent via e-mail in CSV format clicking on the envelop icon.<br />
<br />
== Events ==<br />
The application generates USER events that can be used to add custom logic to alarm events.<br />
<br />
Whenever a new notification is created, the following USER event is triggered:<br />
<br />
<pre><br />
alarm.new = <notification_message><br />
</pre><br />
<br />
For each datapoint with alarm conditions defined, the following USER events are triggered:<br />
<br />
<pre><br />
alarm.<datapoint_id> = 1 // when at least an alarm condition on the datapoint is true<br />
alarm.<datapoint_id> = 0 // when all alarm conditions on the datapoint are false<br />
</pre></div>Giampierohttp://wiki.hsyco.com/3.5.0/index.php/Alarms_ManagerAlarms Manager2015-10-27T15:23:12Z<p>Ulde: /* File Messages Extension */</p>
<hr />
<div>This plugin provides an application for monitoring and configuring alarms reporting for installations comprising heterogeneous devices such as sensors, input/output devices, network devices and IP cameras, managed by several users possibly divided into groups. The application generates alarm logs and notifies users via e-mail and/or SMS text messages.<br />
<br />
Before using the plugin, configure all the I/O Servers needed and make sure they all communicate correctly with HSYCO. <br />
<br />
To view the Alarms Manager interface go to the URL of the "alarms2" project on your server; for instance <nowiki>https://192.168.0.50/hsycoserver/alarms2</nowiki>.<br />
From the main page you can access the different sections:<br />
<br />
[[File:plugin_alarms_manager_menu.png|border|500px]]<br />
<br />
== Configuration ==<br />
To access the configuration page click on the icon on the bottom-right corner of the main page.<br />
<br />
This section is only available for HSYCO users holding admin rights.<br />
<br />
All the devices defined in the configuration and set as "enabled" will be listed in the corresponding sections of the application with a specific ''view interface''.<br />
<br />
At the bottom of the configuration page you find a link to the [[Wiring Editor]] which gets automatically populated with the I/O devices defined in this application.<br />
<br />
Following is the rest of the configuration sections:<br />
<br />
=== Areas ===<br />
Areas represent separate locations of the installation. Each area comprises different devices and users.<br />
<br />
[[File:plugin_alarms_manager_config_area.png|border|500px]]<br />
[[File:plugin_alarms_manager_config_area_edit.png|border|500px]]<br />
<br />
It is possible to create a hierarchical area structure by assigning parent areas to other areas. It is possible to create as many level as needed.<br />
<br />
If more than one area is defined then, from the main page, it will be possible to select an area to filter the item listed in the various sections of the application.<br />
<br />
=== I/O Devices ===<br />
[[File:plugin_alarms_manager_config_io.png|border|500px]]<br />
[[File:plugin_alarms_manager_config_io_edit.png|border|500px]]<br />
<br />
I/O Devices represent datapoints having a discrete set of possible values. The usual case is datapoints having a 1/0 value (corresponding to the ON/OFF states). <br />
<br />
It is possible to define custom values by selecting the '''custom''' option in the '''value''' settings of a datapoint and listing its possible values separated by a comma (e.g. "1,2,3").<br />
It is also possible to assign a user friendly label to each value appending it to the corresponding value after a ':' character (e.g. "1:OK,2:WARN,3:ERROR").<br />
<br />
If the datapoint corresponds to a writable output and you want to allow users to change its value from the view interface select the '''Writable''' option<br />
<br />
=== Sensors ===<br />
[[File:plugin_alarms_manager_config_sens.png|border|500px]]<br />
[[File:plugin_alarms_manager_config_sens_edit.png|border|500px]]<br />
<br />
As sensors you can add datapoints having "analog" values such as temperature, pressure and so on. <br />
<br />
Configuration parameters:<br />
* '''Unit''': unit symbol used in the view interface for this sensor<br />
* '''Min'''/'''Max''': valid range for the sensor values. Values outside the specified range will be ignored by the application.<br />
* '''Apply transformation''': to be used in case a transformation is needed to calculate the actual measured value from the value of the specified datapoint. For instance, it can be used for temperature probes outputting a 4-20 mA value. The read value will be multiplied by the specified '''m''' value and then added to the '''t''' value.<br />
* '''Create data logger''': whether to create a [[Data Loggers | data logger]] gathering data from this sensor. It will be visible in the sensor's view interface. It is possible to specify the persistence time of the saved data.<br />
<br />
=== Pings ===<br />
[[File:plugin_alarms_manager_config_ping.png|border|500px]]<br />
[[File:plugin_alarms_manager_config_ping_edit.png|border|500px]]<br />
<br />
Here you can add network devices to monitor their connectivity (by means of "ping" requests sent from HSYCO). Specify their IP address or host name and set the device name.<br />
<br />
It is possible to specify the '''interval''' at which ping requests are sent and the number of failures after which the device is considered unresponsive and thus an '''alarm''' is triggered.<br />
<br />
=== Cameras ===<br />
[[File:plugin_alarms_manager_config_cam.png|border|500px]]<br />
[[File:plugin_alarms_manager_config_cam_edit.png|border|500px]]<br />
<br />
The cameras listed here are the ones defined in HSYCO's configuration. You cannot add or configure a camera from here.<br />
<br />
As for the other sections, here you can enable/disable cameras to make them available or not in the view interface and assign them a descriptive name and the associated area.<br />
<br />
=== General ===<br />
[[File:plugin_alarms_manager_config_general.png|border|500px]]<br />
<br />
* '''Delete log files after X days''': specifies the persistence time of the [[#Log | log]] files created by the application<br />
* '''E-Mail sender''': the e-amail address to be used to send alarm notifications to users<br />
* '''Max recording time on manual command''': The [[#Cameras | cameras view interface]] gives the possibility to manually record images from the selected camera. This option specifies when to automatically stop the recording if not manually stopped.<br />
<br />
== Groups ==<br />
[[File:plugin_alarms_manager_groups.png|border|500px]]<br />
<br />
A group represents a set of users monitoring the same set of devices. <br />
<br />
Create/delete groups using the '''+'''/'''-''' buttons at the bottom of the list and enter a name.<br />
<br />
For each group you can select the days it is active and, for each day, up to 2 time intervals in which it is active. When a group is active, the users belonging to the group will receive alarm notifications targeted for such group.<br />
<br />
Groups currently active display a "&#149;" symbol next to their names.<br />
<br />
The '''Receives system alarms''' option specifies whether this group should receive system alarms triggered by the [[System | System I/O Server]] (which should be added in HSYCO's configuration) such as low storage available, no internet connectivity, disconnected I/O Servers and unreachable cameras.<br />
<br />
== Users ==<br />
[[File:plugin_alarms_manager_users.png|border|500px]]<br />
<br />
Create/delete users using the '''+'''/'''-''' buttons at the bottom of the list and enter a name.<br />
<br />
*'''E-Mail''': if specified, alarms notifications for the user will be sent to the specified address<br />
*'''Tel.''': if HSYCO is provided with a [[GSM | GSM I/O Server]] you can specify the phone number of the user that will be used to send SMS text notifications to. Use the same number format described in the GSM I/O Server documentation<br />
*'''Can send group messages''': select if the specified number is allowed to send [[#Group SMS | Group SMS messages]]<br />
*'''Group(s)''': select the group(s) the user belongs to<br />
<br />
== I/O Devices ==<br />
[[File:plugin_alarms_manager_io_in.png|border|500px]]<br />
[[File:plugin_alarms_manager_io_out.png|border|500px]]<br />
<br />
This section lists the configured I/O Devices. <br />
By selecting an entry you can view its current state and, if configured as writable, set its value.<br />
<br />
For each device you can specify alarm conditions that will trigger notifications to the target groups. To add a condition click on the '''+''' icon:<br />
<br />
[[File:plugin_alarms_manager_io_alarm.png|border|500px]]<br />
<br />
The specified message will be sent via e-mail/SMS to the users belonging to the target group (if active) when the specified condition evaluates to true. <br />
To avoid repeated notifications you can specify a time interval after an alarm condition is exited in which new notifications will be suppressed.<br />
<br />
Devices for which alarm conditions have been defined show a "&#149;" symbol next to their names in the list. If one of the conditions is active, both the condition and the device name turn red.<br />
<br />
== Sensors ==<br />
[[File:plugin_alarms_manager_sensor.png|border|500px]]<br />
[[File:plugin_alarms_manager_sensor_dl.png|border|500px]]<br />
<br />
This section lists the configured sensors. By selecting an entry you can view its current state and, if configured, its data logger chart.<br />
<br />
As for I/O devices you can add alarm conditions:<br />
<br />
[[File:plugin_alarms_manager_sensor_alarm.png|border|500px]]<br />
<br />
== Cameras ==<br />
[[File:plugin_alarms_manager_cam.png|border|500px]]<br />
<br />
This page lists all the configured cameras. Click on a list entry to view the video stream of the camera and manually record frames.<br />
<br />
For each camera you can create recording conditions associated to an I/O device switching to a specific value: <br />
<br />
[[File:plugin_alarms_manager_cam_alarm.png|border|500px]]<br />
<br />
== Ping ==<br />
[[File:plugin_alarms_manager_ping.png|border|500px]]<br />
<br />
Here you can see all the monitored network devices and specify the target group(s) to send notifications to in case of loss of connectivity.<br />
<br />
== Log ==<br />
[[File:plugin_alarms_manager_log.png|border|500px]]<br />
<br />
This page lists all the recorded alarm events.<br />
You can select log entries and send them via e-mail in CSV format (clicking on the envelop icon) or delete them (clicking on the '''-''' icon).<br />
<br />
Log entries are also stored in CSV files contained in the directory "alarms_manager_data/logs" in the HSYCO root on the server.<br />
<br />
== Group SMS ==<br />
Enabled users can send group SMS texts to users belonging to groups of the same area.<br />
<br />
To this end, the user should send an SMS to the GSM modem connected to HSYCO with the following format:<br />
<pre><br />
<group_name>#<text><br />
</pre><br />
<br />
This message will be forwarded to all the users belonging to the specified group.<br />
<br />
== Events ==<br />
The application generates USER events that can be used to add custom logic to alarm events.<br />
<br />
For each datapoint with alarm conditions defined, the following USER events are triggered:<br />
<br />
<pre><br />
alarm.<datapoint_id> = 1 // when at least an alarm condition on the datapoint is true<br />
alarm.<datapoint_id> = 0 // when all alarm conditions on the datapoint are false<br />
</pre></div>Giampierohttp://wiki.hsyco.com/3.5.0/index.php/Access_Control_HIDAccess Control HID2015-10-27T10:29:27Z<p>Ulde: </p>
<hr />
<div>This plugin lets you manage an access control installation with HID devices.<br />
<br />
Before using the plugin, configure all the [[Hidedgesolo | HID I/O Servers]] needed and make sure they all communicate correctly with HSYCO. No user configuration will be needed on the HID devices since the access rules are stored and managed by HSYCO.<br />
<br />
To view the access control interface go to the URL of the "access" project on your server; for instance <nowiki>https://192.168.0.50/hsycoserver/access</nowiki>.<br />
<br />
From the main page you can access the different sections:<br />
<br />
[[File:plugin_access_control_hid_menu.png|border|600px]]<br />
<br />
<br />
== Configuration ==<br />
To configure the installation go to the configuration page by clicking on the icon in the bottom-right corner.<br />
<br />
[[File:plugin_access_control_hid_config.png|border|600px]]<br />
<br />
This page list all the defined areas and the detected HID modules.<br />
<br />
=== Areas ===<br />
An area represents a set of modules (doors) which share the same access rules.<br />
<br />
To create a new area, press the "+" button and provide a unique name.<br />
<br />
To edit, remove, disable or re-enable an area, click on the corresponding entry in the list. Disabling an area means temporarily blocking the access to all users to all the doors belonging to the area, until re-enabled. If an area is not enabled, the corresponding entry in the list will have a lowed opacity.<br />
<br />
=== Modules ===<br />
<br />
The list of modules show all the HID Solo IO servers defined in HSYCO's settings and their corresponding names as defined in the modules' configuration.<br />
If an entry appears of red color, it means that HSYCO cannot connect to the module.<br />
<br />
Clicking on an entry in the module's list it is possible to access and edit its configuration:<br />
<br />
* '''ID''': the ID assigned to the corresponding IO server. Cannot be modified.<br />
* '''Name''': by default is the name set in the HID module's configuration. It can be changed to any other unique name.<br />
* '''Enabled''': if unchecked no user will be allowed to access to door.<br />
* '''Type''': <br />
** '''One reade'''r: Only one reader is connected to this module.<br />
** '''Two reader''': Two readers are connected to this module: entrance and exit readers.<br />
** '''Programmer''': This module will not be used to control an entrance; instead, it will be used by the application as card reader to assign cards to users.<br />
* '''Area''': area this module belongs to.<br />
* '''Entrance/Exit reader''':<br />
** '''Card''': users only use cards to access from this reader.<br />
** '''Pin''': users only use pin codes to access from this reader.<br />
** '''Card and Pin''': users use cards in combination with pin codes to access from this reader.<br />
**'''Card or Pin''': users use cards or pin codes to access from this reader.<br />
* '''Invert entrance/exit''': in the case of a "Two readers" module, checking this option will cause the application to invert the default transit directions.<br />
<br />
=== System access ===<br />
The '''System Users''' and '''Permissions''' buttons allow to manage the system users who will use the access control application and specify which functionalities to allow/deny to each user.<br />
<br />
=== Installation settings ===<br />
The '''Facility code''' must be set to the value assigned by HID to your installation when purchasing the system.<br />
<br />
The '''Max delay between card and pin''' option allows to specify how much time can elapse between the reading of a card and the inputing of the pin code for readers with typology "Card and Pin".<br />
<br />
=== Backup ===<br />
The '''Backup''' button gives access to the list of previously saved backups and allows to create a backup of the current configuration.<br />
<br />
== User Groups ==<br />
[[File:plugin_access_control_hid_groups.png|border|600px]]<br />
<br />
This page lists all defined user groups and their access rules.<br />
<br />
To create a new group click on the "+" button at the bottom of the list. Set a descriptive name, select the areas accessible by this group and specify the daily schedules.<br />
<br />
The "Enabled" option, if unchecked, disables the access for all the users belonging to this group. <br />
<br />
The "Special dates" link takes you to a page where you can define exceptional dates on which the access rules are different from the daily schedules set in the user groups page. <br />
Each rule will be applied only to the groups selected in the corresponding field, for the groups not selected the normal daily schedule will apply.<br />
<br />
[[File:plugin_access_control_hid_spec_dates.png|border|600px]]<br />
<br />
== Users ==<br />
[[File:plugin_access_control_hid_users.png|border|600px]]<br />
<br />
This page lists the users of the facility divided by groups. Select a user group to see the users belonging to it.<br />
<br />
To add a user, select the user group to add it to and click on the "+" button. Then, enter the user name, optionally add a due date after which the user won't be granted any access and specify the corresponding card number and/or pin code. <br />
If programmer modules are available it will be possible to use them to read the card numbers.<br />
<br />
Unchecking the "Enabled" option will deny the access of the user to all areas until re-enabled.<br />
<br />
To permanently remove a user, select the corresponding entry in the list, click on the "-" button and confirm the operation.<br />
<br />
== Doors status ==<br />
[[File:plugin_access_control_hid_doors.png|border|600px]]<br />
<br />
This section lists all the detected doors connected to the system. Select an entry to check its status or to send commands.<br />
<br />
An open door will be of yellow color in the list, while doors with active alarms will be of red color.<br />
<br />
== Logs ==<br />
[[File:plugin_access_control_hid_log.png|border|600px]]<br />
<br />
In this page the last 1000 system events are reported.<br />
<br />
It is possible to filter the entries clicking on the magnifier icon end setting the desired criteria.<br />
<br />
[[File:plugin_access_control_hid_log_search.png|border|600px]]<br />
<br />
The result entries can be exported via e-mail.<br />
<br />
Log entries are also permanently saved in CSV format in files contained in the directory "access_ctrl/logs" in the HSYCO root on the server.<br />
<br />
== Events ==<br />
The application generates USER events that can be used to add custom logic to access events.<br />
<br />
When a user is granted access the following USER events are triggered:<br />
<pre><br />
access.granted.door.<module_id> = <group_name><br />
access.granted.area.<area_name> = <group_name><br />
</pre><br />
<br />
When a user is denied access the following USER events are triggered:<br />
<pre><br />
access.granted.door.<module_id> = <group_name_if_available_or_empty_string><br />
access.granted.area.<area_name> = <group_name_if_available_or_empty_string><br />
</pre></div>Giampierohttp://wiki.hsyco.com/3.5.0/index.php/PluginsPlugins2015-10-27T09:43:53Z<p>Giampiero: </p>
<hr />
<div>We provide a set of vertical solutions for HSYCO installations as plugins.<br />
<br />
This page lists all the available plugins and links to their documentation.<br />
<br />
* [[Access Control HID]]<br />
* [[Alarms Manager]]<br />
* [[Notifications Utility]]</div>Giampierohttp://wiki.hsyco.com/3.5.0/index.php/Service_Bullettin_20150911_Chrome45Service Bullettin 20150911 Chrome452015-09-11T12:09:22Z<p>Ulde: /* References */</p>
<hr />
<div>[[Category: Service Bulletin]]<br />
<br />
== Service Bulletin - Chrome and Firefox drop support for servers using weak Diffie-Hellman public keys ==<br />
New versions of some web borwsers have dropped support for web servers using Diffie-Hellman public keys shorter than 1024 bits.<br />
<br />
=== Release Date ===<br />
September 10, 2015<br />
<br />
=== Affected Platforms ===<br />
*Any HSYCO Server using the Java 6 virtual machine, independently of the HSYCO software version<br />
*Google Chrome version 45<br />
*Mozilla Firefox 39.0<br />
<br />
<br />
{{note|HSYCO servers using Java 7 are not affected. Most HSYCO units shipped after the first half of 2012 have Java 7 pre-installed.}}<br />
<br />
=== Description ===<br />
HSYCO uses native Java libraries, embedded in the installed Oracle Java Virtual Machine, to implement its internal HTTPS server. Java 6's HTTPS libraries use Diffie-Hellman public keys that Google and Mozilla now consider weak, after the so-called Logjam vulnerability has been discovered. This is independent of the HSYCO software version currently installed on the server.<br />
<br />
When you try to access an HSYCO running on Java 6 via a secure HTTPS connection using the latest versions of Chrome or Firefox, the connection will not work. HTTP (not encrypted) connections are not affected by this issue.<br />
<br />
=== Resolution ===<br />
Both Chrome and Firefox have decided to implement these more restrictive HTTPS requirements, but failed to offer their users an option to either accept of reject a connection to a server which doesn't match these requirements.<br />
<br />
To continue using your HSYCO, you have the following options:<br />
*use a different browser, that still accepts Diffie-Hellman public keys generated by Java 6, like Microsoft's Internet Explorer or Apple's Safari<br />
*implement the work-arounds that have been published on-line, and are described below<br />
*return the HSYCO Server for service to upgrade to Java 7. Please note that you will be charged a service fee for this upgrade.<br />
<br />
=== Resolution: Chrome ===<br />
<br />
{{note|The following solution is reported here, for your convenience only, as found on unverified on-line resources available to the public. Home Systems Consulting is not responsible, and cannot guarantee, that it will work correctly and that there are no side-effects that could affect the stability, integrity and security of your systems. Use at your own risk.}}<br />
<br />
You should launch Chrome with the following startup option:<br />
<br />
--cipher-suite-blacklist=0x0088,0x0087,0x0039,0x0038,0x0044,0x0045,0x0066,0x0032,0x0033,0x0016,0x0013<br />
<br />
On Windows:<br />
<br />
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --cipher-suite-blacklist=0x0088,0x0087,0x0039,0x0038,0x0044,0x0045,0x0066,0x0032,0x0033,0x0016,0x0013<br />
<br />
Execute ad Administrator.<br />
<br />
On Mac OSX:<br />
<br />
/Applications/Google\ Chrome.app --args '--cipher-suite-blacklist=0x0088,0x0087,0x0039,0x0038,0x0044,0x0045,0x0066,0x0032,0x0033,0x0016,0x0013'<br />
<br />
<br />
=== Resolution: Firefox ===<br />
<br />
{{note|The following solution is reported here, for your convenience only, as found on unverified on-line resources available to the public. Home Systems Consulting is not responsible, and cannot guarantee, that it will work correctly and that there are no side-effects that could affect the stability, integrity and security of your systems. Use at your own risk.}}<br />
<br />
*in Firefox, Enter “about:config” in the URL field and press enter<br />
*accept the “This might void your warranty!” warning by clicking “I’ll be careful, I promise!” button<br />
*in the search field, enter “security.ssl3.dhe_rsa_aes”<br />
*double click each result (128 SHA and 256 SHA) to toggle the Value to “false”.<br />
<br />
=== References ===<br />
*[https://weakdh.org Weak Diffie-Hellman and the Logjam Attack]<br />
*[https://productforums.google.com/forum/#!topic/chrome/o3vZD-Mg2Ic Google Chrome Help Forum]</div>Uldehttp://wiki.hsyco.com/3.5.0/index.php/HSYCO_Remote_for_iOS_DevicesHSYCO Remote for iOS Devices2015-09-05T14:19:36Z<p>Ulde: /* Apple Watch */</p>
<hr />
<div>HSYCO Remote is an iOS application for iPhone, iPad and iPod touch that lets you easily connect to your HSYCO Server, in a more convenient way than traditional Web-based access.<br />
<br />
HSYCO Remote can use Touch ID for authentication, and handles your PIN/PUK credentials automatically in the background.<br />
<br />
HSYCO Remote allows you to define your favourite interfaces and to quickly switch between them. It also supports rotation lock and kiosk mode.<br />
<br />
HSYCO Remote also offers Apple Watch support, so you can send any command to your HSYCO Server using your Apple Watch. And if you have multiple HSYCO Servers, a simple swipe on Apple Watch will immediately switch from one server to another.<br />
<br />
<br />
{{note|<center>HSYCO Remote requires iOS 8.2 or later, and HSYCO Server 3.5.0.</center>}}<br />
<br />
To download the HSYCO App, go to your Apple App Store and enter HSYCO in the search box, or click the App Store badge below.<br />
<br />
<br />
<center>[[File:Download_on_the_App_Store_Badge_US-UK_135x40.png|135x40px|link=https://itunes.apple.com/app/hsyco/id1038105480]]</center><br />
<br />
<br />
<br />
==Configuring a connection==<br />
<br />
In the Connections page, press Edit, then + at the bottom, or select an existing connection to edit.<br />
<br />
Enter a name for the connection (connections are listed in alphabetical order by name) and the URL to access your project on your HSYCO server.<br />
<br />
If you have a default project on your server, and use a standard port for the HTTPS connection, you can simply enter the DNS name for your server, without the URL key and project name.<br />
<br />
Enable the Remember PIN option to automatically save your PIN and PUK after the initial validation.<br />
<br />
The Kiosk Mode option enables HSYCO’s kiosk mode, while Lock Rotation prevents rotation and switch between portrait and landscape pages in the project.<br />
<br />
Enable the Favorite option if you want to have this connection in the Favorites list of the main Menu page.<br />
<br />
If your server has a self-generated SSL certificate for HTTPS encryption, you should download and install the server’s certificate in your iOS device profiles, otherwise HSYCO Remote will not be able to establish the connection with the server. Press Download Certificate at the bottom of the page. Safari will open and let you download, accept and install the server’s certificate. Only after the certificate is installed you will be able to use the connection you have configured in HSYCO Remote.<br />
<br />
<br />
[[File:Hsyco_remote_ios_connections.png|200px|border]] [[File:Hsyco_remote_ios_connection_edit.png|200px| border]]<br />
<br />
==Settings==<br />
<br />
In Settings you can enable the Ask Password option to set a password, and optionally use Touch ID, to protect access to HSYCO Remote.<br />
<br />
Once a password has been set, you can enable Touch ID, and set the Lock on Exit and Auto-Lock options.<br />
<br />
When in landscape mode, you can hide the header by disabling the Header in Landscape Mode option. This option is disabled by default on the iPhone, and enabled on iPad.<br />
<br />
Press Clear Cache if you want to clear all connections cache.<br />
<br />
Reset Settings is used to reset all settings of HSYCO Remote.<br />
<br />
<br />
[[File:Hsyco_remote_ios_settings1.png|200px|border]] [[File:Hsyco_remote_ios_settings2.png|200px|border]]<br />
<br />
==Apple Watch==<br />
<br />
If one or more of your connections are associated with HSYCO projects configured with Apple Watch menus, you will automatically have them configured in the Apple Watch.<br />
<br />
If you change the Apple Watch menu in any project on HSYCO Server, simply open the corresponding connection in HSYCO Remote to load the new version. After this, next time you open HSYCO Remote on your Apple Watch, it will automatically show the updated command menu.<br />
<br />
To create an Apple Watch menu for a project, use a project's UISet to set the [[Project#Apple_Watch_support.2C_the_app_watch_attribute|app_watch]] attribute.</div>Uldehttp://wiki.hsyco.com/3.5.0/index.php/GoogleCalendarGoogleCalendar2015-08-31T15:30:29Z<p>Giampiero: /* Datapoints */</p>
<hr />
<div>This driver allows for the use of [https://www.google.com/calendar Google Calendar] as a scheduler.<br />
<br />
[[Category:I/O Server]]<br />
<br />
== HSYCO Configuration ==<br />
Add a GOOGLECAL I/O Server in the [[Settings#I/O Servers|I/O Servers section of the Settings]] and set its parameters:<br />
<br />
=== High Availability ===<br />
*'''Shutdown when inactive''': defaults to false.<br />
<br />
=== Options ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Default<br />
!Values<br />
!Description<br />
<br />
|-<br />
<br />
|pollinterval<br />
|10<br />
|n > 0<br />
|the data acquisition interval, in seconds<br />
<br />
|-<br />
<br />
|calendars<br />
|<br />
|<id_list><br />
|list of calendars IDs separated by ';' (see [[#Setup|Setup]] for details). Omit this option to use the primary calendar<br />
<br />
|-<br />
<br />
|code<br />
|<br />
|<nowiki><code></nowiki><br />
|authorization code (see [[#Setup|Setup]] for details)<br />
<br />
|-<br />
<br />
|pre<br />
|<br />
|n > 0<br />
|if this option is added, the datapoints "<cal_name>.pre" are generated to show the upcoming events with an advance of n minutes<br />
<br />
|}<br />
<br />
== Setup ==<br />
<br />
=== Enable the Google Calendar API ===<br />
<br />
* Use [https://console.developers.google.com/start/api?id=calendar this wizard] to create or select a project in the Google Developers Console and automatically enable the API. Click the '''Go to credentials''' button to continue.<br />
* At the top of the page, select the '''OAuth consent screen''' tab. Select an '''Email address''', enter a '''Product name''' if not already set, and click the '''Save''' button.<br />
* Back on the '''Credentials''' tab, click the '''Add credentials''' button and select '''OAuth 2.0 client ID'''.<br />
* Select the application type '''Other''' and click the '''Create''' button.<br />
* Click '''OK''' to dismiss the resulting dialog.<br />
* Click the '''Download JSON''' button to the right of the client ID. <br />
* Move the downloaded file to HSYCO server, place it into a folder called "google-calendar" in the root and rename it "client_secret.json".<br />
<br />
The "client_secret.json" can be reused for multiple I/O server instances, even on different HSYCO servers.<br />
<br />
=== Create the calendar ===<br />
<br />
* Go to [https://www.google.com/calendar/ Google Calendar] and create a Google account or use your personal one to login.<br />
* If you are going to use the primary calendar for this account you are done, go to the next section. If, on the other hand, you want to create a separate calendar for HSYCO (or more that one), continue here.<br />
* From the left column, click on the small option menu button on the right of '''My Calendars'''; select '''Create new calendar'''.<br />
* Enter a name, set the other settings as desired and click on '''Create calendar'''.<br />
* Find the created calendar from the list under '''My Calendars''', select the option menu button on its right and select '''Calendar settings'''.<br />
* Go to the section '''Calendar Address''' and copy the displayed '''Calendar ID'''.<br />
* Go to the settings of the I/O Server and set the value of the "calendars" option to the copied calendar ID. If you want to use more that one calendar, repeat the above procedure to create another one and add its ID to the "calendars" option using ';' to separate the IDs.<br />
<br />
=== Authorize access ===<br />
<br />
The first time the driver is started it requires access permission to the calendar information of the selected Google account. This procedure is necessary for each I/O Server instance created.<br />
<br />
Shortly after the driver is started for the first time, the value of the datapoint "auth" will be set to a long URL string. Copy that URL and paste it into a browser. Login with the selected Google account and click on '''Accept'''.<br />
<br />
The next page will show a code. Go to the settings of the I/O Server and set the value of the "code" option to this code; save and wait for the server to restart.<br />
<br />
=== Scheduling events ===<br />
<br />
To trigger an event on HSYCO during a specific time just create an event in the calendar for the selected time period and set its title to a string of your choice.<br />
<br />
For instance, let's say the calendar is called "hsycocal" and the title of the created event is "go". During the specified time period the driver will set its datapoint "hsycocal" to the value "go". <br />
<br />
When no event is scheduled for the current moment, the value of the datapoint will be set to an empty string; if there are overlapping events, the value will list all the titles separated by ';'.<br />
<br />
== Datapoints ==<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!R/W<br />
!Description<br />
<br />
|-<br />
<br />
|rowspan="2" |connection<br />
|online<br />
|R<br />
|connection established<br />
|-<br />
|offline<br />
|R<br />
|HSYCO can't connect to the service<br />
<br />
|-<br />
<br />
|<cal_name><br />
|<events_list><br />
|R<br />
|list of ongoing events in the calendar with name <cal_name>. Events names are separated by ';'<br />
<br />
|-<br />
<br />
|<cal_name>.pre<br />
|<events_list><br />
|R<br />
|list of upcoming events in the calendar with name <cal_name>, with an advance specified by the "pre" option. Events names are separated by ';'. If the "pre" option is omitted these datapoints are not created<br />
<br />
|}<br />
<br />
== Release Notes ==<br />
<br />
=== 3.5.0 ===<br />
*initial release<br />
<br />
----<br />
<br />
<br />
''Google is a registered trademarks of Google Inc.''</div>Giampierohttp://wiki.hsyco.com/3.5.0/index.php/StratoStrato2015-08-17T13:12:33Z<p>Ulde: /* 3.5.0 */</p>
<hr />
<div>[[Category:I/O Server]]<br />
<br />
[http://www.sferalabs.cc/strato/ Strato Pi] is an expansion board developed by Sfera Labs for the Raspberry Pi computer.<br />
<br />
[[File:Strato_Board.png|200px|thumb|Strato Pi]]<br />
<br />
Strato Pi implements a number of hardware features to expand the Pi and allows its use in professional applications:<br />
*9-28 Vdc extended-range power supply<br />
*integrated UPS with external NiCd rechargeable battery<br />
*real-time clock with dedicated back-up battery<br />
*opto-isolated RS-232 or RS-485 serial port<br />
*configurable hardware watchdog<br />
*buzzer for audible feedback.<br />
<br />
<br />
== HSYCO Configuration ==<br />
Add a STRATO I/O Server in the [[Settings#I/O Servers|I/O Servers section of the Settings]] and set its parameters.<br />
<br />
{{note|Note that the Strato I/O Server doesn't count in the I/O servers license total, so you don't need an extra I/O Server license to use Strato with HSYCO.}}<br />
<br />
=== High Availability ===<br />
*'''Shutdown when inactive''': defaults to false.<br />
<br />
=== Options ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Default<br />
!Values<br />
!Description<br />
<br />
|-<br />
<br />
|rowspan="2"|watchdog<br />
|rowspan="2"|false<br />
|true<br />
|enables the hardware watchdog and automatically generates the heartbeat signal<br />
|-<br />
|false<br />
|disables the hardware watchdog<br />
<br />
|-<br />
<br />
|rowspan="2"|shutdown_minutes<br />
|rowspan="2"|0<br />
|0<br />
|no automatic shutdown after power failure<br />
|-<br />
|int > 0<br />
|the driver will command the operating system shutdown and hardware power off after N minutes of back-up battery operations during a power failure. The Strato board will automatically power-up the Pi when power is restored<br />
<br />
|-<br />
<br />
|rowspan="2"|quiet<br />
|rowspan="2"|false<br />
|true<br />
|enables audible alarms on power failure<br />
|-<br />
|false<br />
|disables audible alarms on power failure<br />
<br />
|}<br />
<br />
== Datapoints ==<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!R/W<br />
!Description<br />
<br />
|-<br />
<br />
|rowspan="2" |battery<br />
|0<br />
|R<br />
|power supply is available<br />
|-<br />
|1<br />
|R<br />
|power supply failure, running on UPS battery<br />
<br />
|-<br />
<br />
|rowspan="6" |beep<br />
|0<br />
|R<br />
|buzzer is off<br />
|-<br />
|1<br />
|R<br />
|buzzer is on<br />
|-<br />
|off<br />
|W<br />
|turn buzzer off<br />
|-<br />
|on<br />
|W<br />
|turn buzzer on (continuous tone)<br />
|-<br />
|<duration><br />
|W<br />
|turn buzzer on for <duration> seconds (decimals allowed)<br />
|-<br />
|<duration>;<pause><br />
|W<br />
|turn buzzer on for <duration> seconds, then pause for <pause> seconds (decimals allowed)<br />
<br />
|-<br />
<br />
|rowspan="4" |heartbeat<br />
|rowspan="2" |0<br />
|R<br />
|heartbeat line is off<br />
|-<br />
|W<br />
|set heartbeat line to off<br />
|-<br />
|rowspan="2" |1<br />
|R<br />
|heartbeat line is on<br />
|-<br />
|W<br />
|set heartbeat line to on<br />
<br />
|-<br />
<br />
|rowspan="3" |shutdown<br />
|0<br />
|R<br />
|shutdown line is off<br />
|-<br />
|rowspan="2" |1<br />
|R<br />
|shutdown line is on<br />
|-<br />
|W<br />
|set shutdown line to on (Strato will wait approximately 60 seconds, then execute a power off-on cycle. Once the shutdown line is set to on, the power cycle procedure can't be reset<br />
<br />
|-<br />
<br />
|rowspan="2" |timeout<br />
|0<br />
|R<br />
|hardware watchdog timeout line is off<br />
|-<br />
|1<br />
|R<br />
|hardware watchdog timeout line is on. Strato will set this line to on, then wait approximately 60 seconds and execute a power off-on cycle<br />
<br />
|-<br />
<br />
|rowspan="4" |watchdog<br />
|rowspan="2" |0<br />
|R<br />
|hardware watchdog is disabled<br />
|-<br />
|W<br />
|disables the hardware watchdog<br />
|-<br />
|rowspan="2" |1<br />
|R<br />
|hardware watchdog is enabled<br />
|-<br />
|W<br />
|enables the hardware watchdog. When enabled, Strato should see an off-on transition on the hearbeat line at least every 60 seconds, otherwise a power cycle will be initiated, setting the timeout line on, then waiting 60 seconds, removing power to the Pi for 5 seconds, and finally restoring power<br />
<br />
|}<br />
<br />
== Release Notes ==<br />
<br />
=== 3.5.0 ===<br />
*initial release<br />
<br />
----<br />
<br />
<br />
''Strato is a registered trademark of Home Systems Consulting S.p.A.''</div>Ulde