https://wiki.hsyco.com/3.7/api.php?action=feedcontributions&user=Ulde&feedformat=atomHSYCO - User contributions [en]2024-03-29T09:33:17ZUser contributionsMediaWiki 1.33.0https://wiki.hsyco.com/3.7/index.php?title=HSYCO&diff=9466HSYCO2022-05-11T05:30:15Z<p>Ulde: </p>
<hr />
<div>__NOTITLE__<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="100%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle welcome">Welcome to the HSYCO Wiki 3.7</div><br />
<div class="mainpageContent"><br />
'''HSYCO''' is an innovative Java-based software framework for home and building automation applications.<br />
<br />
It is highly scalable, portable, secure, reliable and customizable.<br />
HSYCO combines an efficient HTML5 GUI, with web-based design tools, and an extensive Java and JavaScript server API for the automation and control logic.<br />
<br />
Compared to legacy building automation solutions, it offers a state-of-the-art architecture that is fully based on leading modern standards, like HTML5, CSS3, JavaScript and Java.<br />
<br />
<br />
<br />
This wiki contains all relevant configuration and development information of the latest version of HSYCO.<br />
<br />
The documentation of previous versions is available in the [[Download]] page.<br />
</div><br />
<div class="mainpageLinks"><br />
'''[[Download]] | [[About HSYCO]] | [[Products]] | [[Support]] | [[FAQ]]'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Installation and Configuration</div><br />
<div class="mainpageContent"><br />
[[File:Main Page System Administrator.png|x80px|center|link=]]<br />
Install and configure HSYCO Server<br />
*'''[[Installation Guide]]'''<br />
*'''[[Settings|Configuration Guide]]'''<br />
*'''[[HSYCO_App|HSYCO App for iOS and Android]]'''<br />
*'''[[System Architecture]]'''<br />
</div><br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Development</div><br />
<div class="mainpageContent"><br />
[[File:Main Page Development.png|x80px|center|link=]]<br />
Design your interfaces and develop your applications<br />
*'''[[User Interface|User Interface Design]]'''<br />
*'''[[Programming]]'''<br />
*'''[[Advanced Programming]]'''<br />
</div><br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Integration</div><br />
<div class="mainpageContent"><br />
[[File:Main Page Integration.png|x80px|center|link=]]<br />
How to interface external systems<br />
*'''[[Introduction to I/O Servers]]'''<br />
*'''[[I/O Servers|I/O Servers Application Notes]]'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Versions</div><br />
<div class="mainpageContent"><br />
*The latest stable release is 3.7.1<br />
*The latest release of the previous version is 3.6.1<br />
<br />
<br />
'''[[Release_Notes_3.7.1|3.7.1 Release Notes]]'''<br />
<br />
'''[[Release_Notes_3.7.0|3.7.0 Release Notes]]'''<br />
<br />
'''[[Release_Notes_3.6.1|3.6.1 Release Notes]]''' and '''[http://wiki.hsyco.com/3.6.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.6.0|3.6.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.6.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.5.1|3.5.1 Release Notes]]''' and '''[http://wiki.hsyco.com/3.5.1 Documentation]'''<br />
<br />
'''[[Release_Notes_3.5.0|3.5.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.5.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.4.0|3.4.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.4.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.3.0|3.3.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.3.0 Documentation]'''<br />
<br />
<br />
<br />
<br />
'''Visit the [[Download]] page to download all current and past versions of the HSYCO server software.'''<br />
</div><br />
| valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">News</div><br />
<div class="mainpageContent"><br />
*2022/05/11<br />
**HSYCO 3.7.1 B0136 is available for download. This build contains important security updates, and is recommended for all installations<br />
*2020/10/21<br />
**HSYCO 3.7.0 release is available for download<br />
*2019/08/08<br />
**HSYCO 3.7.0 B0129 BETA is available for download. All users are advised to upgrade to build 0129<br />
*2019/02/01<br />
**HSYCO 3.7.0 B0128 BETA is available for download. This build fixes a bug introduced with previous beta build, that could cause an abnormal number of HTTP requests to the weather service provider. All users are advised to upgrade to build 0128<br />
*2019/01/15<br />
**HSYCO 3.7.0 B0127 BETA is available for download<br />
*2018/03/01<br />
**HSYCO 3.6.1 release is available for download<br />
*2017/11/28<br />
**HSYCO 3.6.0 release is available for download<br />
*2016/04/15<br />
**HSYCO 3.5.1 release is available for download<br />
*2016/1/26<br />
**HSYCO 3.5.1 B0122 BETA is available for download<br />
*2015/10/15<br />
**HSYCO 3.5.0 release is available for download<br />
*2015/9/26<br />
**HSYCO Remote App for iOS and Apple Watch is now available on the [https://itunes.apple.com/app/hsyco/id1038105480 Apple App Store]. Version 1.0.1 with improved support for iOS 9 coming soon<br />
*2015/7/31<br />
**HSYCO 3.5.0 B0120 BETA is available for download<br />
*2015/5/18<br />
**HSYCO 3.5.0 B0119 BETA is available for download<br />
*2015/4/24<br />
**HSYCO 3.5.0 BETA documentation is on-line<br />
*2014/12/22<br />
**HSYCO 3.4.0 release is available for download<br />
*2014/10/24<br />
**Due to the large number of enhancements (not only bug fixes) in the current beta release, formerly known as 3.3.1, we are now promoting it to 3.4.0. There will be no official release of 3.3.1, and all changes are merged in the upcoming 3.4.0 release<br />
*2014/8/7<br />
**HSYCO 3.3.1 B0115 BETA is now available for download<br />
*2014/6/4<br />
**HSYCO 3.3.1 B0114 BETA is available for download<br />
*2014/3/25<br />
**HSYCO 3.3.0 release is available for download<br />
*2014/2/24<br />
**HSYCO 3.3.0 B0112 BETA is available for download<br />
*2013/12/23<br />
**HSYCO 3.3.0 B0109 BETA is available for download<br />
*2013/9/10<br />
**HSYCO 3.2.3 release is available for download<br />
*2013/6/12<br />
**HSYCO 3.2.2 release is available for download<br />
*2013/4/19<br />
**HSYCO 3.2.1 release is available for download<br />
<br />
<br />
'''Older news have been removed from this site. If you need specific information about old releases, please contact us.'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="100%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Service Bulletins</div><br />
<div class="mainpageContent"><br />
*2020/2/5: '''[[Service_Bulletin_20200205_Telegram_BOT|Telegram now requires the TLSv1.2 cryptographic protocol, breaking compatibility on Java 6 and Java 7 virtual machines]]'''<br />
*2019/1/3: '''[[Service_Bulletin_20190103_Yahoo_Weather_API_EOL|Yahoo drops supports for its weather API used in the WXOnline HSYCO I/O Server]]'''<br />
*2016/3/15: '''[[Service_Bullettin_20160315_Yahoo_Weather_API|Yahoo drops supports for previous version of its weather API and introduces new API]]'''<br />
*2015/9/10: '''[[Service_Bullettin_20150911_Weak_DH_HTTPS_Server_Keys|Chrome and Firefox drop support for servers using weak Diffie-Hellman public keys]]'''<br />
</div><br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Release_Notes_3.7.1&diff=9465Release Notes 3.7.12022-05-11T05:28:51Z<p>Ulde: Created page with " Category: Release Notes == Bug Fixes == *HTTP Server: **fixed a security vulnerability that could allow unauthorized access to local files"</p>
<hr />
<div><br />
[[Category: Release Notes]]<br />
<br />
== Bug Fixes ==<br />
*HTTP Server:<br />
**fixed a security vulnerability that could allow unauthorized access to local files</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=HSYCO&diff=9464HSYCO2022-05-11T05:27:37Z<p>Ulde: </p>
<hr />
<div>__NOTITLE__<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="100%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle welcome">Welcome to the HSYCO Wiki 3.7</div><br />
<div class="mainpageContent"><br />
'''HSYCO''' is an innovative Java-based software framework for home and building automation applications.<br />
<br />
It is highly scalable, portable, secure, reliable and customizable.<br />
HSYCO combines an efficient HTML5 GUI, with web-based design tools, and an extensive Java and JavaScript server API for the automation and control logic.<br />
<br />
Compared to legacy building automation solutions, it offers a state-of-the-art architecture that is fully based on leading modern standards, like HTML5, CSS3, JavaScript and Java.<br />
<br />
<br />
<br />
This wiki contains all relevant configuration and development information of the latest version of HSYCO.<br />
<br />
The documentation of previous versions is available in the [[Download]] page.<br />
</div><br />
<div class="mainpageLinks"><br />
'''[[Download]] | [[About HSYCO]] | [[Products]] | [[Support]] | [[FAQ]]'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Installation and Configuration</div><br />
<div class="mainpageContent"><br />
[[File:Main Page System Administrator.png|x80px|center|link=]]<br />
Install and configure HSYCO Server<br />
*'''[[Installation Guide]]'''<br />
*'''[[Settings|Configuration Guide]]'''<br />
*'''[[HSYCO_App|HSYCO App for iOS and Android]]'''<br />
*'''[[System Architecture]]'''<br />
</div><br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Development</div><br />
<div class="mainpageContent"><br />
[[File:Main Page Development.png|x80px|center|link=]]<br />
Design your interfaces and develop your applications<br />
*'''[[User Interface|User Interface Design]]'''<br />
*'''[[Programming]]'''<br />
*'''[[Advanced Programming]]'''<br />
</div><br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Integration</div><br />
<div class="mainpageContent"><br />
[[File:Main Page Integration.png|x80px|center|link=]]<br />
How to interface external systems<br />
*'''[[Introduction to I/O Servers]]'''<br />
*'''[[I/O Servers|I/O Servers Application Notes]]'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Versions</div><br />
<div class="mainpageContent"><br />
*The latest stable release is 3.7.1<br />
*The latest release of the previous version is 3.6.1<br />
<br />
<br />
'''[[Release_Notes_3.7.1|3.7.1 Release Notes]]'''<br />
<br />
'''[[Release_Notes_3.7.0|3.7.0 Release Notes]]'''<br />
<br />
'''[[Release_Notes_3.6.1|3.6.1 Release Notes]]''' and '''[http://wiki.hsyco.com/3.6.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.6.0|3.6.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.6.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.5.1|3.5.1 Release Notes]]''' and '''[http://wiki.hsyco.com/3.5.1 Documentation]'''<br />
<br />
'''[[Release_Notes_3.5.0|3.5.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.5.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.4.0|3.4.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.4.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.3.0|3.3.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.3.0 Documentation]'''<br />
<br />
<br />
<br />
<br />
'''Visit the [[Download]] page to download all current and past versions of the HSYCO server software.'''<br />
</div><br />
| valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">News</div><br />
<div class="mainpageContent"><br />
*2020/10/21<br />
**HSYCO 3.7.0 release is available for download<br />
*2019/08/08<br />
**HSYCO 3.7.0 B0129 BETA is available for download. All users are advised to upgrade to build 0129<br />
*2019/02/01<br />
**HSYCO 3.7.0 B0128 BETA is available for download. This build fixes a bug introduced with previous beta build, that could cause an abnormal number of HTTP requests to the weather service provider. All users are advised to upgrade to build 0128<br />
*2019/01/15<br />
**HSYCO 3.7.0 B0127 BETA is available for download<br />
*2018/03/01<br />
**HSYCO 3.6.1 release is available for download<br />
*2017/11/28<br />
**HSYCO 3.6.0 release is available for download<br />
*2016/04/15<br />
**HSYCO 3.5.1 release is available for download<br />
*2016/1/26<br />
**HSYCO 3.5.1 B0122 BETA is available for download<br />
*2015/10/15<br />
**HSYCO 3.5.0 release is available for download<br />
*2015/9/26<br />
**HSYCO Remote App for iOS and Apple Watch is now available on the [https://itunes.apple.com/app/hsyco/id1038105480 Apple App Store]. Version 1.0.1 with improved support for iOS 9 coming soon<br />
*2015/7/31<br />
**HSYCO 3.5.0 B0120 BETA is available for download<br />
*2015/5/18<br />
**HSYCO 3.5.0 B0119 BETA is available for download<br />
*2015/4/24<br />
**HSYCO 3.5.0 BETA documentation is on-line<br />
*2014/12/22<br />
**HSYCO 3.4.0 release is available for download<br />
*2014/10/24<br />
**Due to the large number of enhancements (not only bug fixes) in the current beta release, formerly known as 3.3.1, we are now promoting it to 3.4.0. There will be no official release of 3.3.1, and all changes are merged in the upcoming 3.4.0 release<br />
*2014/8/7<br />
**HSYCO 3.3.1 B0115 BETA is now available for download<br />
*2014/6/4<br />
**HSYCO 3.3.1 B0114 BETA is available for download<br />
*2014/3/25<br />
**HSYCO 3.3.0 release is available for download<br />
*2014/2/24<br />
**HSYCO 3.3.0 B0112 BETA is available for download<br />
*2013/12/23<br />
**HSYCO 3.3.0 B0109 BETA is available for download<br />
*2013/9/10<br />
**HSYCO 3.2.3 release is available for download<br />
*2013/6/12<br />
**HSYCO 3.2.2 release is available for download<br />
*2013/4/19<br />
**HSYCO 3.2.1 release is available for download<br />
<br />
<br />
'''Older news have been removed from this site. If you need specific information about old releases, please contact us.'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="100%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Service Bulletins</div><br />
<div class="mainpageContent"><br />
*2020/2/5: '''[[Service_Bulletin_20200205_Telegram_BOT|Telegram now requires the TLSv1.2 cryptographic protocol, breaking compatibility on Java 6 and Java 7 virtual machines]]'''<br />
*2019/1/3: '''[[Service_Bulletin_20190103_Yahoo_Weather_API_EOL|Yahoo drops supports for its weather API used in the WXOnline HSYCO I/O Server]]'''<br />
*2016/3/15: '''[[Service_Bullettin_20160315_Yahoo_Weather_API|Yahoo drops supports for previous version of its weather API and introduces new API]]'''<br />
*2015/9/10: '''[[Service_Bullettin_20150911_Weak_DH_HTTPS_Server_Keys|Chrome and Firefox drop support for servers using weak Diffie-Hellman public keys]]'''<br />
</div><br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Download&diff=9463Download2022-05-11T05:20:32Z<p>Ulde: /* HSYCO 3.7 */</p>
<hr />
<div>[[Category:Downloads]]<br />
<br />
This page contains the downloadable files of all recent versions of HSYCO, as well as files and documentation of some older versions. If you are looking for files and documentation of versions not listed here, please contact us requesting the files you need.<br />
<br />
==HSYCO 3.7==<br />
<br />
===HSYCO 3.7.1===<br />
Release date: May 11, 2022<br />
<br />
[http://wiki.hsyco.com/uploads/3.7.1/hsyco.jar-3.7.1.zip HSYCO 3.7.1 Jar file]<br />
<br />
===HSYCO 3.7.0===<br />
Release date: October 21, 2020<br />
<br />
[http://wiki.hsyco.com/uploads/3.7.0/hsyco.jar-3.7.0.zip HSYCO 3.7.0 Jar file]<br />
<br />
==HSYCO 3.6==<br />
<br />
===HSYCO 3.6.1===<br />
Release date: March 1, 2018<br />
<br />
[http://wiki.hsyco.com/uploads/3.6.1/hsyco.jar-3.6.1.zip HSYCO 3.6.1 Jar file]<br />
<br />
===HSYCO 3.6.0===<br />
Release date: November 28, 2017<br />
<br />
[http://wiki.hsyco.com/uploads/3.6.0/hsyco.jar-3.6.0.zip HSYCO 3.6.0 Jar file]<br />
<br />
==HSYCO 3.5==<br />
<br />
===HSYCO 3.5.1===<br />
Release date: April 15, 2016<br />
<br />
[http://wiki.hsyco.com/uploads/3.5.1/hsyco.jar-3.5.1.zip HSYCO 3.5.1 Jar file]<br />
<br />
===HSYCO 3.5.0===<br />
Release date: October 15, 2015<br />
<br />
[http://wiki.hsyco.com/uploads/3.5.0/hsyco.jar-3.5.0.zip HSYCO 3.5.0 Jar file]<br />
<br />
==HSYCO 3.4==<br />
===HSYCO 3.4.0===<br />
Release date: Dec 22, 2014<br />
<br />
[http://wiki.hsyco.com/uploads/3.4.0/hsyco.jar-3.4.0.zip HSYCO 3.4.0 Jar file]<br />
<br />
==HSYCO 3.3==<br />
===HSYCO 3.3.0===<br />
Release date: Dec 23, 2013<br />
<br />
[http://wiki.hsyco.com/uploads/3.3.0/hsyco.jar-3.3.0.zip HSYCO 3.3.0 Jar file]<br />
<br />
==HSYCO 3.2==<br />
===HSYCO 3.2.3===<br />
Release date: Sep 10, 2013<br />
<br />
[http://wiki.hsyco.com/uploads/3.2.3/hsyco.jar-3.2.3.zip HSYCO 3.2.3 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/3.2.3/dev-3.2.3.zip HSYCO 3.2.3 Configuration and Programming Handbook]<br />
<br />
==HSYCO 3.1==<br />
===HSYCO 3.1.2===<br />
Release date: Nov 19, 2012<br />
<br />
[http://wiki.hsyco.com/uploads/3.1.2/hsyco.jar-3.1.2.zip HSYCO 3.1.2 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/3.1.2/dev-3.1.2.zip HSYCO 3.1.2 Configuration and Programming Handbook]<br />
<br />
==HSYCO 3.0==<br />
===HSYCO 3.0.3===<br />
Release date: Apr 24, 2012<br />
<br />
[http://wiki.hsyco.com/uploads/3.0.3/hsyco.jar-3.0.3.zip HSYCO 3.0.3 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/3.0.3/dev-3.0.3.zip HSYCO 3.0.3 Configuration and Programming Handbook]<br />
<br />
==HSYCO 2.10==<br />
===HSYCO 2.10.6===<br />
Release date: Apr 27, 2012<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.6/hsyco.jar-2.10.6.zip HSYCO 2.10.6 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.6/dev-2.10.6.zip HSYCO 2.10.6 Configuration and Programming Handbook]<br />
<br />
===HSYCO 2.10.5===<br />
Release date: Feb 10, 2012<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.5/hsyco.jar-2.10.5.zip HSYCO 2.10.5 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.5/dev-2.10.5.zip HSYCO 2.10.5 Configuration and Programming Handbook]<br />
<br />
===HSYCO 2.10.0===<br />
Release date: Sep 16, 2011<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.0/hsyco.jar-2.10.0.zip HSYCO 2.10.0 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.0/dev-2.10.0.zip HSYCO 2.10.0 Configuration and Programming Handbook]</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Release_Notes_3.7.0&diff=9388Release Notes 3.7.02020-10-22T13:42:01Z<p>Ulde: /* Server Updates */</p>
<hr />
<div><br />
[[Category: Release Notes]]<br />
<br />
== Server Updates ==<br />
*Aritech Comfort CSx75 I/O Server: added possibility to specify zone names<br />
*ARTECOOC I/O Server:<br />
**verbose log output of XML content posted to server and return data<br />
**session id support<br />
*AVIGILON I/O Server: new I/O Server for the Avigilon Control Center 7<br />
*CONTATTO I/O Server:<br />
**support of MODRHT<br />
**support of MODAM2<br />
**support of MODIGLASS, MODIGLASS3<br />
**support of MODLC firmware version 3.2<br />
**support of MODDALI firmware version 6.x<br />
**support of MCP counters<br />
**bus and modules fault detection<br />
*Dea Xensity I/O Server: new I/O Server for the Dea Xensity indoor shock detectors<br />
*DOMINO I/O Server:<br />
**support of DFANA-M<br />
**support of DFDALI64<br />
**support of DFDIM<br />
**support of DFLS smart mode<br />
**support of DF4RI/DF4RIR virtual outputs<br />
**support of DF8RIT configuration with temperature input address enabled and temperature control disabled<br />
**support of position information and commands for DFTP, DFTP/I<br />
**support of DFCP counters<br />
**bus and modules fault detection<br />
**high availability support for redundant DFH installations<br />
*DUELUX I/O Server: new I/O Server for the Duemmegi DUELUX DLCP DALI-2 system controller<br />
*DUMMY I/O Server:<br />
**new "commandstate" option<br />
**new HTTP API: data points can now be set and read remotely with the /x/httpcall HTTP API<br />
**default number of lights, dimmers, automation is 0 (zero)<br />
*ELMO I/O Server: added support for Pregio, Vidomo (Villeggio series), Proxima and Titania panels<br />
*ESC/VP (EPSON) I/O Server:<br />
**improved protocol compatibility<br />
**added support for "middle" luminance level<br />
*Google Calendar I/O Server:<br />
**added capability of creating events<br />
**added "<cal_name>.json" and "<cal_name>.pre.json" datapoints<br />
*KILSEN I/O Server: new I/O Server for the KILSEN fire alarm panels<br />
*KNX I/O Server:<br />
**added support for DPT 29<br />
**added support for ETS5 export file<br />
**added "initreadinterval" I/O Server option<br />
**minor connection handling improvements<br />
*KSENIA I/O Server: new I/O Server for the KSENIA lares security panels<br />
*IFTTT I/O Server: new I/O Server for the IFTTT service<br />
*IONO I/O Server:<br />
**the IONO I/O Server is now "free". Using it doesn't decrease the number of available I/O servers<br />
**"minvariation" option now also applies to polling mode<br />
*IONO PI I/O Server:<br />
**added support for iono pi driver v1.3.0 and "wiegandbits" option<br />
**added support for local Iono Pi direct access<br />
*IONO PI Max I/O Server: new I/O Server for Sfera Labs Iono Pi Max<br />
*LoRaWAN I/O Server: new I/O Server for LoRaWAN Network and Application servers implementation<br />
*MasterBus I/O Server: new I/O Server for Mastervolt's MasterBus<br />
*Modbus I/O Server:<br />
**new "tcpmodbuseventunitid" option. When the Modbus TCP gateway option is enabled, setting tcpmodbuseventunitid to a Unit Id value (0 to 255) will redirect all TCP requests to that Unit Id to the ModbusEvent() callback instead of the Modbus RTU serial bus<br />
**high-availability: when "shutdown when inactive" is true and the HSYCO Server is inactive, all Modbus calls are affectively blocked, and return null. The TCP gateway is also blocked<br />
*MPOWER I/O Server: new I/O Server for the Ubiquity mFi mPower controllable power outlets<br />
*MQTTBROKER and MQTTCLIENT I/O Servers: new I/O servers add support for the MQTT protocol, client and broker<br />
*MyHome I/O Server: added support for HMAC authentication (for MyHome Server 1 and other recent OpenWebNet gateways)<br />
*NetworX I/O Server: added possibility to specify zone names<br />
*Paradox I/O Server: new "log0" data point<br />
*Philips Hue I/O Server: added support for Hue White devices<br />
*Protege I/O Server: new I/O Server for the ICT ProtegeGX security panel<br />
*Sonos I/O Server:<br />
**added support for SONOS firmware version 9<br />
**added datapoint "<player>.queue = <n>"<br />
**player state is now restored after a track is played via "<player>.play = <uri>" or via public announcement<br />
*SSH I/O Server:<br />
**the SSH I/O Server is now "free". Using it doesn't decrease the number of available I/O servers<br />
**new exec.<timeout> data point. Sets the command execution timeout in seconds; defaults to 30<br />
**new connection = close command: closes the SSH connection<br />
**new user = <user name> command; overrides the user configuration parameter<br />
**new password = <user password> command; overrides the password configuration parameter<br />
**new stdout=line option<br />
*Strato I/O Server:<br />
**added support for Strato Pi CAN and Strato Pi CM Duo<br />
**new cpu.temperature data point<br />
*System I/O Server: new data points:<br />
**cpu.model<br />
**cpu.revision<br />
**database.backup.time<br />
**database.backup.elapsed<br />
**database.backup.consolidation.time<br />
**database.backup.consolidation.elapsed<br />
**database.backup.consolidation.status<br />
**database.defrag.time<br />
**database.defrag.elapsed<br />
**database.update.elapsed<br />
**hsyco.version<br />
**java.version<br />
**os.version<br />
*Tecnoalarm I/O Server: added data point "log0"<br />
*Telegram I/O Server: camera images and generic image files can now be sent via Telegram messages<br />
*WOLF8ACCESS I/O Server: new I/O Server for the Wolf Safety "8 ACCESS" access control system<br />
*WXONLINE I/O Server:<br />
**data source changed from Yahoo to Open Weather Map<br />
**increased number of forcasted days from 2 to 5<br />
**location can be set to latitude and longitude, as well as with the location id<br />
*YAMAHAEC I/O Server: new I/O Server for the Yamaha Extended Control communication protocol<br />
**location can be set to latitude and longitude, as well as with the location id<br />
*new embedded Natural Language Processor to support speech and free format text commands<br />
*Cameras: cameras with static image sources are now supported. If Camera.<id>.Type is set to "static", a single HTTP request is sent to acquire the image when a CAMERAREC action is executed. The live camerapanel display will not trigger HTTP requests to the source, but show the last recorded image. Events are grouped per day. For static cameras only, a variable name (starting with $) can be set in the configuration instead of the URL in order to allow dynamic URLs<br />
*Data loggers: new HourConsolidationFactor option for data loggers. Splits hourly consolidated data in multiple sub-intervals (e.g. HourConsolidationFactor = 4 leaves data grouped at minutes 0, 15, 30, 45 after hour consolidation)<br />
*Program timers: if the program timer id starts with $, then the server will also automatically set a variable, with a name equal to the program timer's id, to the remaining number of seconds. Note that the variable is not guaranteed to be updated at every second, as some updates may be skipped due to timing constraints.<br />
*Communication ports, serial gateways configuration: it is now possible to define a custom read timeout to override the 2 seconds default. Set using CommPort.<id>.Params = <timeoutmillis> in hsyco.ini<br />
*Access control: new trustedUsers option: comma separated list of user IDs that are always considered trusted, even when connected from outside of the trusted network. Trusted users connecting to HSYCO are subject to the time-out defined in KeysTrustedValidityHours<br />
*Location Services: improved compatibility with Ubiquiti UniFi access points<br />
*New Database options for scheduled data structure optimization: DatabaseCompactDay, DatabaseCompactHour, DatabaseCompactMinute, DatabaseCompactEnable<br />
*New Database option for backup consolidation (integrity verification and compression), with automatic recovery: DatabaseBackupConsolidation<br />
*The Datalogger import API (csvread and cvsreadover) can now also receive a CSV string directly instead of a file path<br />
*when TimeAutoUpdate is enabled, NTP synchronization is performed every hour (it was once a day, at 00:30 local time, in previous versions)<br />
*on Linux systems with the Intel U1900 CPU, HSYCO will check the system clock source at startup, and set it to "acpi_pm" if different<br />
*High Availability:<br />
**improved client handover between primary and secondary servers<br />
**new hsyco.ini synchronization feature: hsyco.slavediff.ini file contains changes to hsyco.ini to be applied to the slave version of hsyco.ini. It can contain new properties, existing properties with different values, or existing properties with no value, to remove properties from the master's hsyco.ini file. The hsyco.slavediff.ini should be updated from the master only, even if it is only used by the slave<br />
**new haDatabaseSlaveSync hsyco.ini property: haDatabaseSlaveSync = true (defaults to false) restores the slave database, restarting HSYCO, when a new database backup is synced from the master. DatabaseBackupCosolidation must be true to enable database synchronization<br />
<br />
== EVENTS ==<br />
*new LOGIN <userid> transient event<br />
*new LOGOUT <userid> transient event<br />
*new LOCATIONBEACON event keyword. Supports "LOCATIONBEACON userid = zone" and "LOCATIONBEACON zoneid" event conditions<br />
*new NLP action keyword<br />
*MAIL action: you can now optionally specify the number of frames back from the defined number of seconds since last recording. The new format is: “cam:cameraname[:seconds_back[:frames_back]]”<br />
*new format modifiers for $SUNRISE$ and $SUNSSET$ predefined variables, $SUNRISE:HMS$ and $SUNSSET:HMS$<br />
*AUDIO action: new audio destination format, web@<channel>. <channel> can be a project name or an arbitrary name assigned to an audio channel set using the "audiochannel" project attribute<br />
<br />
== Java API ==<br />
*new loginEvent(String address, String session, String userid) callback<br />
*new logoutEvent(String address, String session, String userid, boolean lock) callback<br />
*new LocationBeaconEvent(String session, String address, String userid, String zone, String distance) callback<br />
*new nlp(String text) command<br />
*new uiLink(String source, String target) command<br />
*sendMail() command: you can now optionally specify the number of frames back from the defined number of seconds since last recording. The new format is: “cam:cameraname[:seconds_back[:frames_back]]”<br />
*ioGet(String id): ioGet("*") returns the ids of all data points in a comma-separated list<br />
*varGet(String name): varGet("*") returns the names of all variables in a comma-separated list. Variable names are upper case<br />
*Modbus: all commands now also accept <ip>:<port number> to connect to Modbus TCP servers with a non-standard port number<br />
*audioPlay() command: new audio destination format, web@<channel>. <channel> can be a project name or an arbitrary name assigned to an audio channel set using the "audiochannel" project attribute<br />
<br />
== JavaScript API ==<br />
*new loginEvent(address, session, userid) callback<br />
*new logoutEvent(address, session, userid, lock) callback<br />
*new LocationBeaconEvent(session, address, userid, zone, distance) callback function<br />
*new nlp(text) command<br />
*new uiLink(source, target) command<br />
*sendMail() command: you can now optionally specify the number of frames back from the defind number of seconds since last recording. The new format is: “cam:cameraname[:seconds_back[:frames_back]]”<br />
*ioGet(id): ioGet("*") returns the ids of all data points in a comma-separated list<br />
*varGet(name): varGet("*") returns the names of all variables in a comma-separated list. Variable names are upper case<br />
*Modbus: all commands now also accept <ip>:<port number> to connect to Modbus TCP servers with a non-standard port number<br />
*audioPlayFile() and audioPlayText() commands: new audio destination format, web@<channel>. <channel> can be a project name or an arbitrary name assigned to an audio channel set using the "audiochannel" project attribute<br />
<br />
== GUI Updates ==<br />
*new "html" object<br />
*new "shape" object<br />
*UI objects redirect variables support<br />
*new page and popup "focus" attribute. Specifying an id of an object contained in the page, it will gain focus immediately if visible, and every time the page is opened<br />
*button, 3button, buttonicon, buttonimage now have an id and uiset attributes: pos, visible, label, blink, opacity, rotation, confirm<br />
*new "confirm” attribute for user and button ui objects. If “true” user has to press a second time to send the command<br />
*fullscreen support for datalogger and camerapanel objects:<br />
**new "fullwindow" url query option<br />
**fullwindow=true|false project's UI attribute: set to true to expand inside the browser's window instead of actually going fullscreen<br />
**pinch to zoom on camerapanel<br />
*datalogger object:<br />
**multi-year view in browser mode<br />
**click the values legends to hide/unhide the corresponding graph<br />
**set download="true" enable local download of datalogger browser data in CSV format<br />
**new "csvseparator" attribute<br />
*scale project attribute and URL option keyword: new "auto" and "fit" options. When scale=auto the user interface is automatically expanded to fill the available browser area. When scale=fit, the user interface is expanded as with auto, but also reduced if the available browser area is smaller than the original project's size. The scale attribute can be set as a static project's directive, a URL keyword, or dynamically with UISET<br />
*new "audiochannel" project attribute<br />
*gohome=N project attribute and URL option keyword: after N seconds of inactivity, go to the menu page, or the page set with the page=<page name> URL option<br />
*PIN and PUK can now be pasted from the clipboard<br />
*camerapanel object:<br />
**added support for for pinch to zoom on camerapanel object when in fullscreen mode in the iOS and Android apps<br />
**single frame email replaced with local download<br />
**redesigned download popup and app download support<br />
**reduced height of playback timeline clickable area<br />
*input object: new cssstyle attribute<br />
*link, imagelink objects:<br />
**the link attribute can be dynamically set with UISET<br />
**link objects now can receive focus<br />
*scheduler object: new groups attribute allows changing the list of schedule groups names via UISET<br />
*video object: new "controls" attribute<br />
*other minor graphical changes to the standard skins<br />
*in previous versions, the automatic web UI reload was triggered by changes in any file under the www directory or on HSYCO startup. Starting from this version, HSYCO startup will not trigger the reload if no www files are changed. Reload will also occur if www files under the plugins directory are changed<br />
<br />
== Manager ==<br />
*new LoRaWAN configuration utility<br />
*new SSH tunnel configuration utility<br />
*added support for iBeacon configuration in Location Services Settings<br />
*Log Viewer filter now accepts "strings delimited by quotes", single quotes, "escaped\"quotes\""<br />
*Project Editor:<br />
**new object alignment tools<br />
**project’s scale parameter now specified through a select field<br />
**new "go to page" button on link objects, and other usability improvements<br />
**new QR Code tool<br />
*Modbus Utility:<br />
**new skip on error interval option: skip reading for the specified amount of time after an error<br />
**new error tolerance option: number of consecutive errors accepted before the error data point is triggered<br />
**improved user interface<br />
*other usability improvements, including resizable attributes input fields, and copy to clipboard for Log Viewer and Status Browser<br />
<br />
== Bug Fixes ==<br />
*improved compatibility with Debian 9 (Stretch) systems:<br />
**high availability active IP hand-over<br />
**LAN IP address configuration change: old address remained active until reboot<br />
**system clock synchronization and network time update support<br />
*improved serial port reliability on Linux (x86) systems<br />
*fixed a bug that could cause the corruption of cameras recording indexes<br />
*improved handling of cameras connections errors<br />
*when the Java runtime version is >= 1.7 symbolic links under the HSYCO root are now handled as normal, valid paths<br />
*High Availability:<br />
**sync of zero-length files generated an exception message<br />
**hsyco.jar could fail to synchronize on slave if listed in the AutoKillFiles configuration parameter on the slave<br />
*Contatto I/O Server: fixes to the MODDALI ballast 1 status data point<br />
*Domino I/O Server: "modulefault" data point of individual modules not working with DFH gateways<br />
*Cradlepoint I/O Server: fixed error parsing data points returning long values<br />
*HSYCO Remote I/O Server:<br />
**data points with the '*' character in the value string couldn't be written to the remote server<br />
**the I/O Server could time out during initialization on a very large local database<br />
*IONO I/O Server: port configuration option was ignored<br />
*Modbus I/O Server: fixed a bug causing conversion errors when reading 4 consecutive registers with "longx" or "ulongx" data types<br />
*Paradox I/O Server: minor fixes<br />
*SMTPSERVER I/O Server: fixed a bug that caused messages without a "Content-type" header in the body to be ignored<br />
*Tecnoalarm I/O Server: pass phrases with upper case characters were not supported<br />
*Tecnofire I/O Server:<br />
**log and lastlog UISet ID fixed<br />
**extended communication wait time after read errors<br />
*Telegram I/O Server: a connection error during the I/O server startup sequence could cause it to wait indefinitely and never connect<br />
*API:<br />
**fixed null return value in the following JavaScript command functions: ioGet, readComm, slimCommand, uiGet, uiSessionGet, urlGet, urlPost<br />
**fixed bug in LocationEvent(mac, ip, zoneId) JavaScript callback function<br />
**fixed return value in UserCommand Javascript callback function (index.js)<br />
*GUI:<br />
**menu or pages gestures and scope declarations could propagate to all pages following the declaration in index.hsm<br />
**chart object: valuerange set using a "." separator caused a client-side JavaScript error<br />
**all link objects: fixed relative URL opening in new tab<br />
**linkmini, linkmicro objects: fixed dynamic label attributes<br />
**link object to external URLs not working correctly on iOS and Android app<br />
**panel object: setting height via UISET did not work<br />
**rgb object: pressing off could fail to send the off command in some circumstances<br />
**scheduler object: group names incorrectly set to lower case on HSYCO restart or scheduler.ini reload<br />
**minor fixes to camera objects<br />
*Manager:<br />
**line object didn’t move correctly pressing the arrow keys<br />
**project's page copy & paste not working<br />
**text editor did not recognize event files in plugins directories</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=HSYCO&diff=9387HSYCO2020-10-21T14:32:43Z<p>Ulde: </p>
<hr />
<div>__NOTITLE__<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="100%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle welcome">Welcome to the HSYCO Wiki 3.7</div><br />
<div class="mainpageContent"><br />
'''HSYCO''' is an innovative Java-based software framework for home and building automation applications.<br />
<br />
It is highly scalable, portable, secure, reliable and customizable.<br />
HSYCO combines an efficient HTML5 GUI, with web-based design tools, and an extensive Java and JavaScript server API for the automation and control logic.<br />
<br />
Compared to legacy building automation solutions, it offers a state-of-the-art architecture that is fully based on leading modern standards, like HTML5, CSS3, JavaScript and Java.<br />
<br />
<br />
This wiki contains all relevant configuration and development information of the latest version of HSYCO.<br />
<br />
The documentation of previous versions is available in the [[Download]] page.<br />
</div><br />
<div class="mainpageLinks"><br />
'''[[Download]] | [[About HSYCO]] | [[Products]] | [[Support]] | [[FAQ]]'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Installation and Configuration</div><br />
<div class="mainpageContent"><br />
[[File:Main Page System Administrator.png|x80px|center|link=]]<br />
Install and configure HSYCO Server<br />
*'''[[Installation Guide]]'''<br />
*'''[[Settings|Configuration Guide]]'''<br />
*'''[[HSYCO_App|HSYCO App for iOS and Android]]'''<br />
*'''[[System Architecture]]'''<br />
</div><br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Development</div><br />
<div class="mainpageContent"><br />
[[File:Main Page Development.png|x80px|center|link=]]<br />
Design your interfaces and develop your applications<br />
*'''[[User Interface|User Interface Design]]'''<br />
*'''[[Programming]]'''<br />
*'''[[Advanced Programming]]'''<br />
</div><br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Integration</div><br />
<div class="mainpageContent"><br />
[[File:Main Page Integration.png|x80px|center|link=]]<br />
How to interface external systems<br />
*'''[[Introduction to I/O Servers]]'''<br />
*'''[[I/O Servers|I/O Servers Application Notes]]'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Versions</div><br />
<div class="mainpageContent"><br />
*The latest stable release is 3.7.0<br />
*The latest release of the previous version is 3.6.1<br />
<br />
<br />
'''[[Release_Notes_3.7.0|3.7.0 Release Notes]]'''<br />
<br />
'''[[Release_Notes_3.6.1|3.6.1 Release Notes]]''' and '''[http://wiki.hsyco.com/3.6.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.6.0|3.6.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.6.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.5.1|3.5.1 Release Notes]]''' and '''[http://wiki.hsyco.com/3.5.1 Documentation]'''<br />
<br />
'''[[Release_Notes_3.5.0|3.5.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.5.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.4.0|3.4.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.4.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.3.0|3.3.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.3.0 Documentation]'''<br />
<br />
<br />
<br />
<br />
'''Visit the [[Download]] page to download all current and past versions of the HSYCO server software.'''<br />
</div><br />
| valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">News</div><br />
<div class="mainpageContent"><br />
*2020/10/21<br />
**HSYCO 3.7.0 release is available for download<br />
*2019/08/08<br />
**HSYCO 3.7.0 B0129 BETA is available for download. All users are advised to upgrade to build 0129<br />
*2019/02/01<br />
**HSYCO 3.7.0 B0128 BETA is available for download. This build fixes a bug introduced with previous beta build, that could cause an abnormal number of HTTP requests to the weather service provider. All users are advised to upgrade to build 0128<br />
*2019/01/15<br />
**HSYCO 3.7.0 B0127 BETA is available for download<br />
*2018/03/01<br />
**HSYCO 3.6.1 release is available for download<br />
*2017/11/28<br />
**HSYCO 3.6.0 release is available for download<br />
*2016/04/15<br />
**HSYCO 3.5.1 release is available for download<br />
*2016/1/26<br />
**HSYCO 3.5.1 B0122 BETA is available for download<br />
*2015/10/15<br />
**HSYCO 3.5.0 release is available for download<br />
*2015/9/26<br />
**HSYCO Remote App for iOS and Apple Watch is now available on the [https://itunes.apple.com/app/hsyco/id1038105480 Apple App Store]. Version 1.0.1 with improved support for iOS 9 coming soon<br />
*2015/7/31<br />
**HSYCO 3.5.0 B0120 BETA is available for download<br />
*2015/5/18<br />
**HSYCO 3.5.0 B0119 BETA is available for download<br />
*2015/4/24<br />
**HSYCO 3.5.0 BETA documentation is on-line<br />
*2014/12/22<br />
**HSYCO 3.4.0 release is available for download<br />
*2014/10/24<br />
**Due to the large number of enhancements (not only bug fixes) in the current beta release, formerly known as 3.3.1, we are now promoting it to 3.4.0. There will be no official release of 3.3.1, and all changes are merged in the upcoming 3.4.0 release<br />
*2014/8/7<br />
**HSYCO 3.3.1 B0115 BETA is now available for download<br />
*2014/6/4<br />
**HSYCO 3.3.1 B0114 BETA is available for download<br />
*2014/3/25<br />
**HSYCO 3.3.0 release is available for download<br />
*2014/2/24<br />
**HSYCO 3.3.0 B0112 BETA is available for download<br />
*2013/12/23<br />
**HSYCO 3.3.0 B0109 BETA is available for download<br />
*2013/9/10<br />
**HSYCO 3.2.3 release is available for download<br />
*2013/6/12<br />
**HSYCO 3.2.2 release is available for download<br />
*2013/4/19<br />
**HSYCO 3.2.1 release is available for download<br />
<br />
<br />
'''Older news have been removed from this site. If you need specific information about old releases, please contact us.'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="100%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Service Bulletins</div><br />
<div class="mainpageContent"><br />
*2020/2/5: '''[[Service_Bulletin_20200205_Telegram_BOT|Telegram now requires the TLSv1.2 cryptographic protocol, breaking compatibility on Java 6 and Java 7 virtual machines]]'''<br />
*2019/1/3: '''[[Service_Bulletin_20190103_Yahoo_Weather_API_EOL|Yahoo drops supports for its weather API used in the WXOnline HSYCO I/O Server]]'''<br />
*2016/3/15: '''[[Service_Bullettin_20160315_Yahoo_Weather_API|Yahoo drops supports for previous version of its weather API and introduces new API]]'''<br />
*2015/9/10: '''[[Service_Bullettin_20150911_Weak_DH_HTTPS_Server_Keys|Chrome and Firefox drop support for servers using weak Diffie-Hellman public keys]]'''<br />
</div><br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=HSYCO&diff=9386HSYCO2020-10-21T14:31:48Z<p>Ulde: </p>
<hr />
<div>__NOTITLE__<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="100%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle welcome">Welcome to the HSYCO Wiki 3.7</div><br />
<div class="mainpageContent"><br />
'''HSYCO''' is an innovative Java-based software framework for home and building automation applications.<br />
<br />
It is highly scalable, portable, secure, reliable and customizable.<br />
HSYCO combines an efficient HTML5 GUI, with web-based design tools, and an extensive Java and JavaScript server API for the automation and control logic.<br />
<br />
Compared to legacy building automation solutions, it offers a state-of-the-art architecture that is fully based on leading modern standards, like HTML5, CSS3, JavaScript and Java.<br />
<br />
<br />
This wiki contains all relevant configuration and development information of the latest version of HSYCO.<br />
<br />
The documentation of previous versions is available in the [[Download]] page.<br />
</div><br />
<div class="mainpageLinks"><br />
'''[[Download]] | [[About HSYCO]] | [[Products]] | [[Support]] | [[FAQ]]'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Installation and Configuration</div><br />
<div class="mainpageContent"><br />
[[File:Main Page System Administrator.png|x80px|center|link=]]<br />
Install and configure HSYCO Server<br />
*'''[[Installation Guide]]'''<br />
*'''[[Settings|Configuration Guide]]'''<br />
*'''[[HSYCO_App|HSYCO App for iOS and Android]]'''<br />
*'''[[System Architecture]]'''<br />
</div><br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Development</div><br />
<div class="mainpageContent"><br />
[[File:Main Page Development.png|x80px|center|link=]]<br />
Design your interfaces and develop your applications<br />
*'''[[User Interface|User Interface Design]]'''<br />
*'''[[Programming]]'''<br />
*'''[[Advanced Programming]]'''<br />
</div><br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Integration</div><br />
<div class="mainpageContent"><br />
[[File:Main Page Integration.png|x80px|center|link=]]<br />
How to interface external systems<br />
*'''[[Introduction to I/O Servers]]'''<br />
*'''[[I/O Servers|I/O Servers Application Notes]]'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="33%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Versions</div><br />
<div class="mainpageContent"><br />
*The latest beta release is 3.7.0 B0129<br />
*The latest stable release is 3.6.1<br />
*The latest release of the previous version is 3.5.1<br />
<br />
<br />
'''[[Release_Notes_3.7.0|3.7.0 Release Notes]]'''<br />
<br />
'''[[Release_Notes_3.6.1|3.6.1 Release Notes]]''' and '''[http://wiki.hsyco.com/3.6.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.6.0|3.6.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.6.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.5.1|3.5.1 Release Notes]]''' and '''[http://wiki.hsyco.com/3.5.1 Documentation]'''<br />
<br />
'''[[Release_Notes_3.5.0|3.5.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.5.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.4.0|3.4.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.4.0 Documentation]'''<br />
<br />
'''[[Release_Notes_3.3.0|3.3.0 Release Notes]]''' and '''[http://wiki.hsyco.com/3.3.0 Documentation]'''<br />
<br />
<br />
<br />
<br />
'''Visit the [[Download]] page to download all current and past versions of the HSYCO server software.'''<br />
</div><br />
| valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">News</div><br />
<div class="mainpageContent"><br />
*2020/10/21<br />
**HSYCO 3.7.0 release is available for download<br />
*2019/08/08<br />
**HSYCO 3.7.0 B0129 BETA is available for download. All users are advised to upgrade to build 0129<br />
*2019/02/01<br />
**HSYCO 3.7.0 B0128 BETA is available for download. This build fixes a bug introduced with previous beta build, that could cause an abnormal number of HTTP requests to the weather service provider. All users are advised to upgrade to build 0128<br />
*2019/01/15<br />
**HSYCO 3.7.0 B0127 BETA is available for download<br />
*2018/03/01<br />
**HSYCO 3.6.1 release is available for download<br />
*2017/11/28<br />
**HSYCO 3.6.0 release is available for download<br />
*2016/04/15<br />
**HSYCO 3.5.1 release is available for download<br />
*2016/1/26<br />
**HSYCO 3.5.1 B0122 BETA is available for download<br />
*2015/10/15<br />
**HSYCO 3.5.0 release is available for download<br />
*2015/9/26<br />
**HSYCO Remote App for iOS and Apple Watch is now available on the [https://itunes.apple.com/app/hsyco/id1038105480 Apple App Store]. Version 1.0.1 with improved support for iOS 9 coming soon<br />
*2015/7/31<br />
**HSYCO 3.5.0 B0120 BETA is available for download<br />
*2015/5/18<br />
**HSYCO 3.5.0 B0119 BETA is available for download<br />
*2015/4/24<br />
**HSYCO 3.5.0 BETA documentation is on-line<br />
*2014/12/22<br />
**HSYCO 3.4.0 release is available for download<br />
*2014/10/24<br />
**Due to the large number of enhancements (not only bug fixes) in the current beta release, formerly known as 3.3.1, we are now promoting it to 3.4.0. There will be no official release of 3.3.1, and all changes are merged in the upcoming 3.4.0 release<br />
*2014/8/7<br />
**HSYCO 3.3.1 B0115 BETA is now available for download<br />
*2014/6/4<br />
**HSYCO 3.3.1 B0114 BETA is available for download<br />
*2014/3/25<br />
**HSYCO 3.3.0 release is available for download<br />
*2014/2/24<br />
**HSYCO 3.3.0 B0112 BETA is available for download<br />
*2013/12/23<br />
**HSYCO 3.3.0 B0109 BETA is available for download<br />
*2013/9/10<br />
**HSYCO 3.2.3 release is available for download<br />
*2013/6/12<br />
**HSYCO 3.2.2 release is available for download<br />
*2013/4/19<br />
**HSYCO 3.2.1 release is available for download<br />
<br />
<br />
'''Older news have been removed from this site. If you need specific information about old releases, please contact us.'''<br />
</div><br />
|}<br />
<br />
{| role="presentation" style="border:0; margin: 0;" width="100%" cellspacing="10"<br />
| width="100%" valign="top" class="mainpageBox" |<br />
<div class="mainpageTitle">Service Bulletins</div><br />
<div class="mainpageContent"><br />
*2020/2/5: '''[[Service_Bulletin_20200205_Telegram_BOT|Telegram now requires the TLSv1.2 cryptographic protocol, breaking compatibility on Java 6 and Java 7 virtual machines]]'''<br />
*2019/1/3: '''[[Service_Bulletin_20190103_Yahoo_Weather_API_EOL|Yahoo drops supports for its weather API used in the WXOnline HSYCO I/O Server]]'''<br />
*2016/3/15: '''[[Service_Bullettin_20160315_Yahoo_Weather_API|Yahoo drops supports for previous version of its weather API and introduces new API]]'''<br />
*2015/9/10: '''[[Service_Bullettin_20150911_Weak_DH_HTTPS_Server_Keys|Chrome and Firefox drop support for servers using weak Diffie-Hellman public keys]]'''<br />
</div><br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Download&diff=9385Download2020-10-21T14:28:42Z<p>Ulde: /* HSYCO 3.7.0 */</p>
<hr />
<div>[[Category:Downloads]]<br />
<br />
This page contains the downloadable files of all recent versions of HSYCO, as well as files and documentation of some older versions. If you are looking for files and documentation of versions not listed here, please contact us requesting the files you need.<br />
<br />
==HSYCO 3.7==<br />
<br />
===HSYCO 3.7.0===<br />
Release date: October 21, 2020<br />
<br />
[http://wiki.hsyco.com/uploads/3.7.0/hsyco.jar-3.7.0.zip HSYCO 3.7.0 Jar file]<br />
<br />
==HSYCO 3.6==<br />
<br />
===HSYCO 3.6.1===<br />
Release date: March 1, 2018<br />
<br />
[http://wiki.hsyco.com/uploads/3.6.1/hsyco.jar-3.6.1.zip HSYCO 3.6.1 Jar file]<br />
<br />
===HSYCO 3.6.0===<br />
Release date: November 28, 2017<br />
<br />
[http://wiki.hsyco.com/uploads/3.6.0/hsyco.jar-3.6.0.zip HSYCO 3.6.0 Jar file]<br />
<br />
==HSYCO 3.5==<br />
<br />
===HSYCO 3.5.1===<br />
Release date: April 15, 2016<br />
<br />
[http://wiki.hsyco.com/uploads/3.5.1/hsyco.jar-3.5.1.zip HSYCO 3.5.1 Jar file]<br />
<br />
===HSYCO 3.5.0===<br />
Release date: October 15, 2015<br />
<br />
[http://wiki.hsyco.com/uploads/3.5.0/hsyco.jar-3.5.0.zip HSYCO 3.5.0 Jar file]<br />
<br />
==HSYCO 3.4==<br />
===HSYCO 3.4.0===<br />
Release date: Dec 22, 2014<br />
<br />
[http://wiki.hsyco.com/uploads/3.4.0/hsyco.jar-3.4.0.zip HSYCO 3.4.0 Jar file]<br />
<br />
==HSYCO 3.3==<br />
===HSYCO 3.3.0===<br />
Release date: Dec 23, 2013<br />
<br />
[http://wiki.hsyco.com/uploads/3.3.0/hsyco.jar-3.3.0.zip HSYCO 3.3.0 Jar file]<br />
<br />
==HSYCO 3.2==<br />
===HSYCO 3.2.3===<br />
Release date: Sep 10, 2013<br />
<br />
[http://wiki.hsyco.com/uploads/3.2.3/hsyco.jar-3.2.3.zip HSYCO 3.2.3 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/3.2.3/dev-3.2.3.zip HSYCO 3.2.3 Configuration and Programming Handbook]<br />
<br />
==HSYCO 3.1==<br />
===HSYCO 3.1.2===<br />
Release date: Nov 19, 2012<br />
<br />
[http://wiki.hsyco.com/uploads/3.1.2/hsyco.jar-3.1.2.zip HSYCO 3.1.2 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/3.1.2/dev-3.1.2.zip HSYCO 3.1.2 Configuration and Programming Handbook]<br />
<br />
==HSYCO 3.0==<br />
===HSYCO 3.0.3===<br />
Release date: Apr 24, 2012<br />
<br />
[http://wiki.hsyco.com/uploads/3.0.3/hsyco.jar-3.0.3.zip HSYCO 3.0.3 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/3.0.3/dev-3.0.3.zip HSYCO 3.0.3 Configuration and Programming Handbook]<br />
<br />
==HSYCO 2.10==<br />
===HSYCO 2.10.6===<br />
Release date: Apr 27, 2012<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.6/hsyco.jar-2.10.6.zip HSYCO 2.10.6 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.6/dev-2.10.6.zip HSYCO 2.10.6 Configuration and Programming Handbook]<br />
<br />
===HSYCO 2.10.5===<br />
Release date: Feb 10, 2012<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.5/hsyco.jar-2.10.5.zip HSYCO 2.10.5 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.5/dev-2.10.5.zip HSYCO 2.10.5 Configuration and Programming Handbook]<br />
<br />
===HSYCO 2.10.0===<br />
Release date: Sep 16, 2011<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.0/hsyco.jar-2.10.0.zip HSYCO 2.10.0 Jar file]<br />
<br />
[http://wiki.hsyco.com/uploads/2.10.0/dev-2.10.0.zip HSYCO 2.10.0 Configuration and Programming Handbook]</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Release_Notes_3.7.0&diff=9381Release Notes 3.7.02020-10-21T13:44:10Z<p>Ulde: /* Server Updates */</p>
<hr />
<div><br />
[[Category: Release Notes]]<br />
<br />
== Server Updates ==<br />
*Aritech Comfort CSx75 I/O Server: added possibility to specify zone names<br />
*ARTECOOC I/O Server:<br />
**verbose log output of XML content posted to server and return data<br />
**session id support<br />
* AVIGILON I/O Server: new I/O Server for the Avigilon Control Center 7<br />
*CONTATTO I/O Server:<br />
**support of MODRHT<br />
**support of MODAM2<br />
**support of MODIGLASS, MODIGLASS3<br />
**support of MODLC firmware version 3.2<br />
**support of MODDALI firmware version 6.x<br />
**support of MCP counters<br />
**bus and modules fault detection<br />
*Dea Xensity I/O Server: new I/O Server for the Dea Xensity indoor shock detectors<br />
*DOMINO I/O Server:<br />
**support of DFANA-M<br />
**support of DFDALI64<br />
**support of DFDIM<br />
**support of DFLS smart mode<br />
**support of DF4RI/DF4RIR virtual outputs<br />
**support of DF8RIT configuration with temperature input address enabled and temperature control disabled<br />
**support of position information and commands for DFTP, DFTP/I<br />
**support of DFCP counters<br />
**bus and modules fault detection<br />
**high availability support for redundant DFH installations<br />
*DUELUX I/O Server: new I/O Server for the Duemmegi DUELUX DLCP DALI-2 system controller<br />
*DUMMY I/O Server:<br />
**new "commandstate" option<br />
**new HTTP API: data points can now be set and read remotely with the /x/httpcall HTTP API<br />
**default number of lights, dimmers, automation is 0 (zero)<br />
*ELMO I/O Server: added support for Pregio, Vidomo (Villeggio series), Proxima and Titania panels<br />
*ESC/VP (EPSON) I/O Server:<br />
**improved protocol compatibility<br />
**added support for "middle" luminance level<br />
*Google Calendar I/O Server:<br />
**added capability of creating events<br />
**added "<cal_name>.json" and "<cal_name>.pre.json" datapoints<br />
*KILSEN I/O Server: new I/O Server for the KILSEN fire alarm panels<br />
*KNX I/O Server:<br />
**added support for DPT 29<br />
**added support for ETS5 export file<br />
**added "initreadinterval" I/O Server option<br />
**minor connection handling improvements<br />
*KSENIA I/O Server: new I/O Server for the KSENIA lares security panels<br />
*IFTTT I/O Server: new I/O Server for the IFTTT service<br />
*IONO I/O Server:<br />
**the IONO I/O Server is now "free". Using it doesn't decrease the number of available I/O servers<br />
**"minvariation" option now also applies to polling mode<br />
*IONO PI I/O Server:<br />
**added support for iono pi driver v1.3.0 and "wiegandbits" option<br />
**added support for local Iono Pi direct access<br />
*IONO PI Max I/O Server: new I/O Server for Sfera Labs Iono Pi Max<br />
*MasterBus I/O Server: new I/O Server for Mastervolt's MasterBus<br />
*Modbus I/O Server:<br />
**new "tcpmodbuseventunitid" option. When the Modbus TCP gateway option is enabled, setting tcpmodbuseventunitid to a Unit Id value (0 to 255) will redirect all TCP requests to that Unit Id to the ModbusEvent() callback instead of the Modbus RTU serial bus<br />
**high-availability: when "shutdown when inactive" is true and the HSYCO Server is inactive, all Modbus calls are affectively blocked, and return null. The TCP gateway is also blocked<br />
*MPOWER I/O Server: new I/O Server for the Ubiquity mFi mPower controllable power outlets<br />
*MQTTBROKER and MQTTCLIENT I/O Servers: new I/O servers add support for the MQTT protocol, client and broker<br />
*MyHome I/O Server: added support for HMAC authentication (for MyHome Server 1 and other recent OpenWebNet gateways)<br />
*NetworX I/O Server: added possibility to specify zone names<br />
*Paradox I/O Server: new "log0" data point<br />
*Philips Hue I/O Server: added support for Hue White devices<br />
*Protege I/O Server: new I/O Server for the ICT ProtegeGX security panel<br />
*Sonos I/O Server:<br />
**added support for SONOS firmware version 9<br />
**added datapoint "<player>.queue = <n>"<br />
**player state is now restored after a track is played via "<player>.play = <uri>" or via public announcement<br />
*SSH I/O Server:<br />
**the SSH I/O Server is now "free". Using it doesn't decrease the number of available I/O servers<br />
**new exec.<timeout> data point. Sets the command execution timeout in seconds; defaults to 30<br />
**new connection = close command: closes the SSH connection<br />
**new user = <user name> command; overrides the user configuration parameter<br />
**new password = <user password> command; overrides the password configuration parameter<br />
**new stdout=line option<br />
*Strato I/O Server:<br />
**added support for Strato Pi CAN and Strato Pi CM Duo<br />
**new cpu.temperature data point<br />
*System I/O Server: new data points:<br />
**cpu.model<br />
**cpu.revision<br />
**database.backup.time<br />
**database.backup.elapsed<br />
**database.backup.consolidation.time<br />
**database.backup.consolidation.elapsed<br />
**database.backup.consolidation.status<br />
**database.defrag.time<br />
**database.defrag.elapsed<br />
**database.update.elapsed<br />
**hsyco.version<br />
**java.version<br />
**os.version<br />
*Tecnoalarm I/O Server: added data point "log0"<br />
*Telegram I/O Server: camera images and generic image files can now be sent via Telegram messages<br />
*WOLF8ACCESS I/O Server: new I/O Server for the Wolf Safety "8 ACCESS" access control system<br />
*WXONLINE I/O Server:<br />
**data source changed from Yahoo to Open Weather Map<br />
**increased number of forcasted days from 2 to 5<br />
**location can be set to latitude and longitude, as well as with the location id<br />
*YAMAHAEC I/O Server: new I/O Server for the Yamaha Extended Control communication protocol<br />
**location can be set to latitude and longitude, as well as with the location id<br />
*new embedded Natural Language Processor to support speech and free format text commands<br />
*Cameras: cameras with static image sources are now supported. If Camera.<id>.Type is set to "static", a single HTTP request is sent to acquire the image when a CAMERAREC action is executed. The live camerapanel display will not trigger HTTP requests to the source, but show the last recorded image. Events are grouped per day. For static cameras only, a variable name (starting with $) can be set in the configuration instead of the URL in order to allow dynamic URLs<br />
*Data loggers: new HourConsolidationFactor option for data loggers. Splits hourly consolidated data in multiple sub-intervals (e.g. HourConsolidationFactor = 4 leaves data grouped at minutes 0, 15, 30, 45 after hour consolidation)<br />
*Program timers: if the program timer id starts with $, then the server will also automatically set a variable, with a name equal to the program timer's id, to the remaining number of seconds. Note that the variable is not guaranteed to be updated at every second, as some updates may be skipped due to timing constraints.<br />
*Communication ports, serial gateways configuration: it is now possible to define a custom read timeout to override the 2 seconds default. Set using CommPort.<id>.Params = <timeoutmillis> in hsyco.ini<br />
*Access control: new trustedUsers option: comma separated list of user IDs that are always considered trusted, even when connected from outside of the trusted network. Trusted users connecting to HSYCO are subject to the time-out defined in KeysTrustedValidityHours<br />
*Location Services: improved compatibility with Ubiquiti UniFi access points<br />
*New Database options for scheduled data structure optimization: DatabaseCompactDay, DatabaseCompactHour, DatabaseCompactMinute, DatabaseCompactEnable<br />
*New Database option for backup consolidation (integrity verification and compression), with automatic recovery: DatabaseBackupConsolidation<br />
*The Datalogger import API (csvread and cvsreadover) can now also receive a CSV string directly instead of a file path<br />
*when TimeAutoUpdate is enabled, NTP synchronization is performed every hour (it was once a day, at 00:30 local time, in previous versions)<br />
*on Linux systems with the Intel U1900 CPU, HSYCO will check the system clock source at startup, and set it to "acpi_pm" if different<br />
*High Availability:<br />
**improved client handover between primary and secondary servers<br />
**new hsyco.ini synchronization feature: hsyco.slavediff.ini file contains changes to hsyco.ini to be applied to the slave version of hsyco.ini. It can contain new properties, existing properties with different values, or existing properties with no value, to remove properties from the master's hsyco.ini file. The hsyco.slavediff.ini should be updated from the master only, even if it is only used by the slave<br />
**new haDatabaseSlaveSync hsyco.ini property: haDatabaseSlaveSync = true (defaults to false) restores the slave database, restarting HSYCO, when a new database backup is synced from the master. DatabaseBackupCosolidation must be true to enable database synchronization<br />
<br />
== EVENTS ==<br />
*new LOGIN <userid> transient event<br />
*new LOGOUT <userid> transient event<br />
*new LOCATIONBEACON event keyword. Supports "LOCATIONBEACON userid = zone" and "LOCATIONBEACON zoneid" event conditions<br />
*new NLP action keyword<br />
*MAIL action: you can now optionally specify the number of frames back from the defined number of seconds since last recording. The new format is: “cam:cameraname[:seconds_back[:frames_back]]”<br />
*new format modifiers for $SUNRISE$ and $SUNSSET$ predefined variables, $SUNRISE:HMS$ and $SUNSSET:HMS$<br />
*AUDIO action: new audio destination format, web@<channel>. <channel> can be a project name or an arbitrary name assigned to an audio channel set using the "audiochannel" project attribute<br />
<br />
== Java API ==<br />
*new loginEvent(String address, String session, String userid) callback<br />
*new logoutEvent(String address, String session, String userid, boolean lock) callback<br />
*new LocationBeaconEvent(String session, String address, String userid, String zone, String distance) callback<br />
*new nlp(String text) command<br />
*new uiLink(String source, String target) command<br />
*sendMail() command: you can now optionally specify the number of frames back from the defined number of seconds since last recording. The new format is: “cam:cameraname[:seconds_back[:frames_back]]”<br />
*ioGet(String id): ioGet("*") returns the ids of all data points in a comma-separated list<br />
*varGet(String name): varGet("*") returns the names of all variables in a comma-separated list. Variable names are upper case<br />
*Modbus: all commands now also accept <ip>:<port number> to connect to Modbus TCP servers with a non-standard port number<br />
*audioPlay() command: new audio destination format, web@<channel>. <channel> can be a project name or an arbitrary name assigned to an audio channel set using the "audiochannel" project attribute<br />
<br />
== JavaScript API ==<br />
*new loginEvent(address, session, userid) callback<br />
*new logoutEvent(address, session, userid, lock) callback<br />
*new LocationBeaconEvent(session, address, userid, zone, distance) callback function<br />
*new nlp(text) command<br />
*new uiLink(source, target) command<br />
*sendMail() command: you can now optionally specify the number of frames back from the defind number of seconds since last recording. The new format is: “cam:cameraname[:seconds_back[:frames_back]]”<br />
*ioGet(id): ioGet("*") returns the ids of all data points in a comma-separated list<br />
*varGet(name): varGet("*") returns the names of all variables in a comma-separated list. Variable names are upper case<br />
*Modbus: all commands now also accept <ip>:<port number> to connect to Modbus TCP servers with a non-standard port number<br />
*audioPlayFile() and audioPlayText() commands: new audio destination format, web@<channel>. <channel> can be a project name or an arbitrary name assigned to an audio channel set using the "audiochannel" project attribute<br />
<br />
== GUI Updates ==<br />
*new "html" object<br />
*new "shape" object<br />
*UI objects redirect variables support<br />
*new page and popup "focus" attribute. Specifying an id of an object contained in the page, it will gain focus immediately if visible, and every time the page is opened<br />
*button, 3button, buttonicon, buttonimage now have an id and uiset attributes: pos, visible, label, blink, opacity, rotation, confirm<br />
*new "confirm” attribute for user and button ui objects. If “true” user has to press a second time to send the command<br />
*fullscreen support for datalogger and camerapanel objects:<br />
**new "fullwindow" url query option<br />
**fullwindow=true|false project's UI attribute: set to true to expand inside the browser's window instead of actually going fullscreen<br />
**pinch to zoom on camerapanel<br />
*datalogger object:<br />
**multi-year view in browser mode<br />
**click the values legends to hide/unhide the corresponding graph<br />
**set download="true" enable local download of datalogger browser data in CSV format<br />
**new "csvseparator" attribute<br />
*scale project attribute and URL option keyword: new "auto" and "fit" options. When scale=auto the user interface is automatically expanded to fill the available browser area. When scale=fit, the user interface is expanded as with auto, but also reduced if the available browser area is smaller than the original project's size. The scale attribute can be set as a static project's directive, a URL keyword, or dynamically with UISET<br />
*new "audiochannel" project attribute<br />
*gohome=N project attribute and URL option keyword: after N seconds of inactivity, go to the menu page, or the page set with the page=<page name> URL option<br />
*PIN and PUK can now be pasted from the clipboard<br />
*camerapanel object:<br />
**added support for for pinch to zoom on camerapanel object when in fullscreen mode in the iOS and Android apps<br />
**single frame email replaced with local download<br />
**redesigned download popup and app download support<br />
**reduced height of playback timeline clickable area<br />
*input object: new cssstyle attribute<br />
*link, imagelink objects:<br />
**the link attribute can be dynamically set with UISET<br />
**link objects now can receive focus<br />
*scheduler object: new groups attribute allows changing the list of schedule groups names via UISET<br />
*video object: new "controls" attribute<br />
*other minor graphical changes to the standard skins<br />
*in previous versions, the automatic web UI reload was triggered by changes in any file under the www directory or on HSYCO startup. Starting from this version, HSYCO startup will not trigger the reload if no www files are changed. Reload will also occur if www files under the plugins directory are changed<br />
<br />
== Manager ==<br />
*new LoRaWAN configuration utility<br />
*new SSH tunnel configuration utility<br />
*added support for iBeacon configuration in Location Services Settings<br />
*Log Viewer filter now accepts "strings delimited by quotes", single quotes, "escaped\"quotes\""<br />
*Project Editor:<br />
**new object alignment tools<br />
**project’s scale parameter now specified through a select field<br />
**new "go to page" button on link objects, and other usability improvements<br />
**new QR Code tool<br />
*Modbus Utility:<br />
**new skip on error interval option: skip reading for the specified amount of time after an error<br />
**new error tolerance option: number of consecutive errors accepted before the error data point is triggered<br />
**improved user interface<br />
*other usability improvements, including resizable attributes input fields, and copy to clipboard for Log Viewer and Status Browser<br />
<br />
== Bug Fixes ==<br />
*improved compatibility with Debian 9 (Stretch) systems:<br />
**high availability active IP hand-over<br />
**LAN IP address configuration change: old address remained active until reboot<br />
**system clock synchronization and network time update support<br />
*improved serial port reliability on Linux (x86) systems<br />
*fixed a bug that could cause the corruption of cameras recording indexes<br />
*improved handling of cameras connections errors<br />
*when the Java runtime version is >= 1.7 symbolic links under the HSYCO root are now handled as normal, valid paths<br />
*High Availability:<br />
**sync of zero-length files generated an exception message<br />
**hsyco.jar could fail to synchronize on slave if listed in the AutoKillFiles configuration parameter on the slave<br />
*Contatto I/O Server: fixes to the MODDALI ballast 1 status data point<br />
*Domino I/O Server: "modulefault" data point of individual modules not working with DFH gateways<br />
*Cradlepoint I/O Server: fixed error parsing data points returning long values<br />
*HSYCO Remote I/O Server:<br />
**data points with the '*' character in the value string couldn't be written to the remote server<br />
**the I/O Server could time out during initialization on a very large local database<br />
*IONO I/O Server: port configuration option was ignored<br />
*Modbus I/O Server: fixed a bug causing conversion errors when reading 4 consecutive registers with "longx" or "ulongx" data types<br />
*Paradox I/O Server: minor fixes<br />
*SMTPSERVER I/O Server: fixed a bug that caused messages without a "Content-type" header in the body to be ignored<br />
*Tecnoalarm I/O Server: pass phrases with upper case characters were not supported<br />
*Tecnofire I/O Server:<br />
**log and lastlog UISet ID fixed<br />
**extended communication wait time after read errors<br />
*Telegram I/O Server: a connection error during the I/O server startup sequence could cause it to wait indefinitely and never connect<br />
*API:<br />
**fixed null return value in the following JavaScript command functions: ioGet, readComm, slimCommand, uiGet, uiSessionGet, urlGet, urlPost<br />
**fixed bug in LocationEvent(mac, ip, zoneId) JavaScript callback function<br />
**fixed return value in UserCommand Javascript callback function (index.js)<br />
*GUI:<br />
**menu or pages gestures and scope declarations could propagate to all pages following the declaration in index.hsm<br />
**chart object: valuerange set using a "." separator caused a client-side JavaScript error<br />
**all link objects: fixed relative URL opening in new tab<br />
**linkmini, linkmicro objects: fixed dynamic label attributes<br />
**link object to external URLs not working correctly on iOS and Android app<br />
**panel object: setting height via UISET did not work<br />
**rgb object: pressing off could fail to send the off command in some circumstances<br />
**scheduler object: group names incorrectly set to lower case on HSYCO restart or scheduler.ini reload<br />
**minor fixes to camera objects<br />
*Manager:<br />
**line object didn’t move correctly pressing the arrow keys<br />
**project's page copy & paste not working<br />
**text editor did not recognize event files in plugins directories</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Release_Notes_3.6.0&diff=9380Release Notes 3.6.02020-10-21T13:37:59Z<p>Ulde: /* Server Updates */</p>
<hr />
<div>[[Category: Release Notes]]<br />
<br />
== Server Updates ==<br />
*Contatto I/O Server:<br />
**added support for MOD32IL<br />
**added support for MOD4TP/I<br />
**added support for MODDALI8<br />
**added support for MODANAM<br />
*Domino I/O Server:<br />
**added support for DFTA and DFTE<br />
**DFIGLASS: added support for the optional temperature sensor, and other enhancements<br />
*Dummy I/O Server:<br />
**added support for generic read/write data points<br />
*Daikin I/O Server:<br />
**added support for iTM<br />
*Google Calendar I/O Server:<br />
**the Google Calendar I/O Server is now "free". Using it doesn't decrease the number of available I/O servers<br />
*GSM I/O Server:<br />
**new "simphase2" option to enable support for SIM phase 2+ on some modems<br />
*Hesa Quaranta I/O Server:<br />
**added datapoint "log0"<br />
*HID Edge Solo I/O Server:<br />
**added support for firmware version 2.0<br />
*HSYCO Remote I/O Server:<br />
**added support for data loggers replication<br />
**new "clocksync" option to automatically sync the clock of the remote server with the local one<br />
*Hue I/O Server:<br />
**added support for Philips Hue bridge 2.0 (Java Hue SDK 1.8.1 API)<br />
*HWGMONITOR I/O Server:<br />
**outputs can now be controlled using the name-based data point, as well as the output ID<br />
*INIM I/O Server:<br />
**added datapoint "log0"<br />
*Modbus I/O Server:<br />
**new Modbus Utility scheduler engine, for automatic scheduling and sequencing of Modbus requests<br />
**new Modbus Utility configuration interface<br />
**the Write Registers data point format now accepts values passed as hexadecimal strings<br />
**performance and stability improvements of the Modbus TCP client communication<br />
**Modbus TCP server / Modbus RTU master gateway:<br />
***new "tcpgatewayblacklist" option for IP address based black lists<br />
***new "tcpgatewaywhitelist" option for IP address based white lists<br />
***new "tcpgatewaypriority" option for IP address based priority support<br />
***new "tcpgatewaytimeout" option to set the maximum response timeout<br />
*MyHome I/O Server:<br />
**new "tempignorelocaloffset" option: when true, when sending zones absolute setpoint commands, the local offset is not corrected<br />
*Notifier I/O Server:<br />
**adds support for old AM-x000 firmware versions<br />
**new data points: detected.loops, detected.sensors.<loop>, detected.modules.<loop>, detected.lcds, detected.annunciators<br />
**data point panel.fire.unknown renamed panel.fire.ack<br />
**data point panel.fault.loop.open renamed panel.fault.siren.open<br />
**data point panel.fault.loop.short renamed panel.fault.siren.short<br />
*RACKPDU I/O Server:<br />
**new I/O Server for the APC (Schneider Electric) Rack Power Distribution Unit series AP88XX AP78XX<br />
*SATEL I/O Server:<br />
**new I/O Server for Satel security panels<br />
*SMTPSERVER I/O Server:<br />
**improved UTF-8 support<br />
**added support for multipart/alternative messages<br />
*Strato I/O Server:<br />
**added support for Strato Pi Mini and Strato Pi CM<br />
**new backlight.brightness data point to set the display backlight brightness of HSYCO Pi Touch Display<br />
*System I/O Server:<br />
**new "process.files" data point returns the total number of file descriptors currently opened by the JVM process<br />
**new "process.threads" data point returns the total number of threads used by the JVM process<br />
**new "watchdog" option: when true, enables the hardware watchdog on Linux servers<br />
**the "time" data point can now be written to set the system's clock<br />
*Tecnoalarm I/O Server:<br />
**adds support for TP8-88P<br />
*Tecnofire I/O Server:<br />
**new I/O Server for the Tecnofire fire panels<br />
*Telegram I/O Server:<br />
**new I/O Server for the Telegram messaging service bot API<br />
*Texecom I/O Server:<br />
**new I/O Server for Texecom security panels<br />
*Serial Communication Ports:<br />
**substantial performance improvements<br />
**the CommPortsList optional parameter is not used any more<br />
*Axis Cameras:<br />
**improved compatibility of PTZ control for panoramic cameras<br />
*Axis Audio devices:<br />
**added user authentication support to the AUDIO action and audioPlay() funcions<br />
*new "haTimeoutSeconds" parameter, allows to change the keep-alive timeout in high availability configuration<br />
*HSQLDB engine upgraded to version 2.3.4<br />
<br />
== EVENTS ==<br />
*new USERTIMERSET action, to dynamically set a user timer<br />
<br />
== Java API ==<br />
* uiSet(String session, String id, String attr, String value): calling this method with a null value, if a global UI value exists, removes the session value and restores the global one. Passing a null value has no effect if there is no previous session UI value, or no global UI value exists<br />
*new userTimerSet(timerid, on, hour, minute, duration, days) function, to dynamically set a user timer<br />
<br />
== JavaScript API ==<br />
*uiSessionSet(String session, String id, String attr, String value): calling this method with a null value, if a global UI value exists, removes the session value and restores the global one. Passing a null value has no effect if there is no previous session UI value, or no global UI value exists<br />
*new userTimerSet(String name, Boolean on, Integer hour, Integer minute, Integer duration, String days) function, to dynamically set a user timer<br />
<br />
== GUI Updates ==<br />
*the PUK authentication now returns with no delay if there were no previous authentication errors within the last 30 seconds<br />
*enhanced datalogger object<br />
**new pie chart type<br />
**support for multiple data logger sources displayed in the same object<br />
**new high-definition attribute<br />
**new valuecolor[n] attribute<br />
*new trigger mode for schedulers<br />
*new download, downloadimage, downloadlist, upload and uploadimage objects<br />
*new line object<br />
*image object:<br />
**new resize attribute<br />
*userimage object:<br />
**set repeat="move" to send commands when the cursor moves over the image; used in combination with parameter="coordinates"<br />
**positioning of pop-up pages now based on click coordinates for large images <br />
*link, linkmini, linkmicro, dlink, imagelink objects:<br />
**add a "!" character to the URL to open the page in a new window or tab<br />
*new alternative landscape/portrait page attribute<br />
*new project attributes: screensaverimage, screensaversize<br />
*improved keyboard support for date objects<br />
*usability improvements to user administration objects<br />
*minor usability improvements to date and datepanel objects<br />
*screensaver mode<br />
*set the page attribute of a project to "logout" to force a log out of the current session and show the PIN pop-up<br />
*extensions and performance improvements to the Draw API<br />
*redesigned Apple Watch support<br />
<br />
== Manager ==<br />
*new Modbus Utility configuration interface<br />
*user IDs now sorted alphabetically in User Admin panels<br />
*redesigned text editor, with code assist<br />
*support for Watch interface design in Project Editor<br />
<br />
== Bug Fixes ==<br />
*Contatto I/O Server:<br />
**fixed a bug that could cause erroneous readings of MODANA's ptotk datapoint when total active power is negative<br />
*Domino I/O Server:<br />
**improved compatibility with DF4DV<br />
**fixed a bug that could affect DF4RI/DF4RIR or DF8RIT modules with adjacent addresses and shutters defined<br />
*Elsner P03/3-MODBUS I/O Server:<br />
**fixed a bug that could cause erroneous readings of negative value temperatures<br />
*GSM I/O Server:<br />
**fixed hang on high traffic conditions<br />
*Guardall I/O Server:<br />
**stability improvements<br />
*HSYCO I/O Server:<br />
**special characters in data point values could cause the I/O server to go offline<br />
*API:<br />
**WebRootRequestEvent not working with URLs to external web servers<br />
*GUI:<br />
**fixed an issue related to the HTML5 persistent cache, that could cause an infinite loop reloading the page<br />
**background image not rendering correctly on Firefox when scaled<br />
**multiline inputs sometimes not working correctly on modal popups in iOS<br />
**minor fixes to the (adminlink) object<br />
**minor fixes to the (dmx) object<br />
**minor fixes to the (keypad) object<br />
**project's autoreload attribute: interface kept on reloading the cache in background if autoreload was false<br />
**fixes to the scale and browserscale attributes of the (datalogger) object, and other minor fixes<br />
*Manager:<br />
**fixed project editor minor issues when browser's view is zoomed</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Release_Notes_3.6.0&diff=9379Release Notes 3.6.02020-10-21T13:37:13Z<p>Ulde: /* Server Updates */</p>
<hr />
<div>[[Category: Release Notes]]<br />
<br />
== Server Updates ==<br />
*Contatto I/O Server:<br />
**added support for MOD32IL<br />
**added support for MOD4TP/I<br />
**added support for MODDALI8<br />
**added support for MODANAM<br />
*Domino I/O Server:<br />
**added support for DFTA and DFTE<br />
**DFIGLASS: added support for the optional temperature sensor, and other enhancements<br />
*Dummy I/O Server:<br />
**added support for generic read/write data points<br />
*Daikin I/O Server:<br />
**added support for iTM<br />
*Google Calendar I/O Server:<br />
**the Google Calendar I/O Server is now "free". Using it doesn't decrease the number of available I/O servers<br />
*GSM I/O Server:<br />
**new "simphase2" option to enable support for SIM phase 2+ on some modems<br />
*Hesa Quaranta I/O Server:<br />
**added datapoint "log0"<br />
*HID Edge Solo I/O Server:<br />
**added support for firmware version 2.0<br />
*HSYCO Remote I/O Server:<br />
**added support for data loggers replication<br />
**new "clocksync" option to automatically sync the clock of the remote server with the local one<br />
*Hue I/O Server:<br />
**added support for Philips Hue bridge 2.0 (Java Hue SDK 1.8.1 API)<br />
*HWGMONITOR I/O Server:<br />
**outputs can now be controlled using the name-based data point, as well as the output ID<br />
*INIM I/O Server:<br />
**added datapoint "log0"<br />
*Modbus I/O Server:<br />
**new Modbus Utility scheduler engine, for automatic scheduling and sequencing of Modbus requests<br />
**new Modbus Utility configuration interface<br />
**the Write Registers data point format now accepts values passed as hexadecimal strings<br />
**performance and stability improvements of the Modbus TCP client communication<br />
**Modbus TCP server / Modbus RTU master gateway:<br />
***new "tcpgatewayblacklist" option for IP address based black lists<br />
***new "tcpgatewaywhitelist" option for IP address based white lists<br />
***new "tcpgatewaypriority" option for IP address based priority support<br />
***new "tcpgatewaytimeout" option to set the maximum response timeout<br />
*MyHome I/O Server:<br />
**new "tempignorelocaloffset" option: when true, when sending zones absolute setpoint commands, the local offset is not corrected<br />
*Notifier I/O Server:<br />
**adds support for old AM-x000 firmware versions<br />
**new data points: detected.loops, detected.sensors.<loop>, detected.modules.<loop>, detected.lcds, detected.annunciators<br />
**data point panel.fire.unknown renamed panel.fire.ack<br />
**data point panel.fault.loop.open renamed panel.fault.siren.open<br />
**data point panel.fault.loop.short renamed panel.fault.siren.short<br />
*RACKPDU I/O Server:<br />
**new I/O Server for the APC (Schneider Electric) Rack Power Distribution Unit series AP88XX AP78XX<br />
*SATEL I/O Server:<br />
**new I/O Server for Satel security panels<br />
*SMTPSERVER I/O Server:<br />
**improved UTF-8 support<br />
**added support for multipart/alternative messages<br />
*SONOS I/O Server:<br />
**added support for SONOS firmware version 9<br />
**added datapoint "<player>.queue = <n>"<br />
**player state is now restored after a track is played via "<player>.play = <uri>" or via public announcement<br />
*Strato I/O Server:<br />
**added support for Strato Pi Mini and Strato Pi CM<br />
**new backlight.brightness data point to set the display backlight brightness of HSYCO Pi Touch Display<br />
*System I/O Server:<br />
**new "process.files" data point returns the total number of file descriptors currently opened by the JVM process<br />
**new "process.threads" data point returns the total number of threads used by the JVM process<br />
**new "watchdog" option: when true, enables the hardware watchdog on Linux servers<br />
**the "time" data point can now be written to set the system's clock<br />
*Tecnoalarm I/O Server:<br />
**adds support for TP8-88P<br />
*Tecnofire I/O Server:<br />
**new I/O Server for the Tecnofire fire panels<br />
*Telegram I/O Server:<br />
**new I/O Server for the Telegram messaging service bot API<br />
*Texecom I/O Server:<br />
**new I/O Server for Texecom security panels<br />
*Serial Communication Ports:<br />
**substantial performance improvements<br />
**the CommPortsList optional parameter is not used any more<br />
*Axis Cameras:<br />
**improved compatibility of PTZ control for panoramic cameras<br />
*Axis Audio devices:<br />
**added user authentication support to the AUDIO action and audioPlay() funcions<br />
*new "haTimeoutSeconds" parameter, allows to change the keep-alive timeout in high availability configuration<br />
*HSQLDB engine upgraded to version 2.3.4<br />
<br />
== EVENTS ==<br />
*new USERTIMERSET action, to dynamically set a user timer<br />
<br />
== Java API ==<br />
* uiSet(String session, String id, String attr, String value): calling this method with a null value, if a global UI value exists, removes the session value and restores the global one. Passing a null value has no effect if there is no previous session UI value, or no global UI value exists<br />
*new userTimerSet(timerid, on, hour, minute, duration, days) function, to dynamically set a user timer<br />
<br />
== JavaScript API ==<br />
*uiSessionSet(String session, String id, String attr, String value): calling this method with a null value, if a global UI value exists, removes the session value and restores the global one. Passing a null value has no effect if there is no previous session UI value, or no global UI value exists<br />
*new userTimerSet(String name, Boolean on, Integer hour, Integer minute, Integer duration, String days) function, to dynamically set a user timer<br />
<br />
== GUI Updates ==<br />
*the PUK authentication now returns with no delay if there were no previous authentication errors within the last 30 seconds<br />
*enhanced datalogger object<br />
**new pie chart type<br />
**support for multiple data logger sources displayed in the same object<br />
**new high-definition attribute<br />
**new valuecolor[n] attribute<br />
*new trigger mode for schedulers<br />
*new download, downloadimage, downloadlist, upload and uploadimage objects<br />
*new line object<br />
*image object:<br />
**new resize attribute<br />
*userimage object:<br />
**set repeat="move" to send commands when the cursor moves over the image; used in combination with parameter="coordinates"<br />
**positioning of pop-up pages now based on click coordinates for large images <br />
*link, linkmini, linkmicro, dlink, imagelink objects:<br />
**add a "!" character to the URL to open the page in a new window or tab<br />
*new alternative landscape/portrait page attribute<br />
*new project attributes: screensaverimage, screensaversize<br />
*improved keyboard support for date objects<br />
*usability improvements to user administration objects<br />
*minor usability improvements to date and datepanel objects<br />
*screensaver mode<br />
*set the page attribute of a project to "logout" to force a log out of the current session and show the PIN pop-up<br />
*extensions and performance improvements to the Draw API<br />
*redesigned Apple Watch support<br />
<br />
== Manager ==<br />
*new Modbus Utility configuration interface<br />
*user IDs now sorted alphabetically in User Admin panels<br />
*redesigned text editor, with code assist<br />
*support for Watch interface design in Project Editor<br />
<br />
== Bug Fixes ==<br />
*Contatto I/O Server:<br />
**fixed a bug that could cause erroneous readings of MODANA's ptotk datapoint when total active power is negative<br />
*Domino I/O Server:<br />
**improved compatibility with DF4DV<br />
**fixed a bug that could affect DF4RI/DF4RIR or DF8RIT modules with adjacent addresses and shutters defined<br />
*Elsner P03/3-MODBUS I/O Server:<br />
**fixed a bug that could cause erroneous readings of negative value temperatures<br />
*GSM I/O Server:<br />
**fixed hang on high traffic conditions<br />
*Guardall I/O Server:<br />
**stability improvements<br />
*HSYCO I/O Server:<br />
**special characters in data point values could cause the I/O server to go offline<br />
*API:<br />
**WebRootRequestEvent not working with URLs to external web servers<br />
*GUI:<br />
**fixed an issue related to the HTML5 persistent cache, that could cause an infinite loop reloading the page<br />
**background image not rendering correctly on Firefox when scaled<br />
**multiline inputs sometimes not working correctly on modal popups in iOS<br />
**minor fixes to the (adminlink) object<br />
**minor fixes to the (dmx) object<br />
**minor fixes to the (keypad) object<br />
**project's autoreload attribute: interface kept on reloading the cache in background if autoreload was false<br />
**fixes to the scale and browserscale attributes of the (datalogger) object, and other minor fixes<br />
*Manager:<br />
**fixed project editor minor issues when browser's view is zoomed</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=JavaScript_Programming&diff=9378JavaScript Programming2020-10-21T08:57:59Z<p>Ulde: /* Reserved word usage */</p>
<hr />
<div>[[Category:JavaScript]]<br />
HSYCO integrates a JavaScript interpreter, allowing you to embed JavaScript code in the EVENTS files.<br />
<br />
There are two ways to embed JavaScript in events: using JavaScript actions and with JavaScript callbacks.<br />
<br />
== JavaScript actions ==<br />
<br />
Actions can be directly implemented in JavaScript, using curly brackets to enclose JavaScript code:<br />
<br />
<syntaxhighlight lang="javascript"><br />
event : { /* JavaScript Code here */ }<br />
</syntaxhighlight><br />
<br />
When the event is triggered, HSYCO will execute the JavaScript code enclosed in the brackets.<br />
<br />
{{tip|The basic action format and the JavaScript action format are exclusive and cannot be mixed after the colon. It is of course possible to define two distinct event:action rules, using the same event, one with standard actions and the other with embedded JavaScript.}}<br />
<br />
The code can be written on multiple lines, only the opening bracket needs to be in the same line of the event section, for example:<br />
<br />
<syntaxhighlight lang="javascript"><br />
TIME : {<br />
// JavaScript Code here<br />
}<br />
</syntaxhighlight><br />
<br />
The syntax highlighter and integrated syntax error viewer are also available for JavaScript. When you save an EVENTS file from the editor, the file is parsed and all JavaScript code is interpreted. Syntax errors, including calling functions that are not defined, are reported in the error viewer, and also logged in the log file.<br />
<br />
In the following example, at line 3, we are referencing a JavaScript function that doesn’t exist. We also have another error at line 6, where the open curly bracket is missing from the action.<br />
<br />
[[File:Events_editor_javascript_errors.png|border|600px|center]]<br />
<br />
=== Coding JavaScript actions ===<br />
<br />
The code you can write in actions is standard JavaScript. Because the interpreter is fully embedded in the HSYCO Java core, you also have access to the standard Java classes and, most importantly, to the HSYCO’s Java commands and utility methods, with only minor differences and a few limitations related to the differences in data types between JavaScript and Java languages.<br />
<br />
In the following example, when the I/O data point k36 goes to 1, the I/O data point k.37, a dimmer in this case, will step from 10% to 100% in 10% increments every 400 milliseconds:<br />
<br />
<syntaxhighlight lang="javascript"><br />
io k.36 = 1 : {<br />
for (i = 10; i <= 100; i += 10) {<br />
ioSet('k.37', i);<br />
sleep(400);<br />
}<br />
} <br />
</syntaxhighlight><br />
<br />
As you can see we have combined standard JavaScript features, like the for loop, with HSYCO’s command APIs, the ioSet() and sleep() methods, to create a simple JavaScript action and associate it to a specific event.<br />
<br />
You can directly use Java classes too, for example:<br />
<br />
<syntaxhighlight lang="javascript"><br />
time = 0000 : {<br />
(new java.io.File("myfile.txt")).renameTo(new java.io.File("myfile_backup.txt"));<br />
}<br />
</syntaxhighlight><br />
<br />
Here we are using the File class, in the java.io package, to rename a file every day at midnight.<br />
<br />
Here is another, slightly more complex example, creating a JavaScript function to append text strings to an arbitrary file:<br />
<br />
<syntaxhighlight lang="javascript"><br />
init : {<br />
function fileLog(fileName, text) {<br />
var date = new java.text.SimpleDateFormat("yyyy-MM-dd hh:mm:ss").format(java.util.Calendar.getInstance().getTime());<br />
var writer = new java.io.BufferedWriter(new java.io.FileWriter(fileName, true));<br />
writer.write(date + " " + text);<br />
writer.newLine();<br />
writer.close();<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
=== Comments in the JavaScript code ===<br />
<br />
You can use the normal JavaScript comment formats. Single line comments start with // and multi line comments start with /* and end with */.<br />
<br />
Because the EVENTS parser is also run on JavaScript code, you can also use the # character to mark text as comment until the end of the line is reached.<br />
<br />
As with the standard EVENTS syntax, if you need to use the # character in JavaScript strings, you should use double quotes, not single quotes, to delimit the string containing # characters.<br />
<br />
=== JavaScript code errors checking ===<br />
<br />
The EVENTS parser is able to report syntax errors in the embedded JavaScript code. If errors are detected, the whole event:action rule is not loaded in the EVENTS engine, to avoid run-time errors.<br />
<br />
Unfortunately, to perform these checks, the parser needs to perform a dummy run of all JavaScript code every time an EVENTS file is loaded.<br />
<br />
During the test run, all calls to HSYCO methods are automatically skipped, and JavaScript variables are segregated in a dedicate test namespace, but any other native Java or JavaScript command will execute as if the event was triggered at run-time.<br />
<br />
In the file rename example, the file would actually be renamed not only at midnight, but also every time EVENTS files are reloaded.<br />
<br />
If you want to avoid unwanted execution of code, you can check the <code>__run</code> predefined JavaScript variable, that is set to 0 when code is test run, and to 1 when executed on proper events. A safe file rename example would be:<br />
<br />
<syntaxhighlight lang="javascript"><br />
time = 0000 : {<br />
if (__run == 1) {<br />
(new java.io.File("myfile.txt")).renameTo(new java.io.File("myfile_backup.txt"));<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
{{tip| Infinite loops in code, or JavaScript code that runs for a very long time are handled in a special way in HSYCO. When EVENTS files are saved, If any code section takes more than 20 seconds to execute during the test run, HSYCO will abort the JavaScript engine, rename the original file with the '''_unsafe.txt''' suffix and, a few seconds later, will restart the whole HSYCO server engine to protect the integrity of the system.}}<br />
<br />
An error message will be visible in the editor, before HSYCO restarts.<br />
<br />
[[File:Events_editor_javascript_unrecoverable_error.png|border|600px|center]]<br />
<br />
The EventsLoadTimeout parameter in the general system configuration parameters of [[Settings#General|Settings]] allows you to change the default 20 seconds timeout.<br />
<br />
=== Predefined variables ===<br />
<br />
Besides <code>__run</code>, there are a few other predefined variables that you can use at run-time: <code>triggerKey</code>, <code>triggerValue</code> and <code>sessionId</code>.<br />
<br />
<code>triggerKey</code> and <code>triggerValue</code> contain the internal representation of the event’s trigger keyword and value that caused the execution of the JavaScript action. These variables could be quite useful when you want to execute code that needs to know which specific event caused its execution, for example when you have a complex event expression, that could be triggered by different events.<br />
<br />
We are not documenting the returned values for these variables, but you can easily find out with a single line of code:<br />
<br />
<syntaxhighlight lang="javascript"><br />
... : { messageLog(triggerKey + "/" + triggerValue + ".") } <br />
</syntaxhighlight><br />
<br />
<code>sessionId</code> returns the internal representation of the Web client session on events like USER and PAGE. You can use the <code>sessionId</code> value directly to set session-specific user interface attributes.<br />
<br />
=== The INIT JavaScript scope ===<br />
<br />
JavaScript code that is associated to the INIT event keyword is different from code associated to any other event, as it is executed in a global scope that is shared with all other JavaScript segments. In more practical terms, if you need to define JavaScript functions or variables that will be used in other JavaScript actions, you should define them in one or more JavaScript actions directly associated to the INIT event, like in the following example:<br />
<br />
<syntaxhighlight lang="javascript"><br />
INIT : {<br />
var counter = 0;<br />
<br />
function myLog(text) {<br />
messageLog(text);<br />
}<br />
}<br />
<br />
TIME : {<br />
if (__run == 1) {<br />
counter++;<br />
myLog("My Counter is: " + counter);<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
{{tip|Note that the INIT scope is bound to each file: variables and functions defined in the INIT section or sections of an events file are only accessible from JavaScript code in the same file.}}<br />
<br />
Check the log file, and you will see something like:<br />
<br />
2014.01.24 15:41:00.519 - My Counter is: 1 <br />
2014.01.24 15:42:00.497 - My Counter is: 2 <br />
2014.01.24 15:43:00.498 - My Counter is: 3<br />
<br />
=== JavaScript Reserved Words ===<br />
<br />
The following are keywords and may not be used as variables, functions, methods, or object identifiers, because ECMAScript specifies special behavior for them:<br />
<br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4"><br />
*break<br />
*case<br />
*catch<br />
*continue<br />
*debugger<br />
*default<br />
*delete<br />
*do<br />
*else<br />
*finally<br />
*for<br />
*function<br />
*if<br />
*in<br />
*instanceof<br />
*new<br />
*return<br />
*switch<br />
*this<br />
*throw<br />
*try<br />
*typeof<br />
*var<br />
*void<br />
*while<br />
*with<br />
</div><br />
<br />
==== Words reserved for possible future use ====<br />
<br />
The following are reserved as future keywords by the ECMAScript specification.<br />
They have no special functionality at present, but they might at some future time, so they cannot be used as identifiers.<br />
<br />
Although some of the following keywords may be used in the current release of the JavaScript engine embedded in HSYCO, we recommend to avoid using any of these to avoid issues with future releases of the HSYCO Server.<br />
<br />
<br />
'''List of future keywords, defined in ECMAScript 1:'''<br />
<br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4"><br />
*const<br />
*enum<br />
*export<br />
*extends<br />
*import<br />
*super<br />
</div><br />
<br />
<br />
'''List of future keywords, defined in ECMAScript 2:'''<br />
<br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4"><br />
*abstract<br />
*boolean<br />
*byte<br />
*char<br />
*class<br />
*const<br />
*double<br />
*enum<br />
*export<br />
*extends<br />
*final<br />
*float<br />
*goto<br />
*implements<br />
*import<br />
*int<br />
*interface<br />
*long<br />
*native<br />
*package<br />
*private<br />
*protected<br />
*public<br />
*short<br />
*static<br />
*super<br />
*synchronized<br />
*throw<br />
*throws<br />
*transient<br />
*volatile<br />
</div><br />
<br />
<br />
'''List of future keywords, defined in ECMAScript 3:'''<br />
<br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4"><br />
*abstract<br />
*boolean<br />
*byte<br />
*char<br />
*class<br />
*const<br />
*double<br />
*enum<br />
*export<br />
*extends<br />
*final<br />
*float<br />
*goto<br />
*implements<br />
*import<br />
*int<br />
*interface<br />
*long<br />
*native<br />
*package<br />
*private<br />
*protected<br />
*public<br />
*short<br />
*static<br />
*super<br />
*synchronized<br />
*throws<br />
*transient<br />
*volatile<br />
</div><br />
<br />
'''List of future keywords, defined in ECMAScript 5:'''<br />
<br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4"><br />
*class<br />
*enum<br />
*export<br />
*extends<br />
*implements<br />
*import<br />
*interface<br />
*let<br />
*package<br />
*private<br />
*protected<br />
*public<br />
*static<br />
*super<br />
*yield<br />
</div><br />
<br />
==== Reserved word usage ====<br />
<br />
In order to call methods of Java classes having the same name of reserved keywords, you can use a notation that refers to the name as "IdentifierNames", avoiding conflict with reserved keywords. For example, to call the delete method of a Java File object, you should use the following notation:<br />
<br />
<syntaxhighlight lang="javascript"><br />
var myfile = new java.io.File("logs/myfile.txt");<br />
myfile['delete']();<br />
</syntaxhighlight><br />
<br />
== JavaScript callbacks ==<br />
<br />
You can also associate JavaScript actions directly to specific event callback functions. This method offers more control and flexibility over the basic event:action syntax. The JavaScript callbacks are equivalent to the Java callbacks, providing full access to all core events in pure JavaScript.<br />
<br />
The JavaScript callback/action syntax in EVENTS is:<br />
<br />
<syntaxhighlight lang="javascript"><br />
function f(p) : { /* JavaScript Code here */ }<br />
</syntaxhighlight><br />
<br />
where f(p) is one of the callback functions with its parameters. The parameters’ names in the callback declaration are available as variables in the JavaScript action code.<br />
<br />
This syntax is quite similar to what a normal function declaration in JavaScript would be, just with the added colon character between the function’s parameter’s list and the function’s code.<br />
<br />
Just like ordinary functions, if the JavaScript action code is associated to a callback function and not to a basic event, you are allowed to use the return statement to return a value to the HSYCO event engine. Some callbacks will need return values to implement specific features. For example:<br />
<br />
<syntaxhighlight lang="javascript"><br />
function WebRootRequestEvent(addr, secure, useragent) : {<br />
return "hsycoserver/manager";<br />
}<br />
</syntaxhighlight><br />
<br />
This code will redirect root HTTP requests received by the HSYCO server to the manager page. In fact the WebRootRequestEvent() callback is called on every HTTP request received by the HTTP server, and takes an optional return value as the redirection URL.<br />
<br />
<br />
{{note|You can define multiple JavaScript functions for the same callback in the same EVENTS file or different files, but execution order is not guaranteed. If the functions return a value, only the first not null value returned is used as the event return value.}}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9257SSH Tunnel Utility2020-10-14T16:19:16Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
{{note|Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.}}<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!Description<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.enable<br />
|true<br />
|enable the tunnels<br />
|-<br />
|false<br />
|disable the tunnels<br />
<br />
|-<br />
|sshtunnel.host<br />
|<host><br />
|the SSH hub host name or IP address<br />
<br />
|-<br />
|sshtunnel.user<br />
|<user><br />
|the user name on SSH hub used to connect from this unit<br />
<br />
|-<br />
|sshtunnel.ssh.port<br />
|<port><br />
|the SSH port number on hub that will be tunnelled to this unit's SSH port<br />
<br />
|-<br />
|sshtunnel.https.port<br />
|<port><br />
|the HTTPS port number on hub that will be tunnelled to this unit's HTTPS port<br />
<br />
|-<br />
|sshtunnel.https.local.port<br />
|<port><br />
|the local HTTPS port number<br />
<br />
|-<br />
|sshtunnel.aux.port<br />
|<port><br />
|the AUX port number on hub that will be tunnelled to this unit's AUX port<br />
<br />
|-<br />
|sshtunnel.aux.local.port<br />
|<port><br />
|the local AUX port number<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.kill<br />
|true<br />
|all running SSH processes will be killed at start-up<br />
|-<br />
|false<br />
|don't kill SSH processes at start-up<br />
<br />
|}<br />
<br />
{{note|The tunnel utility must not be enabled to change the configuration parameters with API commands.}}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9256SSH Tunnel Utility2020-10-14T16:18:55Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
{{note|Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped}}<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!Description<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.enable<br />
|true<br />
|enable the tunnels<br />
|-<br />
|false<br />
|disable the tunnels<br />
<br />
|-<br />
|sshtunnel.host<br />
|<host><br />
|the SSH hub host name or IP address<br />
<br />
|-<br />
|sshtunnel.user<br />
|<user><br />
|the user name on SSH hub used to connect from this unit<br />
<br />
|-<br />
|sshtunnel.ssh.port<br />
|<port><br />
|the SSH port number on hub that will be tunnelled to this unit's SSH port<br />
<br />
|-<br />
|sshtunnel.https.port<br />
|<port><br />
|the HTTPS port number on hub that will be tunnelled to this unit's HTTPS port<br />
<br />
|-<br />
|sshtunnel.https.local.port<br />
|<port><br />
|the local HTTPS port number<br />
<br />
|-<br />
|sshtunnel.aux.port<br />
|<port><br />
|the AUX port number on hub that will be tunnelled to this unit's AUX port<br />
<br />
|-<br />
|sshtunnel.aux.local.port<br />
|<port><br />
|the local AUX port number<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.kill<br />
|true<br />
|all running SSH processes will be killed at start-up<br />
|-<br />
|false<br />
|don't kill SSH processes at start-up<br />
<br />
|}<br />
<br />
{{note|The tunnel utility must not be enabled to change the configuration parameters with API commands}}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9255SSH Tunnel Utility2020-10-14T16:18:28Z<p>Ulde: /* User commands */</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!Description<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.enable<br />
|true<br />
|enable the tunnels<br />
|-<br />
|false<br />
|disable the tunnels<br />
<br />
|-<br />
|sshtunnel.host<br />
|<host><br />
|the SSH hub host name or IP address<br />
<br />
|-<br />
|sshtunnel.user<br />
|<user><br />
|the user name on SSH hub used to connect from this unit<br />
<br />
|-<br />
|sshtunnel.ssh.port<br />
|<port><br />
|the SSH port number on hub that will be tunnelled to this unit's SSH port<br />
<br />
|-<br />
|sshtunnel.https.port<br />
|<port><br />
|the HTTPS port number on hub that will be tunnelled to this unit's HTTPS port<br />
<br />
|-<br />
|sshtunnel.https.local.port<br />
|<port><br />
|the local HTTPS port number<br />
<br />
|-<br />
|sshtunnel.aux.port<br />
|<port><br />
|the AUX port number on hub that will be tunnelled to this unit's AUX port<br />
<br />
|-<br />
|sshtunnel.aux.local.port<br />
|<port><br />
|the local AUX port number<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.kill<br />
|true<br />
|all running SSH processes will be killed at start-up<br />
|-<br />
|false<br />
|don't kill SSH processes at start-up<br />
<br />
|}<br />
<br />
{{note|The tunnel utility must not be enabled to change the configuration parameters with API commands}}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9254SSH Tunnel Utility2020-10-14T16:17:11Z<p>Ulde: /* User commands */</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!Description<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.enable<br />
|true<br />
|enable the tunnels (the tunnel must not be enabled to change the configuration parameters with API commands)<br />
|-<br />
|false<br />
|disable the tunnels<br />
<br />
|-<br />
|sshtunnel.host<br />
|<host><br />
|the SSH hub host name or IP address<br />
<br />
|-<br />
|sshtunnel.user<br />
|<user><br />
|the user name on SSH hub used to connect from this unit<br />
<br />
|-<br />
|sshtunnel.ssh.port<br />
|<port><br />
|the SSH port number on hub that will be tunnelled to this unit's SSH port<br />
<br />
|-<br />
|sshtunnel.https.port<br />
|<port><br />
|the HTTPS port number on hub that will be tunnelled to this unit's HTTPS port<br />
<br />
|-<br />
|sshtunnel.https.local.port<br />
|<port><br />
|the local HTTPS port number<br />
<br />
|-<br />
|sshtunnel.aux.port<br />
|<port><br />
|the AUX port number on hub that will be tunnelled to this unit's AUX port<br />
<br />
|-<br />
|sshtunnel.aux.local.port<br />
|<port><br />
|the local AUX port number<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.kill<br />
|true<br />
|all running SSH processes will be killed at start-up<br />
|-<br />
|false<br />
|don't kill SSH processes at start-up<br />
<br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9253SSH Tunnel Utility2020-10-14T16:16:38Z<p>Ulde: /* User commands */</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!Description<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.enable<br />
|true<br />
|enable the tunnels (the tunnel must not be enabled to edit the configuration parameters)<br />
|-<br />
|false<br />
|disable the tunnels<br />
<br />
|-<br />
|sshtunnel.host<br />
|<host><br />
|the SSH hub host name or IP address<br />
<br />
|-<br />
|sshtunnel.user<br />
|<user><br />
|the user name on SSH hub used to connect from this unit<br />
<br />
|-<br />
|sshtunnel.ssh.port<br />
|<port><br />
|the SSH port number on hub that will be tunnelled to this unit's SSH port<br />
<br />
|-<br />
|sshtunnel.https.port<br />
|<port><br />
|the HTTPS port number on hub that will be tunnelled to this unit's HTTPS port<br />
<br />
|-<br />
|sshtunnel.https.local.port<br />
|<port><br />
|the local HTTPS port number<br />
<br />
|-<br />
|sshtunnel.aux.port<br />
|<port><br />
|the AUX port number on hub that will be tunnelled to this unit's AUX port<br />
<br />
|-<br />
|sshtunnel.aux.local.port<br />
|<port><br />
|the local AUX port number<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.kill<br />
|true<br />
|all running SSH processes will be killed at start-up<br />
|-<br />
|false<br />
|don't kill SSH processes at start-up<br />
<br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9252SSH Tunnel Utility2020-10-14T16:15:52Z<p>Ulde: /* User commands */</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!Description<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.enable<br />
|true<br />
|enable the tunnels (the tunnel must not be enabled to edit the configuration parameters)<br />
|-<br />
|false<br />
|disable the tunnels<br />
<br />
|-<br />
|sshtunnel.host<br />
|<name><br />
|the SSH hub host name or IP address<br />
<br />
|-<br />
|sshtunnel.user<br />
|<name><br />
|the user name on SSH hub used to connect from this unit<br />
<br />
|-<br />
|sshtunnel.ssh.port<br />
|<name><br />
|the SSH port number on hub that will be tunnelled to this unit's SSH port<br />
<br />
|-<br />
|sshtunnel.https.port<br />
|<name><br />
|the HTTPS port number on hub that will be tunnelled to this unit's HTTPS port<br />
<br />
|-<br />
|sshtunnel.https.local.port<br />
|<name><br />
|the local HTTPS port number<br />
<br />
|-<br />
|sshtunnel.aux.port<br />
|<name><br />
|the AUX port number on hub that will be tunnelled to this unit's AUX port<br />
<br />
|-<br />
|sshtunnel.aux.local.port<br />
|<name><br />
|the local AUX port number<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.kill<br />
|true<br />
|all running SSH processes will be killed at start-up<br />
|-<br />
|false<br />
|don't kill SSH processes at start-up<br />
<br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9251SSH Tunnel Utility2020-10-14T16:08:04Z<p>Ulde: /* User commands */</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!Description<br />
<br />
|-<br />
|rowspan="2" |sshtunnel.enable<br />
|true<br />
|enable the tunnels<br />
|-<br />
|false<br />
|disable the tunnels<br />
<br />
|-<br />
|sshtunnel.host<br />
|<name><br />
|network name or IP address of the remote SSH tunnel server (hub)<br />
<br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9250SSH Tunnel Utility2020-10-14T16:06:25Z<p>Ulde: /* User commands */</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!Description<br />
<br />
|-<br />
<br />
|rowspan="2" |sshtunnel.enable<br />
|true<br />
|enable the tunnels<br />
|-<br />
|false<br />
|disable the tunnels<br />
<br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9249SSH Tunnel Utility2020-10-14T16:05:14Z<p>Ulde: /* User commands */</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!R/W<br />
!Description<br />
<br />
|-<br />
<br />
|rowspan="2" |battery<br>(base/ups only)<br />
|0<br />
|R<br />
|power supply is available<br />
|-<br />
|1<br />
|R<br />
|power supply failure, running on UPS battery<br />
<br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9248SSH Tunnel Utility2020-10-14T16:04:38Z<p>Ulde: /* User commands */</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!R/W<br />
!Description<br />
<br />
|-<br />
<br />
|rowspan="2" |backlight.brightness<br />
|rowspan="2" |<brightness><br />
|R<br />
|the current backlight brightness of HSYCO Pi Touch Display<br />
|-<br />
|W<br />
|set brightness of HSYCO Pi Touch Display to a value between 0 (off) and 255 (max)<br />
<br />
|-<br />
<br />
|rowspan="2" |battery<br>(base/ups only)<br />
|0<br />
|R<br />
|power supply is available<br />
|-<br />
|1<br />
|R<br />
|power supply failure, running on UPS battery<br />
<br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9247SSH Tunnel Utility2020-10-14T16:04:02Z<p>Ulde: /* = User commands */</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ===<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!R/W<br />
!Description<br />
<br />
|-<br />
<br />
|rowspan="2" |backlight.brightness<br />
|rowspan="2" |<brightness><br />
|R<br />
|the current backlight brightness of HSYCO Pi Touch Display<br />
|-<br />
|W<br />
|set brightness of HSYCO Pi Touch Display to a value between 0 (off) and 255 (max)<br />
<br />
|-<br />
<br />
|rowspan="2" |battery<br>(base/ups only)<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>(base/ups/mini only)<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 />
|cpu.temperature<br />
|<temperature><br />
|R<br />
|the current CPU core temperature in Celsius degrees<br />
<br />
|-<br />
<br />
|rowspan="6" |led<br>(cm only)<br />
|0<br />
|R<br />
|led is off<br />
|-<br />
|1<br />
|R<br />
|led is on<br />
|-<br />
|off<br />
|W<br />
|turn led off<br />
|-<br />
|on<br />
|W<br />
|turn led on<br />
|-<br />
|<duration><br />
|W<br />
|turn led on for <duration> seconds (decimals allowed)<br />
|-<br />
|<duration>;<pause><br />
|W<br />
|turn led on for <duration> seconds, then pause for <pause> seconds (decimals allowed)<br />
<br />
|-<br />
<br />
|rowspan="4" |heartbeat<br>(base/ups/cm only)<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>(base/ups/cm only)<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. On Strato Pi CM, a hardware reset of the Compute Module is performed, while the power is not removed<br />
<br />
|-<br />
<br />
|rowspan="2" |timeout<br>(base/ups/cm only)<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. On Strato Pi CM, a hardware reset of the Compute Module is performed, while the power is not removed<br />
<br />
|-<br />
<br />
|rowspan="4" |watchdog<br>(base/ups/cm only)<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. On Strato Pi CM, a hardware reset of the Compute Module is performed, while the power is not removed<br />
<br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9246SSH Tunnel Utility2020-10-14T15:59:37Z<p>Ulde: /* The configuration API */</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false<br />
<br />
=== User commands ==<br />
<br />
{| class="wikitable"<br />
!ID<br />
!Value<br />
!R/W<br />
!Description<br />
<br />
|-<br />
<br />
|rowspan="2" |backlight.brightness<br />
|rowspan="2" |<brightness><br />
|R<br />
|the current backlight brightness of HSYCO Pi Touch Display<br />
|-<br />
|W<br />
|set brightness of HSYCO Pi Touch Display to a value between 0 (off) and 255 (max)<br />
<br />
|-<br />
<br />
|rowspan="2" |battery<br>(base/ups only)<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>(base/ups/mini only)<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 />
|cpu.temperature<br />
|<temperature><br />
|R<br />
|the current CPU core temperature in Celsius degrees<br />
<br />
|-<br />
<br />
|rowspan="6" |led<br>(cm only)<br />
|0<br />
|R<br />
|led is off<br />
|-<br />
|1<br />
|R<br />
|led is on<br />
|-<br />
|off<br />
|W<br />
|turn led off<br />
|-<br />
|on<br />
|W<br />
|turn led on<br />
|-<br />
|<duration><br />
|W<br />
|turn led on for <duration> seconds (decimals allowed)<br />
|-<br />
|<duration>;<pause><br />
|W<br />
|turn led on for <duration> seconds, then pause for <pause> seconds (decimals allowed)<br />
<br />
|-<br />
<br />
|rowspan="4" |heartbeat<br>(base/ups/cm only)<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>(base/ups/cm only)<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. On Strato Pi CM, a hardware reset of the Compute Module is performed, while the power is not removed<br />
<br />
|-<br />
<br />
|rowspan="2" |timeout<br>(base/ups/cm only)<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. On Strato Pi CM, a hardware reset of the Compute Module is performed, while the power is not removed<br />
<br />
|-<br />
<br />
|rowspan="4" |watchdog<br>(base/ups/cm only)<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. On Strato Pi CM, a hardware reset of the Compute Module is performed, while the power is not removed<br />
<br />
|}</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9245SSH Tunnel Utility2020-10-14T15:57:51Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
== The configuration API ==<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9244SSH Tunnel Utility2020-10-14T15:57:06Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility allows to create secure reverse SSH-based connection tunnels to a remote SSH server (hub). Up to three concurrent tunnels can be established, one for local SSH console access, one for the HTTPS Web server connections and one additional (AUX) tunnel to any local service network port like, for example, the Modbus TCP Gateway server.<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
A tunnel is configured by setting the local TCP port of a network server, and the remote TCP port for the tunnel on the remote SSH server. Connecting to the TCP port associated to a tunnel on the remote server will route the connection and all established traffic, through the tunnel, to the local TCP port defined in the tunnel configuration.<br />
<br />
Thanks to the SSH tunnels, a local HSYCO Server that lacks inbound connectivity, could still be accessed via a remote and accessible SSH server configured as a tunnel end-point.<br />
<br />
The tunnel configuration parameters can be modified only when tunneling is not enabled.<br />
<br />
The "SSH hub host name" is the network name or IP address of the remote SSH tunnel server (hub).<br />
<br />
In order to establish a secure connection, the SSH Tunnel Utility authenticates on the remote SSH tunnel server with the user id set in "SSH user on hub" and the "SSH public key" of the HSYCO Server, that must be copied into the "authorized_keys" file on the hub for that user.<br />
<br />
If the SSH, HTTPS or AUX port number fields are left empty, the corresponding tunnel is not activated.<br />
<br />
Note that the tunnels are only active while HSYCO is running. Restarting HSYCO, all connections established through the tunnels, including the SSH connection, are dropped.<br />
<br />
<br />
The configuration API<br />
<br />
The SSH Tunnel Utility can be dynamically configured, and the tunnel service enabled and disabled, with USER calls in ENVENTS and the user() command in Java or JavaScript.<br />
<br />
In the following EVENTS example, the tunnel is enabled at 08:00 and disabled at 18:00.<br />
<br />
TIME 0800 : USER sshtunnel.enable = true<br />
TIME 1800 : USER sshtunnel.enable = false</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Modbus_Utility&diff=9243Modbus Utility2020-10-14T11:04:21Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager Modbus Utility Icon.png|class=appIcon]]<br />
The Modbus Utility is an application that allows you to easily setup repetitive polling read requests and monitor the performance and status of each request.<br />
<br />
Each read request is defined with a repeat interval in seconds. The Modbus Utility internal scheduler will try to repeat the execution of each request as close as possible to the preset interval. It will also sequence all requests to the same Modbus I/O server so they never overlap.<br />
<br />
You can optionally assign a variable to each request for conditional execution. If a variable is defined, it has to exist and have value “1” to activate the request polling. Requests that are not active are highlighted in grey.<br />
<br />
The optional "Error Tolerance" parameter is used to set the number of consecutive errors accepted before the Modbus error data point is set to report an error condition. The default is zero, so that even a single error will set the error data point. For example, setting the error tolerance to two means that up to two consecutive errors will be tolerated, and only the third consecutive error will set the error data point.<br />
<br />
The optional "Error Skip Interval" defines for how long the Modbus Utility should stop executing a Modbus request if an error occurs.<br />
<br />
<br />
[[File:ModbusUtility1.png|border|600px|center|Modbus Utility]]<br />
<br />
<br />
The Modbus Utility tracks the actual repeat interval and compares it with the defined interval. If the difference is more than 25% from the target value, the request is marked as “slow” and highlighted in yellow. The difference between defined and actual interval is reported in the “delta” field. <br />
<br />
Requests that return errors are also tracked and highlighted in red.<br />
<br />
The minimum and maximum response time is also tracked for each request, and displayed in the “min. time” and “max. time” fields in the requests list.<br />
<br />
You can reset the status, delta, minimum and maximum time using the “refresh” button.<br />
<br />
You can use filters to only show a subset of requests in the user interface. Entering a text in the search field will only show requests having a data point name that contains the search text. You can also filter by status, selecting slow, skipped, errors, or successful requests.<br />
<br />
{{note|Note that filters act globally, so if you set a filter all other users will also share the same view of the filtered list. Also note that, to reduce performance overhead, the status and performance data in the list of requests stops being updated after about 60 seconds of inactivity. This is also shared by all users. The refresh of requests’ data has no effect on the actual request scheduler, that runs independently and is never interrupted.}}<br />
<br />
<br />
[[File:ModbusUtility2.png|border|600px|center|Modbus Utility]]<br />
<br />
<br />
The Modbus Utility configuration is stored in a human readable file named modbus-scheduler.ini and located in HSYCO’s main directory. If you manually edit this file, it will be automatically reloaded within a few seconds after it is saved. In a high availability setup, the Modbus Utility is also automatically mirrored from the master to the slave server.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9242SSH Tunnel Utility2020-10-14T11:03:57Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility is an application that allows you to easily setup repetitive polling read requests and monitor the performance and status of each request.<br />
<br />
Each read request is defined with a repeat interval in seconds. The Modbus Utility internal scheduler will try to repeat the execution of each request as close as possible to the preset interval. It will also sequence all requests to the same Modbus I/O server so they never overlap.<br />
<br />
You can optionally assign a variable to each request for conditional execution. If a variable is defined, it has to exist and have value “1” to activate the request polling. Requests that are not active are highlighted in grey.<br />
<br />
The optional "Error Tolerance" parameter is used to set the number of consecutive errors accepted before the Modbus error data point is set to report an error condition. The default is zero, so that even a single error will set the error data point. For example, setting the error tolerance to two means that up to two consecutive errors will be tolerated, and only the third consecutive error will set the error data point.<br />
<br />
The optional "Error Skip Interval" defines for how long the Modbus Utility should stop executing a Modbus request if an error occurs.<br />
<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
The Modbus Utility tracks the actual repeat interval and compares it with the defined interval. If the difference is more than 25% from the target value, the request is marked as “slow” and highlighted in yellow. The difference between defined and actual interval is reported in the “delta” field. <br />
<br />
Requests that return errors are also tracked and highlighted in red.<br />
<br />
The minimum and maximum response time is also tracked for each request, and displayed in the “min. time” and “max. time” fields in the requests list.<br />
<br />
You can reset the status, delta, minimum and maximum time using the “refresh” button.<br />
<br />
You can use filters to only show a subset of requests in the user interface. Entering a text in the search field will only show requests having a data point name that contains the search text. You can also filter by status, selecting slow, skipped, errors, or successful requests.<br />
<br />
{{note|Note that filters act globally, so if you set a filter all other users will also share the same view of the filtered list. Also note that, to reduce performance overhead, the status and performance data in the list of requests stops being updated after about 60 seconds of inactivity. This is also shared by all users. The refresh of requests’ data has no effect on the actual request scheduler, that runs independently and is never interrupted.}}<br />
<br />
The Modbus Utility configuration is stored in a human readable file named modbus-scheduler.ini and located in HSYCO’s main directory. If you manually edit this file, it will be automatically reloaded within a few seconds after it is saved. In a high availability setup, the Modbus Utility is also automatically mirrored from the master to the slave server.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Manager&diff=9236Manager2020-10-14T10:23:58Z<p>Ulde: </p>
<hr />
<div>[[Category:System Architecture]]<br />
The Manager is the Web-based toolkit of applications that you will use to create customized graphic user interfaces and access all system's configuration files.<br />
<br />
<br />
{{note|The Manager runs on most modern Web browsers, including tablets like Apple’s iPad. It also runs on small screen devices like the iPhone or iPod touch, although a larger screen size is advisable for ease of use. Microsoft’s Internet Explorer versions 8 and older are not supported, and IE9 is not guaranteed to work, although it should in most cases.}}<br />
<br />
<br />
To access the Manager, enter the following URL in your Web Browser:<br />
<br />
<nowiki>https://192.168.0.50/hsycoserver/manager</nowiki><br />
<br />
[[File:Manager menu.png|240px|thumb|The Manager's application popup]]<br />
[[File:Manager About.png|240px|thumb|<br />
Touch!! “about” in the bottom left corner to show HSYCO’s current version information.<br />
]]<br />
You need to authenticate using a PIN with administrator privileges to use the Manager.<br />
<br />
<br />
The Manager has several applications:<br />
<br />
*[[File:Manager Settings Icon.png|20px|link=Settings]] '''[[Settings]]''' - to configure the HSYCO system.<br />
<br />
*[[File:Manager Admin Icon.png|20px|link=Admin]] '''[[Admin]]''' - for basic user and network settings.<br />
<br />
*[[File:Manager Project Editor Icon.png|20px|link=Project Editor]] '''[[Project Editor]]''' - the visual editor used to create the user interfaces.<br />
<br />
*[[File:Manager File Manager Icon.png|20px|link=File Manager]] '''[[File Manager]]''' - provides access to all HSYCO's files, just like the standard file manager you have in your personal computer, only this one is fully Web-based and works directly on HSYCO Server's files.<br />
<br />
*[[File:Manager Log Viewer Icon.png|20px|link=Log Viewer]] '''[[Log Viewer]]''' - a real-time viewer of HSYCO's logs.<br />
<br />
*[[File:Manager Status Browser Icon.png|20px|link=Status Browser]] '''[[Status Browser]]''' - a real-time viewer of data points, variables and dynamic user interface attributes.<br />
<br />
*[[File:Manager System Monitor Icon.png|20px|link=System Monitor]] '''[[System Monitor]]''' - used to monitor several key hardware and operating system parameter of the HSYCO server.<br />
<br />
*[[File:Manager Wiring Editor Icon.png|20px|link=Wiring Editor]] '''[[Wiring Editor]]''' - an easy to use end-user logic and scenarios builder.<br />
<br />
*[[File:Manager Modbus Utility Icon.png|20px|link=Modbus Utility]] '''[[Modbus Utility]]''' - accessible if the Modbus I/O server is enabled<br />
<br />
*[[File:Manager KNX Utility Icon.png|20px|link=KNX Utility]] '''[[KNX Utility]]''' - accessible if the KNX I/O server is enabled<br />
<br />
*[[File:Manager BACnet Utility Icon.png|20px|link=BACnet Utility]] '''[[BACnet Utility]]''' - accessible if the BACnet I/O server is enabled<br />
<br />
*[[File:Manager LoRaWAN Utility Icon.png|20px|link=LoRaWAN Utility]] '''[[LoRaWAN Utility]]''' - accessible if the LoRaWAN I/O server is enabled<br />
<br />
*[[File:Manager SSH Tunnel Utility Icon.png|20px|link=SSH Tunnel Utility]] '''[[SSH Tunnel Utility]]''' - SSH reverse tunnel configuration<br />
<br />
*[[File:Manager Heos Utility Icon.png|20px|link=Heos Utility]] '''[[Heos Utility]]''' - accessible if the Heos I/O server is enabled<br />
<br />
<br />
You can switch between applications from any application using the [[File:Manager Switching Applications.png]] button on the top bar.<br />
<br />
Using a PC with a physical keyboard, you can also press '''[Ctrl] and [Shift]''' at the same time for fast switching between applications. An application selection panel appears until you keep the [Ctrl] key pressed; select the application you need by repeatedly pressing [Shift], then releasing [Ctrl].</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Manager&diff=9235Manager2020-10-14T10:23:45Z<p>Ulde: </p>
<hr />
<div>[[Category:System Architecture]]<br />
The Manager is the Web-based toolkit of applications that you will use to create customized graphic user interfaces and access all system's configuration files.<br />
<br />
<br />
{{note|The Manager runs on most modern Web browsers, including tablets like Apple’s iPad. It also runs on small screen devices like the iPhone or iPod touch, although a larger screen size is advisable for ease of use. Microsoft’s Internet Explorer versions 8 and older are not supported, and IE9 is not guaranteed to work, although it should in most cases.}}<br />
<br />
<br />
To access the Manager, enter the following URL in your Web Browser:<br />
<br />
<nowiki>https://192.168.0.50/hsycoserver/manager</nowiki><br />
<br />
[[File:Manager menu.png|240px|thumb|The Manager's application popup]]<br />
[[File:Manager About.png|100px|thumb|<br />
Touch!! “about” in the bottom left corner to show HSYCO’s current version information.<br />
]]<br />
You need to authenticate using a PIN with administrator privileges to use the Manager.<br />
<br />
<br />
The Manager has several applications:<br />
<br />
*[[File:Manager Settings Icon.png|20px|link=Settings]] '''[[Settings]]''' - to configure the HSYCO system.<br />
<br />
*[[File:Manager Admin Icon.png|20px|link=Admin]] '''[[Admin]]''' - for basic user and network settings.<br />
<br />
*[[File:Manager Project Editor Icon.png|20px|link=Project Editor]] '''[[Project Editor]]''' - the visual editor used to create the user interfaces.<br />
<br />
*[[File:Manager File Manager Icon.png|20px|link=File Manager]] '''[[File Manager]]''' - provides access to all HSYCO's files, just like the standard file manager you have in your personal computer, only this one is fully Web-based and works directly on HSYCO Server's files.<br />
<br />
*[[File:Manager Log Viewer Icon.png|20px|link=Log Viewer]] '''[[Log Viewer]]''' - a real-time viewer of HSYCO's logs.<br />
<br />
*[[File:Manager Status Browser Icon.png|20px|link=Status Browser]] '''[[Status Browser]]''' - a real-time viewer of data points, variables and dynamic user interface attributes.<br />
<br />
*[[File:Manager System Monitor Icon.png|20px|link=System Monitor]] '''[[System Monitor]]''' - used to monitor several key hardware and operating system parameter of the HSYCO server.<br />
<br />
*[[File:Manager Wiring Editor Icon.png|20px|link=Wiring Editor]] '''[[Wiring Editor]]''' - an easy to use end-user logic and scenarios builder.<br />
<br />
*[[File:Manager Modbus Utility Icon.png|20px|link=Modbus Utility]] '''[[Modbus Utility]]''' - accessible if the Modbus I/O server is enabled<br />
<br />
*[[File:Manager KNX Utility Icon.png|20px|link=KNX Utility]] '''[[KNX Utility]]''' - accessible if the KNX I/O server is enabled<br />
<br />
*[[File:Manager BACnet Utility Icon.png|20px|link=BACnet Utility]] '''[[BACnet Utility]]''' - accessible if the BACnet I/O server is enabled<br />
<br />
*[[File:Manager LoRaWAN Utility Icon.png|20px|link=LoRaWAN Utility]] '''[[LoRaWAN Utility]]''' - accessible if the LoRaWAN I/O server is enabled<br />
<br />
*[[File:Manager SSH Tunnel Utility Icon.png|20px|link=SSH Tunnel Utility]] '''[[SSH Tunnel Utility]]''' - SSH reverse tunnel configuration<br />
<br />
*[[File:Manager Heos Utility Icon.png|20px|link=Heos Utility]] '''[[Heos Utility]]''' - accessible if the Heos I/O server is enabled<br />
<br />
<br />
You can switch between applications from any application using the [[File:Manager Switching Applications.png]] button on the top bar.<br />
<br />
Using a PC with a physical keyboard, you can also press '''[Ctrl] and [Shift]''' at the same time for fast switching between applications. An application selection panel appears until you keep the [Ctrl] key pressed; select the application you need by repeatedly pressing [Shift], then releasing [Ctrl].</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Manager&diff=9234Manager2020-10-14T10:23:17Z<p>Ulde: </p>
<hr />
<div>[[Category:System Architecture]]<br />
The Manager is the Web-based toolkit of applications that you will use to create customized graphic user interfaces and access all system's configuration files.<br />
<br />
<br />
{{note|The Manager runs on most modern Web browsers, including tablets like Apple’s iPad. It also runs on small screen devices like the iPhone or iPod touch, although a larger screen size is advisable for ease of use. Microsoft’s Internet Explorer versions 8 and older are not supported, and IE9 is not guaranteed to work, although it should in most cases.}}<br />
<br />
<br />
To access the Manager, enter the following URL in your Web Browser:<br />
<br />
<nowiki>https://192.168.0.50/hsycoserver/manager</nowiki><br />
<br />
[[File:Manager menu.png|240px|thumb|The Manager's application popup]]<br />
[[File:Manager About.png|100px|frame|<br />
Touch!! “about” in the bottom left corner to show HSYCO’s current version information.<br />
]]<br />
You need to authenticate using a PIN with administrator privileges to use the Manager.<br />
<br />
<br />
The Manager has several applications:<br />
<br />
*[[File:Manager Settings Icon.png|20px|link=Settings]] '''[[Settings]]''' - to configure the HSYCO system.<br />
<br />
*[[File:Manager Admin Icon.png|20px|link=Admin]] '''[[Admin]]''' - for basic user and network settings.<br />
<br />
*[[File:Manager Project Editor Icon.png|20px|link=Project Editor]] '''[[Project Editor]]''' - the visual editor used to create the user interfaces.<br />
<br />
*[[File:Manager File Manager Icon.png|20px|link=File Manager]] '''[[File Manager]]''' - provides access to all HSYCO's files, just like the standard file manager you have in your personal computer, only this one is fully Web-based and works directly on HSYCO Server's files.<br />
<br />
*[[File:Manager Log Viewer Icon.png|20px|link=Log Viewer]] '''[[Log Viewer]]''' - a real-time viewer of HSYCO's logs.<br />
<br />
*[[File:Manager Status Browser Icon.png|20px|link=Status Browser]] '''[[Status Browser]]''' - a real-time viewer of data points, variables and dynamic user interface attributes.<br />
<br />
*[[File:Manager System Monitor Icon.png|20px|link=System Monitor]] '''[[System Monitor]]''' - used to monitor several key hardware and operating system parameter of the HSYCO server.<br />
<br />
*[[File:Manager Wiring Editor Icon.png|20px|link=Wiring Editor]] '''[[Wiring Editor]]''' - an easy to use end-user logic and scenarios builder.<br />
<br />
*[[File:Manager Modbus Utility Icon.png|20px|link=Modbus Utility]] '''[[Modbus Utility]]''' - accessible if the Modbus I/O server is enabled<br />
<br />
*[[File:Manager KNX Utility Icon.png|20px|link=KNX Utility]] '''[[KNX Utility]]''' - accessible if the KNX I/O server is enabled<br />
<br />
*[[File:Manager BACnet Utility Icon.png|20px|link=BACnet Utility]] '''[[BACnet Utility]]''' - accessible if the BACnet I/O server is enabled<br />
<br />
*[[File:Manager LoRaWAN Utility Icon.png|20px|link=LoRaWAN Utility]] '''[[LoRaWAN Utility]]''' - accessible if the LoRaWAN I/O server is enabled<br />
<br />
*[[File:Manager SSH Tunnel Utility Icon.png|20px|link=SSH Tunnel Utility]] '''[[SSH Tunnel Utility]]''' - SSH reverse tunnel configuration<br />
<br />
*[[File:Manager Heos Utility Icon.png|20px|link=Heos Utility]] '''[[Heos Utility]]''' - accessible if the Heos I/O server is enabled<br />
<br />
<br />
You can switch between applications from any application using the [[File:Manager Switching Applications.png]] button on the top bar.<br />
<br />
Using a PC with a physical keyboard, you can also press '''[Ctrl] and [Shift]''' at the same time for fast switching between applications. An application selection panel appears until you keep the [Ctrl] key pressed; select the application you need by repeatedly pressing [Shift], then releasing [Ctrl].</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Manager&diff=9233Manager2020-10-14T10:22:24Z<p>Ulde: </p>
<hr />
<div>[[Category:System Architecture]]<br />
The Manager is the Web-based toolkit of applications that you will use to create customized graphic user interfaces and access all system's configuration files.<br />
<br />
<br />
{{note|The Manager runs on most modern Web browsers, including tablets like Apple’s iPad. It also runs on small screen devices like the iPhone or iPod touch, although a larger screen size is advisable for ease of use. Microsoft’s Internet Explorer versions 8 and older are not supported, and IE9 is not guaranteed to work, although it should in most cases.}}<br />
<br />
<br />
To access the Manager, enter the following URL in your Web Browser:<br />
<br />
<nowiki>https://192.168.0.50/hsycoserver/manager</nowiki><br />
<br />
[[File:Manager menu.png|240px|thumb|The Manager's application popup]]<br />
[[File:Manager About.png|200px|frame|<br />
Touch “about” in the bottom left corner to show HSYCO’s current version information.<br />
]]<br />
You need to authenticate using a PIN with administrator privileges to use the Manager.<br />
<br />
<br />
The Manager has several applications:<br />
<br />
*[[File:Manager Settings Icon.png|20px|link=Settings]] '''[[Settings]]''' - to configure the HSYCO system.<br />
<br />
*[[File:Manager Admin Icon.png|20px|link=Admin]] '''[[Admin]]''' - for basic user and network settings.<br />
<br />
*[[File:Manager Project Editor Icon.png|20px|link=Project Editor]] '''[[Project Editor]]''' - the visual editor used to create the user interfaces.<br />
<br />
*[[File:Manager File Manager Icon.png|20px|link=File Manager]] '''[[File Manager]]''' - provides access to all HSYCO's files, just like the standard file manager you have in your personal computer, only this one is fully Web-based and works directly on HSYCO Server's files.<br />
<br />
*[[File:Manager Log Viewer Icon.png|20px|link=Log Viewer]] '''[[Log Viewer]]''' - a real-time viewer of HSYCO's logs.<br />
<br />
*[[File:Manager Status Browser Icon.png|20px|link=Status Browser]] '''[[Status Browser]]''' - a real-time viewer of data points, variables and dynamic user interface attributes.<br />
<br />
*[[File:Manager System Monitor Icon.png|20px|link=System Monitor]] '''[[System Monitor]]''' - used to monitor several key hardware and operating system parameter of the HSYCO server.<br />
<br />
*[[File:Manager Wiring Editor Icon.png|20px|link=Wiring Editor]] '''[[Wiring Editor]]''' - an easy to use end-user logic and scenarios builder.<br />
<br />
*[[File:Manager Modbus Utility Icon.png|20px|link=Modbus Utility]] '''[[Modbus Utility]]''' - accessible if the Modbus I/O server is enabled<br />
<br />
*[[File:Manager KNX Utility Icon.png|20px|link=KNX Utility]] '''[[KNX Utility]]''' - accessible if the KNX I/O server is enabled<br />
<br />
*[[File:Manager BACnet Utility Icon.png|20px|link=BACnet Utility]] '''[[BACnet Utility]]''' - accessible if the BACnet I/O server is enabled<br />
<br />
*[[File:Manager LoRaWAN Utility Icon.png|20px|link=LoRaWAN Utility]] '''[[LoRaWAN Utility]]''' - accessible if the LoRaWAN I/O server is enabled<br />
<br />
*[[File:Manager SSH Tunnel Utility Icon.png|20px|link=SSH Tunnel Utility]] '''[[SSH Tunnel Utility]]''' - SSH reverse tunnel configuration<br />
<br />
*[[File:Manager Heos Utility Icon.png|20px|link=Heos Utility]] '''[[Heos Utility]]''' - accessible if the Heos I/O server is enabled<br />
<br />
<br />
You can switch between applications from any application using the [[File:Manager Switching Applications.png]] button on the top bar.<br />
<br />
Using a PC with a physical keyboard, you can also press '''[Ctrl] and [Shift]''' at the same time for fast switching between applications. An application selection panel appears until you keep the [Ctrl] key pressed; select the application you need by repeatedly pressing [Shift], then releasing [Ctrl].</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Manager&diff=9232Manager2020-10-14T10:20:58Z<p>Ulde: </p>
<hr />
<div>[[Category:System Architecture]]<br />
The Manager is the Web-based toolkit of applications that you will use to create customized graphic user interfaces and access all system's configuration files.<br />
<br />
<br />
{{note|The Manager runs on most modern Web browsers, including tablets like Apple’s iPad. It also runs on small screen devices like the iPhone or iPod touch, although a larger screen size is advisable for ease of use. Microsoft’s Internet Explorer versions 8 and older are not supported, and IE9 is not guaranteed to work, although it should in most cases.}}<br />
<br />
<br />
To access the Manager, enter the following URL in your Web Browser:<br />
<br />
<nowiki>https://192.168.0.50/hsycoserver/manager</nowiki><br />
<br />
[[File:Manager menu.png|240px|thumb|The Manager's application popup]]<br />
[[File:Manager About.png|240px|frame|<br />
Touch “about” in the bottom left corner to show HSYCO’s current version information.<br />
]]<br />
You need to authenticate using a PIN with administrator privileges to use the Manager.<br />
<br />
<br />
The Manager has several applications:<br />
<br />
*[[File:Manager Settings Icon.png|20px|link=Settings]] '''[[Settings]]''' - to configure the HSYCO system.<br />
<br />
*[[File:Manager Admin Icon.png|20px|link=Admin]] '''[[Admin]]''' - for basic user and network settings.<br />
<br />
*[[File:Manager Project Editor Icon.png|20px|link=Project Editor]] '''[[Project Editor]]''' - the visual editor used to create the user interfaces.<br />
<br />
*[[File:Manager File Manager Icon.png|20px|link=File Manager]] '''[[File Manager]]''' - provides access to all HSYCO's files, just like the standard file manager you have in your personal computer, only this one is fully Web-based and works directly on HSYCO Server's files.<br />
<br />
*[[File:Manager Log Viewer Icon.png|20px|link=Log Viewer]] '''[[Log Viewer]]''' - a real-time viewer of HSYCO's logs.<br />
<br />
*[[File:Manager Status Browser Icon.png|20px|link=Status Browser]] '''[[Status Browser]]''' - a real-time viewer of data points, variables and dynamic user interface attributes.<br />
<br />
*[[File:Manager System Monitor Icon.png|20px|link=System Monitor]] '''[[System Monitor]]''' - used to monitor several key hardware and operating system parameter of the HSYCO server.<br />
<br />
*[[File:Manager Wiring Editor Icon.png|20px|link=Wiring Editor]] '''[[Wiring Editor]]''' - an easy to use end-user logic and scenarios builder.<br />
<br />
*[[File:Manager Modbus Utility Icon.png|20px|link=Modbus Utility]] '''[[Modbus Utility]]''' - accessible if the Modbus I/O server is enabled<br />
<br />
*[[File:Manager KNX Utility Icon.png|20px|link=KNX Utility]] '''[[KNX Utility]]''' - accessible if the KNX I/O server is enabled<br />
<br />
*[[File:Manager BACnet Utility Icon.png|20px|link=BACnet Utility]] '''[[BACnet Utility]]''' - accessible if the BACnet I/O server is enabled<br />
<br />
*[[File:Manager LoRaWAN Utility Icon.png|20px|link=LoRaWAN Utility]] '''[[LoRaWAN Utility]]''' - accessible if the LoRaWAN I/O server is enabled<br />
<br />
*[[File:Manager SSH Tunnel Utility Icon.png|20px|link=SSH Tunnel Utility]] '''[[SSH Tunnel Utility]]''' - SSH reverse tunnel configuration<br />
<br />
*[[File:Manager Heos Utility Icon.png|20px|link=Heos Utility]] '''[[Heos Utility]]''' - accessible if the Heos I/O server is enabled<br />
<br />
<br />
You can switch between applications from any application using the [[File:Manager Switching Applications.png]] button on the top bar.<br />
<br />
Using a PC with a physical keyboard, you can also press '''[Ctrl] and [Shift]''' at the same time for fast switching between applications. An application selection panel appears until you keep the [Ctrl] key pressed; select the application you need by repeatedly pressing [Shift], then releasing [Ctrl].</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=File:Manager_About.png&diff=9231File:Manager About.png2020-10-14T10:20:13Z<p>Ulde: Ulde uploaded a new version of File:Manager About.png</p>
<hr />
<div></div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=File:Manager_menu.png&diff=9230File:Manager menu.png2020-10-14T10:18:56Z<p>Ulde: Ulde uploaded a new version of File:Manager menu.png</p>
<hr />
<div></div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=File:SSHTunnelUtility1.png&diff=9229File:SSHTunnelUtility1.png2020-10-14T10:15:26Z<p>Ulde: </p>
<hr />
<div></div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Modbus_Utility&diff=9228Modbus Utility2020-10-14T10:14:56Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager Modbus Utility Icon.png|class=appIcon]]<br />
The Modbus Utility is an application that allows you to easily setup repetitive polling read requests and monitor the performance and status of each request.<br />
<br />
Each read request is defined with a repeat interval in seconds. The Modbus Utility internal scheduler will try to repeat the execution of each request as close as possible to the preset interval. It will also sequence all requests to the same Modbus I/O server so they never overlap.<br />
<br />
You can optionally assign a variable to each request for conditional execution. If a variable is defined, it has to exist and have value “1” to activate the request polling. Requests that are not active are highlighted in grey.<br />
<br />
The optional "Error Tolerance" parameter is used to set the number of consecutive errors accepted before the Modbus error data point is set to report an error condition. The default is zero, so that even a single error will set the error data point. For example, setting the error tolerance to two means that up to two consecutive errors will be tolerated, and only the third consecutive error will set the error data point.<br />
<br />
The optional "Error Skip Interval" defines for how long the Modbus Utility should stop executing a Modbus request if an error occurs.<br />
<br />
<br />
[[File:ModbusUtility1.png|border|600px|center|Modbus Utility]]<br />
<br />
<br />
The Modbus Utility tracks the actual repeat interval and compares it with the defined interval. If the difference is more than 25% from the target value, the request is marked as “slow” and highlighted in yellow. The difference between defined and actual interval is reported in the “delta” field. <br />
<br />
Requests that return errors are also tracked and highlighted in red.<br />
<br />
The minimum and maximum response time is also tracked for each request, and displayed in the “min. time” and “max. time” fields in the requests list.<br />
<br />
You can reset the status, delta, minimum and maximum time using the “refresh” button.<br />
<br />
You can use filters to only show a subset of requests in the user interface. Entering a text in the search field will only show requests having a data point name that contains the search text. You can also filter by status, selecting slow, skipped, errors, or successful requests.<br />
<br />
{{note|Note that filters act globally, so if you set a filter all other users will also share the same view of the filtered list. Also note that, to reduce performance overhead, the status and performance data in the list of requests stops being updated after about 60 seconds of inactivity. This is also shared by all users. The refresh of requests’ data has no effect on the actual request scheduler, that runs independently and is never interrupted.}}<br />
<br />
<br />
[[File:ModbusUtility2.png|border|600px|center|BACnet utility.]]<br />
<br />
<br />
The Modbus Utility configuration is stored in a human readable file named modbus-scheduler.ini and located in HSYCO’s main directory. If you manually edit this file, it will be automatically reloaded within a few seconds after it is saved. In a high availability setup, the Modbus Utility is also automatically mirrored from the master to the slave server.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9227SSH Tunnel Utility2020-10-14T10:14:38Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility is an application that allows you to easily setup repetitive polling read requests and monitor the performance and status of each request.<br />
<br />
Each read request is defined with a repeat interval in seconds. The Modbus Utility internal scheduler will try to repeat the execution of each request as close as possible to the preset interval. It will also sequence all requests to the same Modbus I/O server so they never overlap.<br />
<br />
You can optionally assign a variable to each request for conditional execution. If a variable is defined, it has to exist and have value “1” to activate the request polling. Requests that are not active are highlighted in grey.<br />
<br />
The optional "Error Tolerance" parameter is used to set the number of consecutive errors accepted before the Modbus error data point is set to report an error condition. The default is zero, so that even a single error will set the error data point. For example, setting the error tolerance to two means that up to two consecutive errors will be tolerated, and only the third consecutive error will set the error data point.<br />
<br />
The optional "Error Skip Interval" defines for how long the Modbus Utility should stop executing a Modbus request if an error occurs.<br />
<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility]]<br />
<br />
<br />
The Modbus Utility tracks the actual repeat interval and compares it with the defined interval. If the difference is more than 25% from the target value, the request is marked as “slow” and highlighted in yellow. The difference between defined and actual interval is reported in the “delta” field. <br />
<br />
Requests that return errors are also tracked and highlighted in red.<br />
<br />
The minimum and maximum response time is also tracked for each request, and displayed in the “min. time” and “max. time” fields in the requests list.<br />
<br />
You can reset the status, delta, minimum and maximum time using the “refresh” button.<br />
<br />
You can use filters to only show a subset of requests in the user interface. Entering a text in the search field will only show requests having a data point name that contains the search text. You can also filter by status, selecting slow, skipped, errors, or successful requests.<br />
<br />
{{note|Note that filters act globally, so if you set a filter all other users will also share the same view of the filtered list. Also note that, to reduce performance overhead, the status and performance data in the list of requests stops being updated after about 60 seconds of inactivity. This is also shared by all users. The refresh of requests’ data has no effect on the actual request scheduler, that runs independently and is never interrupted.}}<br />
<br />
<br />
[[File:ModbusUtility2.png|border|600px|center|BACnet utility.]]<br />
<br />
<br />
The Modbus Utility configuration is stored in a human readable file named modbus-scheduler.ini and located in HSYCO’s main directory. If you manually edit this file, it will be automatically reloaded within a few seconds after it is saved. In a high availability setup, the Modbus Utility is also automatically mirrored from the master to the slave server.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9226SSH Tunnel Utility2020-10-14T10:14:30Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility is an application that allows you to easily setup repetitive polling read requests and monitor the performance and status of each request.<br />
<br />
Each read request is defined with a repeat interval in seconds. The Modbus Utility internal scheduler will try to repeat the execution of each request as close as possible to the preset interval. It will also sequence all requests to the same Modbus I/O server so they never overlap.<br />
<br />
You can optionally assign a variable to each request for conditional execution. If a variable is defined, it has to exist and have value “1” to activate the request polling. Requests that are not active are highlighted in grey.<br />
<br />
The optional "Error Tolerance" parameter is used to set the number of consecutive errors accepted before the Modbus error data point is set to report an error condition. The default is zero, so that even a single error will set the error data point. For example, setting the error tolerance to two means that up to two consecutive errors will be tolerated, and only the third consecutive error will set the error data point.<br />
<br />
The optional "Error Skip Interval" defines for how long the Modbus Utility should stop executing a Modbus request if an error occurs.<br />
<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|SSH Tunnel Utility.]]<br />
<br />
<br />
The Modbus Utility tracks the actual repeat interval and compares it with the defined interval. If the difference is more than 25% from the target value, the request is marked as “slow” and highlighted in yellow. The difference between defined and actual interval is reported in the “delta” field. <br />
<br />
Requests that return errors are also tracked and highlighted in red.<br />
<br />
The minimum and maximum response time is also tracked for each request, and displayed in the “min. time” and “max. time” fields in the requests list.<br />
<br />
You can reset the status, delta, minimum and maximum time using the “refresh” button.<br />
<br />
You can use filters to only show a subset of requests in the user interface. Entering a text in the search field will only show requests having a data point name that contains the search text. You can also filter by status, selecting slow, skipped, errors, or successful requests.<br />
<br />
{{note|Note that filters act globally, so if you set a filter all other users will also share the same view of the filtered list. Also note that, to reduce performance overhead, the status and performance data in the list of requests stops being updated after about 60 seconds of inactivity. This is also shared by all users. The refresh of requests’ data has no effect on the actual request scheduler, that runs independently and is never interrupted.}}<br />
<br />
<br />
[[File:ModbusUtility2.png|border|600px|center|BACnet utility.]]<br />
<br />
<br />
The Modbus Utility configuration is stored in a human readable file named modbus-scheduler.ini and located in HSYCO’s main directory. If you manually edit this file, it will be automatically reloaded within a few seconds after it is saved. In a high availability setup, the Modbus Utility is also automatically mirrored from the master to the slave server.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9225SSH Tunnel Utility2020-10-14T10:14:10Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility is an application that allows you to easily setup repetitive polling read requests and monitor the performance and status of each request.<br />
<br />
Each read request is defined with a repeat interval in seconds. The Modbus Utility internal scheduler will try to repeat the execution of each request as close as possible to the preset interval. It will also sequence all requests to the same Modbus I/O server so they never overlap.<br />
<br />
You can optionally assign a variable to each request for conditional execution. If a variable is defined, it has to exist and have value “1” to activate the request polling. Requests that are not active are highlighted in grey.<br />
<br />
The optional "Error Tolerance" parameter is used to set the number of consecutive errors accepted before the Modbus error data point is set to report an error condition. The default is zero, so that even a single error will set the error data point. For example, setting the error tolerance to two means that up to two consecutive errors will be tolerated, and only the third consecutive error will set the error data point.<br />
<br />
The optional "Error Skip Interval" defines for how long the Modbus Utility should stop executing a Modbus request if an error occurs.<br />
<br />
<br />
[[File:SSHTunnelUtility1.png|border|600px|center|Modbus utility.]]<br />
<br />
<br />
The Modbus Utility tracks the actual repeat interval and compares it with the defined interval. If the difference is more than 25% from the target value, the request is marked as “slow” and highlighted in yellow. The difference between defined and actual interval is reported in the “delta” field. <br />
<br />
Requests that return errors are also tracked and highlighted in red.<br />
<br />
The minimum and maximum response time is also tracked for each request, and displayed in the “min. time” and “max. time” fields in the requests list.<br />
<br />
You can reset the status, delta, minimum and maximum time using the “refresh” button.<br />
<br />
You can use filters to only show a subset of requests in the user interface. Entering a text in the search field will only show requests having a data point name that contains the search text. You can also filter by status, selecting slow, skipped, errors, or successful requests.<br />
<br />
{{note|Note that filters act globally, so if you set a filter all other users will also share the same view of the filtered list. Also note that, to reduce performance overhead, the status and performance data in the list of requests stops being updated after about 60 seconds of inactivity. This is also shared by all users. The refresh of requests’ data has no effect on the actual request scheduler, that runs independently and is never interrupted.}}<br />
<br />
<br />
[[File:ModbusUtility2.png|border|600px|center|BACnet utility.]]<br />
<br />
<br />
The Modbus Utility configuration is stored in a human readable file named modbus-scheduler.ini and located in HSYCO’s main directory. If you manually edit this file, it will be automatically reloaded within a few seconds after it is saved. In a high availability setup, the Modbus Utility is also automatically mirrored from the master to the slave server.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9224SSH Tunnel Utility2020-10-14T10:12:50Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility is an application that allows you to easily setup repetitive polling read requests and monitor the performance and status of each request.<br />
<br />
Each read request is defined with a repeat interval in seconds. The Modbus Utility internal scheduler will try to repeat the execution of each request as close as possible to the preset interval. It will also sequence all requests to the same Modbus I/O server so they never overlap.<br />
<br />
You can optionally assign a variable to each request for conditional execution. If a variable is defined, it has to exist and have value “1” to activate the request polling. Requests that are not active are highlighted in grey.<br />
<br />
The optional "Error Tolerance" parameter is used to set the number of consecutive errors accepted before the Modbus error data point is set to report an error condition. The default is zero, so that even a single error will set the error data point. For example, setting the error tolerance to two means that up to two consecutive errors will be tolerated, and only the third consecutive error will set the error data point.<br />
<br />
The optional "Error Skip Interval" defines for how long the Modbus Utility should stop executing a Modbus request if an error occurs.<br />
<br />
<br />
[[File:ModbusUtility1.png|border|600px|center|Modbus utility.]]<br />
<br />
<br />
The Modbus Utility tracks the actual repeat interval and compares it with the defined interval. If the difference is more than 25% from the target value, the request is marked as “slow” and highlighted in yellow. The difference between defined and actual interval is reported in the “delta” field. <br />
<br />
Requests that return errors are also tracked and highlighted in red.<br />
<br />
The minimum and maximum response time is also tracked for each request, and displayed in the “min. time” and “max. time” fields in the requests list.<br />
<br />
You can reset the status, delta, minimum and maximum time using the “refresh” button.<br />
<br />
You can use filters to only show a subset of requests in the user interface. Entering a text in the search field will only show requests having a data point name that contains the search text. You can also filter by status, selecting slow, skipped, errors, or successful requests.<br />
<br />
{{note|Note that filters act globally, so if you set a filter all other users will also share the same view of the filtered list. Also note that, to reduce performance overhead, the status and performance data in the list of requests stops being updated after about 60 seconds of inactivity. This is also shared by all users. The refresh of requests’ data has no effect on the actual request scheduler, that runs independently and is never interrupted.}}<br />
<br />
<br />
[[File:ModbusUtility2.png|border|600px|center|BACnet utility.]]<br />
<br />
<br />
The Modbus Utility configuration is stored in a human readable file named modbus-scheduler.ini and located in HSYCO’s main directory. If you manually edit this file, it will be automatically reloaded within a few seconds after it is saved. In a high availability setup, the Modbus Utility is also automatically mirrored from the master to the slave server.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Modbus_Utility&diff=9223Modbus Utility2020-10-14T10:12:01Z<p>Ulde: Undo revision 9222 by Ulde (talk)</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager Modbus Utility Icon.png|class=appIcon]]<br />
The Modbus Utility is an application that allows you to easily setup repetitive polling read requests and monitor the performance and status of each request.<br />
<br />
Each read request is defined with a repeat interval in seconds. The Modbus Utility internal scheduler will try to repeat the execution of each request as close as possible to the preset interval. It will also sequence all requests to the same Modbus I/O server so they never overlap.<br />
<br />
You can optionally assign a variable to each request for conditional execution. If a variable is defined, it has to exist and have value “1” to activate the request polling. Requests that are not active are highlighted in grey.<br />
<br />
The optional "Error Tolerance" parameter is used to set the number of consecutive errors accepted before the Modbus error data point is set to report an error condition. The default is zero, so that even a single error will set the error data point. For example, setting the error tolerance to two means that up to two consecutive errors will be tolerated, and only the third consecutive error will set the error data point.<br />
<br />
The optional "Error Skip Interval" defines for how long the Modbus Utility should stop executing a Modbus request if an error occurs.<br />
<br />
<br />
[[File:ModbusUtility1.png|border|600px|center|Modbus utility.]]<br />
<br />
<br />
The Modbus Utility tracks the actual repeat interval and compares it with the defined interval. If the difference is more than 25% from the target value, the request is marked as “slow” and highlighted in yellow. The difference between defined and actual interval is reported in the “delta” field. <br />
<br />
Requests that return errors are also tracked and highlighted in red.<br />
<br />
The minimum and maximum response time is also tracked for each request, and displayed in the “min. time” and “max. time” fields in the requests list.<br />
<br />
You can reset the status, delta, minimum and maximum time using the “refresh” button.<br />
<br />
You can use filters to only show a subset of requests in the user interface. Entering a text in the search field will only show requests having a data point name that contains the search text. You can also filter by status, selecting slow, skipped, errors, or successful requests.<br />
<br />
{{note|Note that filters act globally, so if you set a filter all other users will also share the same view of the filtered list. Also note that, to reduce performance overhead, the status and performance data in the list of requests stops being updated after about 60 seconds of inactivity. This is also shared by all users. The refresh of requests’ data has no effect on the actual request scheduler, that runs independently and is never interrupted.}}<br />
<br />
<br />
[[File:ModbusUtility2.png|border|600px|center|BACnet utility.]]<br />
<br />
<br />
The Modbus Utility configuration is stored in a human readable file named modbus-scheduler.ini and located in HSYCO’s main directory. If you manually edit this file, it will be automatically reloaded within a few seconds after it is saved. In a high availability setup, the Modbus Utility is also automatically mirrored from the master to the slave server.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Modbus_Utility&diff=9222Modbus Utility2020-10-14T10:08:44Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:SSH Tunnel Utility Icon.png|class=appIcon]]<br />
The SSH Tunnel Utility is an application that allows you to easily setup repetitive polling read requests and monitor the performance and status of each request.<br />
<br />
Each read request is defined with a repeat interval in seconds. The Modbus Utility internal scheduler will try to repeat the execution of each request as close as possible to the preset interval. It will also sequence all requests to the same Modbus I/O server so they never overlap.<br />
<br />
You can optionally assign a variable to each request for conditional execution. If a variable is defined, it has to exist and have value “1” to activate the request polling. Requests that are not active are highlighted in grey.<br />
<br />
The optional "Error Tolerance" parameter is used to set the number of consecutive errors accepted before the Modbus error data point is set to report an error condition. The default is zero, so that even a single error will set the error data point. For example, setting the error tolerance to two means that up to two consecutive errors will be tolerated, and only the third consecutive error will set the error data point.<br />
<br />
The optional "Error Skip Interval" defines for how long the Modbus Utility should stop executing a Modbus request if an error occurs.<br />
<br />
<br />
[[File:ModbusUtility1.png|border|600px|center|Modbus utility.]]<br />
<br />
<br />
The Modbus Utility tracks the actual repeat interval and compares it with the defined interval. If the difference is more than 25% from the target value, the request is marked as “slow” and highlighted in yellow. The difference between defined and actual interval is reported in the “delta” field. <br />
<br />
Requests that return errors are also tracked and highlighted in red.<br />
<br />
The minimum and maximum response time is also tracked for each request, and displayed in the “min. time” and “max. time” fields in the requests list.<br />
<br />
You can reset the status, delta, minimum and maximum time using the “refresh” button.<br />
<br />
You can use filters to only show a subset of requests in the user interface. Entering a text in the search field will only show requests having a data point name that contains the search text. You can also filter by status, selecting slow, skipped, errors, or successful requests.<br />
<br />
{{note|Note that filters act globally, so if you set a filter all other users will also share the same view of the filtered list. Also note that, to reduce performance overhead, the status and performance data in the list of requests stops being updated after about 60 seconds of inactivity. This is also shared by all users. The refresh of requests’ data has no effect on the actual request scheduler, that runs independently and is never interrupted.}}<br />
<br />
<br />
[[File:ModbusUtility2.png|border|600px|center|BACnet utility.]]<br />
<br />
<br />
The Modbus Utility configuration is stored in a human readable file named modbus-scheduler.ini and located in HSYCO’s main directory. If you manually edit this file, it will be automatically reloaded within a few seconds after it is saved. In a high availability setup, the Modbus Utility is also automatically mirrored from the master to the slave server.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=SSH_Tunnel_Utility&diff=9221SSH Tunnel Utility2020-10-14T08:52:04Z<p>Ulde: Created page with "Category:Manager class=appIcon The Modbus Utility is an application that allows you to easily setup repetitive polling read reques..."</p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager Modbus Utility Icon.png|class=appIcon]]<br />
The Modbus Utility is an application that allows you to easily setup repetitive polling read requests and monitor the performance and status of each request.<br />
<br />
Each read request is defined with a repeat interval in seconds. The Modbus Utility internal scheduler will try to repeat the execution of each request as close as possible to the preset interval. It will also sequence all requests to the same Modbus I/O server so they never overlap.<br />
<br />
You can optionally assign a variable to each request for conditional execution. If a variable is defined, it has to exist and have value “1” to activate the request polling. Requests that are not active are highlighted in grey.<br />
<br />
The optional "Error Tolerance" parameter is used to set the number of consecutive errors accepted before the Modbus error data point is set to report an error condition. The default is zero, so that even a single error will set the error data point. For example, setting the error tolerance to two means that up to two consecutive errors will be tolerated, and only the third consecutive error will set the error data point.<br />
<br />
The optional "Error Skip Interval" defines for how long the Modbus Utility should stop executing a Modbus request if an error occurs.<br />
<br />
<br />
[[File:ModbusUtility1.png|border|600px|center|Modbus utility.]]<br />
<br />
<br />
The Modbus Utility tracks the actual repeat interval and compares it with the defined interval. If the difference is more than 25% from the target value, the request is marked as “slow” and highlighted in yellow. The difference between defined and actual interval is reported in the “delta” field. <br />
<br />
Requests that return errors are also tracked and highlighted in red.<br />
<br />
The minimum and maximum response time is also tracked for each request, and displayed in the “min. time” and “max. time” fields in the requests list.<br />
<br />
You can reset the status, delta, minimum and maximum time using the “refresh” button.<br />
<br />
You can use filters to only show a subset of requests in the user interface. Entering a text in the search field will only show requests having a data point name that contains the search text. You can also filter by status, selecting slow, skipped, errors, or successful requests.<br />
<br />
{{note|Note that filters act globally, so if you set a filter all other users will also share the same view of the filtered list. Also note that, to reduce performance overhead, the status and performance data in the list of requests stops being updated after about 60 seconds of inactivity. This is also shared by all users. The refresh of requests’ data has no effect on the actual request scheduler, that runs independently and is never interrupted.}}<br />
<br />
<br />
[[File:ModbusUtility2.png|border|600px|center|BACnet utility.]]<br />
<br />
<br />
The Modbus Utility configuration is stored in a human readable file named modbus-scheduler.ini and located in HSYCO’s main directory. If you manually edit this file, it will be automatically reloaded within a few seconds after it is saved. In a high availability setup, the Modbus Utility is also automatically mirrored from the master to the slave server.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=File:Manager_SSH_Tunnel_Utility_Icon.png&diff=9211File:Manager SSH Tunnel Utility Icon.png2020-10-13T16:53:56Z<p>Ulde: </p>
<hr />
<div></div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Manager&diff=9210Manager2020-10-13T16:47:19Z<p>Ulde: </p>
<hr />
<div>[[Category:System Architecture]]<br />
The Manager is the Web-based toolkit of applications that you will use to create customized graphic user interfaces and access all system's configuration files.<br />
<br />
<br />
{{note|The Manager runs on most modern Web browsers, including tablets like Apple’s iPad. It also runs on small screen devices like the iPhone or iPod touch, although a larger screen size is advisable for ease of use. Microsoft’s Internet Explorer versions 8 and older are not supported, and IE9 is not guaranteed to work, although it should in most cases.}}<br />
<br />
<br />
To access the Manager, enter the following URL in your Web Browser:<br />
<br />
<nowiki>https://192.168.0.50/hsycoserver/manager</nowiki><br />
<br />
[[File:Manager menu.png|240px|thumb|The Manager's application popup]]<br />
[[File:Manager About.png|frame|<br />
Touch “about” in the bottom left corner to show HSYCO’s current version information.<br />
]]<br />
You need to authenticate using a PIN with administrator privileges to use the Manager.<br />
<br />
<br />
The Manager has several applications:<br />
<br />
*[[File:Manager Settings Icon.png|20px|link=Settings]] '''[[Settings]]''' - to configure the HSYCO system.<br />
<br />
*[[File:Manager Admin Icon.png|20px|link=Admin]] '''[[Admin]]''' - for basic user and network settings.<br />
<br />
*[[File:Manager Project Editor Icon.png|20px|link=Project Editor]] '''[[Project Editor]]''' - the visual editor used to create the user interfaces.<br />
<br />
*[[File:Manager File Manager Icon.png|20px|link=File Manager]] '''[[File Manager]]''' - provides access to all HSYCO's files, just like the standard file manager you have in your personal computer, only this one is fully Web-based and works directly on HSYCO Server's files.<br />
<br />
*[[File:Manager Log Viewer Icon.png|20px|link=Log Viewer]] '''[[Log Viewer]]''' - a real-time viewer of HSYCO's logs.<br />
<br />
*[[File:Manager Status Browser Icon.png|20px|link=Status Browser]] '''[[Status Browser]]''' - a real-time viewer of data points, variables and dynamic user interface attributes.<br />
<br />
*[[File:Manager System Monitor Icon.png|20px|link=System Monitor]] '''[[System Monitor]]''' - used to monitor several key hardware and operating system parameter of the HSYCO server.<br />
<br />
*[[File:Manager Wiring Editor Icon.png|20px|link=Wiring Editor]] '''[[Wiring Editor]]''' - an easy to use end-user logic and scenarios builder.<br />
<br />
*[[File:Manager Modbus Utility Icon.png|20px|link=Modbus Utility]] '''[[Modbus Utility]]''' - accessible if the Modbus I/O server is enabled<br />
<br />
*[[File:Manager KNX Utility Icon.png|20px|link=KNX Utility]] '''[[KNX Utility]]''' - accessible if the KNX I/O server is enabled<br />
<br />
*[[File:Manager BACnet Utility Icon.png|20px|link=BACnet Utility]] '''[[BACnet Utility]]''' - accessible if the BACnet I/O server is enabled<br />
<br />
*[[File:Manager LoRaWAN Utility Icon.png|20px|link=LoRaWAN Utility]] '''[[LoRaWAN Utility]]''' - accessible if the LoRaWAN I/O server is enabled<br />
<br />
*[[File:Manager SSH Tunnel Utility Icon.png|20px|link=SSH Tunnel Utility]] '''[[SSH Tunnel Utility]]''' - SSH reverse tunnel configuration<br />
<br />
*[[File:Manager Heos Utility Icon.png|20px|link=Heos Utility]] '''[[Heos Utility]]''' - accessible if the Heos I/O server is enabled<br />
<br />
<br />
You can switch between applications from any application using the [[File:Manager Switching Applications.png]] button on the top bar.<br />
<br />
Using a PC with a physical keyboard, you can also press '''[Ctrl] and [Shift]''' at the same time for fast switching between applications. An application selection panel appears until you keep the [Ctrl] key pressed; select the application you need by repeatedly pressing [Shift], then releasing [Ctrl].</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Release_Notes_3.7.0&diff=9209Release Notes 3.7.02020-10-13T16:43:07Z<p>Ulde: /* Manager */</p>
<hr />
<div><br />
[[Category: Release Notes]]<br />
<br />
== Server Updates ==<br />
*Aritech Comfort CSx75 I/O Server: added possibility to specify zone names<br />
*ARTECOOC I/O Server:<br />
**verbose log output of XML content posted to server and return data<br />
**session id support<br />
* AVIGILON I/O Server: new I/O Server for the Avigilon Control Center 7<br />
*CONTATTO I/O Server:<br />
**support of MODRHT<br />
**support of MODAM2<br />
**support of MODIGLASS, MODIGLASS3<br />
**support of MODLC firmware version 3.2<br />
**support of MODDALI firmware version 6.x<br />
**support of MCP counters<br />
**bus and modules fault detection<br />
*DOMINO I/O Server:<br />
**support of DFANA-M<br />
**support of DFDALI64<br />
**support of DFDIM<br />
**support of DFLS smart mode<br />
**support of DF4RI/DF4RIR virtual outputs<br />
**support of DF8RIT configuration with temperature input address enabled and temperature control disabled<br />
**support of position information and commands for DFTP, DFTP/I<br />
**support of DFCP counters<br />
**bus and modules fault detection<br />
**high availability support for redundant DFH installations<br />
*DUELUX I/O Server: new I/O Server for the Duemmegi DUELUX DLCP DALI-2 system controller<br />
*DUMMY I/O Server:<br />
**new "commandstate" option<br />
**new HTTP API: data points can now be set and read remotely with the /x/httpcall HTTP API<br />
**default number of lights, dimmers, automation is 0 (zero)<br />
*ELMO I/O Server: added support for Pregio, Vidomo (Villeggio series), Proxima and Titania panels<br />
*ESC/VP (EPSON) I/O Server:<br />
**improved protocol compatibility<br />
**added support for "middle" luminance level<br />
*Google Calendar I/O Server:<br />
**added capability of creating events<br />
**added "<cal_name>.json" and "<cal_name>.pre.json" datapoints<br />
*KILSEN I/O Server: new I/O Server for the KILSEN fire alarm panels<br />
*KNX I/O Server:<br />
**added support for DPT 29<br />
**added support for ETS5 export file<br />
**added "initreadinterval" I/O Server option<br />
**minor connection handling improvements<br />
*KSENIA I/O Server: new I/O Server for the KSENIA lares security panels<br />
*IFTTT I/O Server: new I/O Server for the IFTTT service<br />
*IONO I/O Server:<br />
**the IONO I/O Server is now "free". Using it doesn't decrease the number of available I/O servers<br />
**"minvariation" option now also applies to polling mode<br />
*IONO PI I/O Server:<br />
**added support for iono pi driver v1.3.0 and "wiegandbits" option<br />
**added support for local Iono Pi direct access<br />
*IONO PI Max I/O Server: new I/O Server for Sfera Labs Iono Pi Max<br />
*MasterBus I/O Server: new I/O Server for Mastervolt's MasterBus<br />
*Modbus I/O Server:<br />
**new "tcpmodbuseventunitid" option. When the Modbus TCP gateway option is enabled, setting tcpmodbuseventunitid to a Unit Id value (0 to 255) will redirect all TCP requests to that Unit Id to the ModbusEvent() callback instead of the Modbus RTU serial bus<br />
**high-availability: when "shutdown when inactive" is true and the HSYCO Server is inactive, all Modbus calls are affectively blocked, and return null. The TCP gateway is also blocked<br />
*MPOWER I/O Server: new I/O Server for the Ubiquity mFi mPower controllable power outlets<br />
*MQTTBROKER and MQTTCLIENT I/O Servers: new I/O servers add support for the MQTT protocol, client and broker<br />
*MyHome I/O Server: added support for HMAC authentication (for MyHome Server 1 and other recent OpenWebNet gateways)<br />
*NetworX I/O Server: added possibility to specify zone names<br />
*Paradox I/O Server: new "log0" data point<br />
*Philips Hue I/O Server: added support for Hue White devices<br />
*Protege I/O Server: new I/O Server for the ICT ProtegeGX security panel<br />
*Sonos I/O Server:<br />
**added support for SONOS firmware version 9<br />
**added datapoint "<player>.queue = <n>"<br />
**player state is now restored after a track is played via "<player>.play = <uri>" or via public announcement<br />
*SSH I/O Server:<br />
**the SSH I/O Server is now "free". Using it doesn't decrease the number of available I/O servers<br />
**new exec.<timeout> data point. Sets the command execution timeout in seconds; defaults to 30<br />
**new connection = close command: closes the SSH connection<br />
**new user = <user name> command; overrides the user configuration parameter<br />
**new password = <user password> command; overrides the password configuration parameter<br />
**new stdout=line option<br />
*Strato I/O Server:<br />
**added support for Strato Pi CAN and Strato Pi CM Duo<br />
**new cpu.temperature data point<br />
*System I/O Server: new data points:<br />
**cpu.model<br />
**cpu.revision<br />
**database.backup.time<br />
**database.backup.elapsed<br />
**database.backup.consolidation.time<br />
**database.backup.consolidation.elapsed<br />
**database.backup.consolidation.status<br />
**database.defrag.time<br />
**database.defrag.elapsed<br />
**database.update.elapsed<br />
**hsyco.version<br />
**java.version<br />
**os.version<br />
*Tecnoalarm I/O Server: added data point "log0"<br />
*Telegram I/O Server: camera images and generic image files can now be sent via Telegram messages<br />
*WOLF8ACCESS I/O Server: new I/O Server for the Wolf Safety "8 ACCESS" access control system<br />
*WXONLINE I/O Server:<br />
**data source changed from Yahoo to Open Weather Map<br />
**increased number of forcasted days from 2 to 5<br />
**location can be set to latitude and longitude, as well as with the location id<br />
*YAMAHAEC I/O Server: new I/O Server for the Yamaha Extended Control communication protocol<br />
**location can be set to latitude and longitude, as well as with the location id<br />
*new embedded Natural Language Processor to support speech and free format text commands<br />
*Cameras: cameras with static image sources are now supported. If Camera.<id>.Type is set to "static", a single HTTP request is sent to acquire the image when a CAMERAREC action is executed. The live camerapanel display will not trigger HTTP requests to the source, but show the last recorded image. Events are grouped per day. For static cameras only, a variable name (starting with $) can be set in the configuration instead of the URL in order to allow dynamic URLs<br />
*Data loggers: new HourConsolidationFactor option for data loggers. Splits hourly consolidated data in multiple sub-intervals (e.g. HourConsolidationFactor = 4 leaves data grouped at minutes 0, 15, 30, 45 after hour consolidation)<br />
*Program timers: if the program timer id starts with $, then the server will also automatically set a variable, with a name equal to the program timer's id, to the remaining number of seconds. Note that the variable is not guaranteed to be updated at every second, as some updates may be skipped due to timing constraints.<br />
*Communication ports, serial gateways configuration: it is now possible to define a custom read timeout to override the 2 seconds default. Set using CommPort.<id>.Params = <timeoutmillis> in hsyco.ini<br />
*Access control: new trustedUsers option: comma separated list of user IDs that are always considered trusted, even when connected from outside of the trusted network. Trusted users connecting to HSYCO are subject to the time-out defined in KeysTrustedValidityHours<br />
*Location Services: improved compatibility with Ubiquiti UniFi access points<br />
*New Database options for scheduled data structure optimization: DatabaseCompactDay, DatabaseCompactHour, DatabaseCompactMinute, DatabaseCompactEnable<br />
*New Database option for backup consolidation (integrity verification and compression), with automatic recovery: DatabaseBackupConsolidation<br />
*The Datalogger import API (csvread and cvsreadover) can now also receive a CSV string directly instead of a file path<br />
*when TimeAutoUpdate is enabled, NTP synchronization is performed every hour (it was once a day, at 00:30 local time, in previous versions)<br />
*on Linux systems with the Intel U1900 CPU, HSYCO will check the system clock source at startup, and set it to "acpi_pm" if different<br />
*High Availability:<br />
**improved client handover between primary and secondary servers<br />
**new hsyco.ini synchronization feature: hsyco.slavediff.ini file contains changes to hsyco.ini to be applied to the slave version of hsyco.ini. It can contain new properties, existing properties with different values, or existing properties with no value, to remove properties from the master's hsyco.ini file. The hsyco.slavediff.ini should be updated from the master only, even if it is only used by the slave<br />
**new haDatabaseSlaveSync hsyco.ini property: haDatabaseSlaveSync = true (defaults to false) restores the slave database, restarting HSYCO, when a new database backup is synced from the master. DatabaseBackupCosolidation must be true to enable database synchronization<br />
<br />
== EVENTS ==<br />
*new LOGIN <userid> transient event<br />
*new LOGOUT <userid> transient event<br />
*new LOCATIONBEACON event keyword. Supports "LOCATIONBEACON userid = zone" and "LOCATIONBEACON zoneid" event conditions<br />
*new NLP action keyword<br />
*MAIL action: you can now optionally specify the number of frames back from the defined number of seconds since last recording. The new format is: “cam:cameraname[:seconds_back[:frames_back]]”<br />
*new format modifiers for $SUNRISE$ and $SUNSSET$ predefined variables, $SUNRISE:HMS$ and $SUNSSET:HMS$<br />
*AUDIO action: new audio destination format, web@<channel>. <channel> can be a project name or an arbitrary name assigned to an audio channel set using the "audiochannel" project attribute<br />
<br />
== Java API ==<br />
*new loginEvent(String address, String session, String userid) callback<br />
*new logoutEvent(String address, String session, String userid, boolean lock) callback<br />
*new LocationBeaconEvent(String session, String address, String userid, String zone, String distance) callback<br />
*new nlp(String text) command<br />
*new uiLink(String source, String target) command<br />
*sendMail() command: you can now optionally specify the number of frames back from the defined number of seconds since last recording. The new format is: “cam:cameraname[:seconds_back[:frames_back]]”<br />
*ioGet(String id): ioGet("*") returns the ids of all data points in a comma-separated list<br />
*varGet(String name): varGet("*") returns the names of all variables in a comma-separated list. Variable names are upper case<br />
*Modbus: all commands now also accept <ip>:<port number> to connect to Modbus TCP servers with a non-standard port number<br />
*audioPlay() command: new audio destination format, web@<channel>. <channel> can be a project name or an arbitrary name assigned to an audio channel set using the "audiochannel" project attribute<br />
<br />
== JavaScript API ==<br />
*new loginEvent(address, session, userid) callback<br />
*new logoutEvent(address, session, userid, lock) callback<br />
*new LocationBeaconEvent(session, address, userid, zone, distance) callback function<br />
*new nlp(text) command<br />
*new uiLink(source, target) command<br />
*sendMail() command: you can now optionally specify the number of frames back from the defind number of seconds since last recording. The new format is: “cam:cameraname[:seconds_back[:frames_back]]”<br />
*ioGet(id): ioGet("*") returns the ids of all data points in a comma-separated list<br />
*varGet(name): varGet("*") returns the names of all variables in a comma-separated list. Variable names are upper case<br />
*Modbus: all commands now also accept <ip>:<port number> to connect to Modbus TCP servers with a non-standard port number<br />
*audioPlayFile() and audioPlayText() commands: new audio destination format, web@<channel>. <channel> can be a project name or an arbitrary name assigned to an audio channel set using the "audiochannel" project attribute<br />
<br />
== GUI Updates ==<br />
*new "html" object<br />
*new "shape" object<br />
*UI objects redirect variables support<br />
*new page and popup "focus" attribute. Specifying an id of an object contained in the page, it will gain focus immediately if visible, and every time the page is opened<br />
*button, 3button, buttonicon, buttonimage now have an id and uiset attributes: pos, visible, label, blink, opacity, rotation, confirm<br />
*new "confirm” attribute for user and button ui objects. If “true” user has to press a second time to send the command<br />
*fullscreen support for datalogger and camerapanel objects:<br />
**new "fullwindow" url query option<br />
**fullwindow=true|false project's UI attribute: set to true to expand inside the browser's window instead of actually going fullscreen<br />
**pinch to zoom on camerapanel<br />
*datalogger object:<br />
**multi-year view in browser mode<br />
**click the values legends to hide/unhide the corresponding graph<br />
**set download="true" enable local download of datalogger browser data in CSV format<br />
**new "csvseparator" attribute<br />
*scale project attribute and URL option keyword: new "auto" and "fit" options. When scale=auto the user interface is automatically expanded to fill the available browser area. When scale=fit, the user interface is expanded as with auto, but also reduced if the available browser area is smaller than the original project's size. The scale attribute can be set as a static project's directive, a URL keyword, or dynamically with UISET<br />
*new "audiochannel" project attribute<br />
*gohome=N project attribute and URL option keyword: after N seconds of inactivity, go to the menu page, or the page set with the page=<page name> URL option<br />
*PIN and PUK can now be pasted from the clipboard<br />
*camerapanel object:<br />
**added support for for pinch to zoom on camerapanel object when in fullscreen mode in the iOS and Android apps<br />
**single frame email replaced with local download<br />
**redesigned download popup and app download support<br />
**reduced height of playback timeline clickable area<br />
*input object: new cssstyle attribute<br />
*link, imagelink objects:<br />
**the link attribute can be dynamically set with UISET<br />
**link objects now can receive focus<br />
*scheduler object: new groups attribute allows changing the list of schedule groups names via UISET<br />
*video object: new "controls" attribute<br />
*other minor graphical changes to the standard skins<br />
*in previous versions, the automatic web UI reload was triggered by changes in any file under the www directory or on HSYCO startup. Starting from this version, HSYCO startup will not trigger the reload if no www files are changed. Reload will also occur if www files under the plugins directory are changed<br />
<br />
== Manager ==<br />
*new LoRaWAN configuration utility<br />
*new SSH tunnel configuration utility<br />
*added support for iBeacon configuration in Location Services Settings<br />
*Log Viewer filter now accepts "strings delimited by quotes", single quotes, "escaped\"quotes\""<br />
*Project Editor:<br />
**new object alignment tools<br />
**project’s scale parameter now specified through a select field<br />
**new "go to page" button on link objects, and other usability improvements<br />
**new QR Code tool<br />
*Modbus Utility:<br />
**new skip on error interval option: skip reading for the specified amount of time after an error<br />
**new error tolerance option: number of consecutive errors accepted before the error data point is triggered<br />
**improved user interface<br />
*other usability improvements, including resizable attributes input fields, and copy to clipboard for Log Viewer and Status Browser<br />
<br />
== Bug Fixes ==<br />
*improved compatibility with Debian 9 (Stretch) systems:<br />
**high availability active IP hand-over<br />
**LAN IP address configuration change: old address remained active until reboot<br />
**system clock synchronization and network time update support<br />
*improved serial port reliability on Linux (x86) systems<br />
*fixed a bug that could cause the corruption of cameras recording indexes<br />
*improved handling of cameras connections errors<br />
*when the Java runtime version is >= 1.7 symbolic links under the HSYCO root are now handled as normal, valid paths<br />
*High Availability:<br />
**sync of zero-length files generated an exception message<br />
**hsyco.jar could fail to synchronize on slave if listed in the AutoKillFiles configuration parameter on the slave<br />
*Contatto I/O Server: fixes to the MODDALI ballast 1 status data point<br />
*Domino I/O Server: "modulefault" data point of individual modules not working with DFH gateways<br />
*Cradlepoint I/O Server: fixed error parsing data points returning long values<br />
*HSYCO Remote I/O Server:<br />
**data points with the '*' character in the value string couldn't be written to the remote server<br />
**the I/O Server could time out during initialization on a very large local database<br />
*IONO I/O Server: port configuration option was ignored<br />
*Modbus I/O Server: fixed a bug causing conversion errors when reading 4 consecutive registers with "longx" or "ulongx" data types<br />
*Paradox I/O Server: minor fixes<br />
*SMTPSERVER I/O Server: fixed a bug that caused messages without a "Content-type" header in the body to be ignored<br />
*Tecnoalarm I/O Server: pass phrases with upper case characters were not supported<br />
*Tecnofire I/O Server:<br />
**log and lastlog UISet ID fixed<br />
**extended communication wait time after read errors<br />
*Telegram I/O Server: a connection error during the I/O server startup sequence could cause it to wait indefinitely and never connect<br />
*API:<br />
**fixed null return value in the following JavaScript command functions: ioGet, readComm, slimCommand, uiGet, uiSessionGet, urlGet, urlPost<br />
**fixed bug in LocationEvent(mac, ip, zoneId) JavaScript callback function<br />
**fixed return value in UserCommand Javascript callback function (index.js)<br />
*GUI:<br />
**menu or pages gestures and scope declarations could propagate to all pages following the declaration in index.hsm<br />
**chart object: valuerange set using a "." separator caused a client-side JavaScript error<br />
**all link objects: fixed relative URL opening in new tab<br />
**linkmini, linkmicro objects: fixed dynamic label attributes<br />
**link object to external URLs not working correctly on iOS and Android app<br />
**panel object: setting height via UISET did not work<br />
**rgb object: pressing off could fail to send the off command in some circumstances<br />
**scheduler object: group names incorrectly set to lower case on HSYCO restart or scheduler.ini reload<br />
**minor fixes to camera objects<br />
*Manager:<br />
**line object didn’t move correctly pressing the arrow keys<br />
**project's page copy & paste not working<br />
**text editor did not recognize event files in plugins directories</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Log_Viewer&diff=9208Log Viewer2020-10-13T16:36:49Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager Log Viewer Icon.png|class=appIcon|The '''Log Viewer''' icon]]<br />
The Log Viewer application shows a scrollable live view of the last 1000 lines from the daily log file.<br />
<br />
<br />
[[File:Manager Log Viewer.png|center|800px]]<br />
<br />
<br />
The tool bar at the bottom lets you filter log lines searching for a text, or to exclude a text in order to de-clutter the log. Type multiple words to select or exclude all lines that contain at least one of the words. Enclosing multiple words inside quotes will match the full text. Quotes can be escaped with the backslash escape character.<br />
<br />
Touch “search” to toggle between text search and exclude mode.<br />
<br />
Touch “pause” to stop updating the viewer, then press again to restart. New log lines written while paused will not appear in the viewer, but will still be saved in the log file.<br />
<br />
Touch “clear” to clear the log window, or "copy" to copy the whole log text to the clipboard.<br />
<br />
You can also temporarily select which log levels you want, without having to modify the hsyco.ini main configuration file.<br />
<br />
Touch “verbose”, “events” or “user” to enable or disable the log levels. Changing log levels also affects what other users will see in the Log Viewer as well as what is actually written in the log file. Changes to the log levels will return to the preset configuration after you leave the Log Viewer application.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=Log_Viewer&diff=9207Log Viewer2020-10-13T16:33:43Z<p>Ulde: </p>
<hr />
<div>[[Category:Manager]]<br />
[[File:Manager Log Viewer Icon.png|class=appIcon|The '''Log Viewer''' icon]]<br />
The Log Viewer application shows a scrollable live view of the last 1000 lines from the daily log file.<br />
<br />
<br />
[[File:Manager Log Viewer.png|center]]<br />
<br />
<br />
The tool bar at the bottom lets you filter log lines searching for a text, or to exclude a text in order to de-clutter the log. Type multiple words to select or exclude all lines that contain at least one of the words. Enclosing multiple words inside quotes will match the full text. Quotes can be escaped with the backslash escape character.<br />
<br />
Touch “search” to toggle between text search and exclude mode.<br />
<br />
Touch “pause” to stop updating the viewer, then press again to restart. New log lines written while paused will not appear in the viewer, but will still be saved in the log file.<br />
<br />
Touch “clear” to clear the log window, or "copy" to copy the whole log text to the clipboard.<br />
<br />
You can also temporarily select which log levels you want, without having to modify the hsyco.ini main configuration file.<br />
<br />
Touch “verbose”, “events” or “user” to enable or disable the log levels. Changing log levels also affects what other users will see in the Log Viewer as well as what is actually written in the log file. Changes to the log levels will return to the preset configuration after you leave the Log Viewer application.</div>Uldehttps://wiki.hsyco.com/3.7/index.php?title=File:Manager_Log_Viewer.png&diff=9206File:Manager Log Viewer.png2020-10-13T16:31:19Z<p>Ulde: Ulde uploaded a new version of File:Manager Log Viewer.png</p>
<hr />
<div></div>Ulde