Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Francois Smuts

Member
  • Posts

    6
  • Joined

  • Last visited

About Francois Smuts

Profile information

  • Gender
    Male
  • Country
    South Africa
  • Gateway/s
    Home Center 2
    Home Center Lite

Contact

  • Website URL
    www.elvey.co.za

Recent Profile Visitors

74 profile views

Francois Smuts's Achievements

Newbie

Newbie (1/8)

0

Reputation

  1. Just checked, our demo room is still on ver 3.2... --[[ Name: HC2_DSCengine Date: 2018-03-11 19:12 CET Author: Per-Olov Sjoholm E-mail: [email protected] --]] DSCengine_version = "3.2"
  2. You have done a great job with DSCengine, we use it in demo room... however at my house I use the Envisalink plugin
  3. HC2_DSCengine, an innovative response to overcoming the current Envisalink plugin issues, well done... I must admit, I still prefer the Envisalink Plugin because device/zone status displays in rooms are inline with Z-wave motion detectors. I do however suggest that Fibaro looks at DSCengine in order to improve on the Envisalink plugin as all the hard work has been done for them. The question, is what will it take to motivate Fibaro to improve on the existing Envisalink plugin. For most Fibaro installers/users it would be is easier to create VDs based on plugins, than having to code a complete virtual interface in LUA. PS - For those interested in the DSC PowerSeries Neo with its TL280 IP communicator, well a plugin would be the only option from DSC's (Tyco) perspective. Access to the relative IP protocol come with a nondisclosure agreement.
  4. The existing Envisalink plugin is 80% there to create a simple Virtual Device for control and status monitoring of DSC and Honeywell (Ademco) Security Systems. All that’s required is to sort a few bugs and add some basic device options for Partitions and Zones. Device Options required: 1) Partitions and Zones hide option. 2) Zone Sensor Type selection option such as Motion, Window and Door (zones are currently fixed as Motion Sensors). 3) Option to change Zone icons. Bugs: 1) Partitions arm() actions does not work. 2) Partitions disarm() actions does not work. 3) Partition “ready” property does not work. 4) Partition “entryTime” property does not work. Additional feature required: 1) Partition armed property require additional parameters to reflect “Stay” and “Night” arming modes (current: “0” = Disarmed & “1” = Armed). 2) Zone bypass() action to be added. 3) Zone bypass status property to be added. 4) Control of Alarm system’s outputs (PGMs) with controlled device type association such as with Z-wave switches. 5) Sending of a Command string, consisting of a combination of the panel’s kepad keystrokes, to simulate user control.
  5. With regard to adpostelnicu's comment " Now after I've explained this I hope you better understand why we will not have RTSP support implemented in the near future." Disappointing response. As mentioned before, IP CCTV manufactures are moving away form mjpeg support........
  6. Agree, rstp support is needed urgently. mjpg support is being phased out by most leading IP camera manufacturers.
×
×
  • Create New...