Camect Integration with IPIO

EyeSpyFX are excited to announce that Camect AI systems are now integrated with the IPIO system of devices and mobile apps.

Camect make AI security camera hubs that feature world beating video analytics. Accuracy of detection events is close to 99%.

Camect AI detection hub

Camect AI detection hub

IPIO can be used to arm/disarm the video analytics on a whole system basis using just one IPIO switch or on a per zone basis using up to four IPIO switches. Multiple cameras can be armed or disarmed per zone.

Normally IPIO units communicate with AI video analytics camera systems using wired IO, but with this integration the need for IO connections is negated. IPIO units can now be connected directly to Camect hubs using a software integration. This software integration reduces the install time and overall system complexity.

• Easy, fast install – no IO wires required
• Two levels of user preferences
• Super accurate detections with app based arm and disarm control
• Multi camera zone arm/disarm
• Input and schedule based rules
• Full log system
• Instant event notifications

Arm Camect AI systems camera zone by zone

Arm Camect AI systems camera zone by zone

Event Logs that are legible

Event logs in Security Camera and Access Control Systems are notoriously hard to read. There are too many events, the individual logs are poorly phrased and badly parsed, you need to wade through lots of data that has no real information value to find the item you are looking for. Looking through logs on a mobile device is even more difficult as the length of the line is longer than the width of the screen. There are lots of good technical reasons why event logs are complex and the difficulty in reading it all is to some extent unavoidable. In the IPIO app we have tackled this problem and come up a with a design that makes the complexity a little easier to read.

Organised per day and collapsible
We decided that a day was the right unit to look at logs in. There are reasons when you need to look at logs over a week, but they are more extreme and we decided against including the UI overhead of that option. Each day can be easily expanded and collapsed.

The logs follow the naming preferences the user has set
Every system has the default names it gives to entities such as cameras, doors, sensors, buttons. In many event log systems these names carry through to the logs. This has the advantage of being always true in a system sense but the disadvantage of being difficult to interpret.
For example: Node1 UnSet by UserID AX456.
We decided against that and use the User named buttons and actions.
For example: Kitchen Camera, On, by Joe.

Colour coded
We use colour in a way that increases legibility. Green indicates armed, red indicates disarmed, blue indicates a sensor reset and white indicates a trigger event.

Short
Our log entries are as short as possible. We cannot always manage to get the whole event log into just one line and need to carriage return but we try and keep the event log both meaningful and as short as possible.

Time of day is parsed as stand out feature
We use time as the main index within the day view. Event times are parsed out and made clear and stand alone.

These careful design considerations make IPIO logs easy and fast to read, improving the experience for the user and also helping the process of enabling the user to use the data as information that people can base action on.

IPIO Event Logs

IPIO Event Logs

IPIO App Configuration

IPIO is a universal I/O device and corresponding mobile app. By “universal” we mean that it can be used to monitor and switch any electronic/electrical device. Our expertise is in the Security Industry and typically IPIO is used to switch CCTV systems, Alarm systems, PIR systems, door and gate locks, security lights, audio warnings, etc. However, it could be used to switch a washing machine. Although none of our customers have used IPIO to control a washing machine many have found interesting and surprising uses for IPIO. To support “universality” the labels on each output button are editable. Button names and action status can be changed to suit the device under control.

Labels on buttons
The default label on a button is “Output (1234), Armed/Disarmed”. This can be changed to give more meaningful notations (Settings/Name/On Status/Off Status). The notations are also reflected in the event logs and app notifications.Screenshot 2022-03-02 at 14.39.40

Only display active buttons
The default set up for an IPIO unit is to display 4 Outputs and no Input ports. This can be changed to suit the individual set up. In many IPIO installations not all four Output ports are used. If a button is not being used it can be removed from the app. This creates a cleaner set up for the user.

Inputs
Input tiles are by default not displayed. They can be made active in the Settings area. Inputs 1-4 are for physical inputs that correspond to the input ports inside the IPIO box. These can be wired to door sensors, intruder alarms or any other device. Inputs 5-8 are virtual inputs that can be used with Sigfox input devices.

Screenshot 2022-03-02 at 14.46.37

Remote gate sensors

EyeSpyFX are proud to announce integration with IOTA door/gate sensors and IPIO mobile app. IOTA door/gate sensors and IPIO are ideal for:

  • gates on remote building sites
  • farm buildings
  • the access hatch to CCTV tower units
  • equipment rooms in harbours, boat yards and other remote locations
  • boat hatches

The IOTA door/gate sensor is a robust device suitable for outdoor deployment in remote locations. It uses the SIGFOX network. Sigfox is a ZeroG mobile network that transmits very small pieces of data. The sensor has its own power supply and network connectivity. Open/close events are logged on the IPIO mobile app and a notification is sent to the user. Battery status, signal strength and postion state are displayed in the App input tile.

  • Robust build quality
  • Excellent UK and Ireland Sigfox network coverage
  • 10 year battery life
  • Event logs shown in IPIO app
  • Event notifications sent to app
  • Battery and Signal strength indicators in app
  • Event rules can trigger IPIO actions such as lights on or warning siren
  • No more running wires to difficult to reach door and gates
boathouse2

IOTA remote sensor and IPIO: ideal for locations with no power or internet

Gate Sensor

Robust Gate Sensor

ipioapp

IPIO app showing Sensor tile and door and CCTV controls

IPIO app showing log page

IPIO app showing log page

Sigfox coverage

Sigfox coverage in UK and Ireland

Contact info@eyespyfx.com for further information.

 

IPIO User levels

The IPIO system has a number of different user levels each designed to suit different roles. There are levels for:

  • Site owner/managers
  • Ordinary users and site visitors
  • System Installers
  • ARC operators

Site Owner/Managers
This person will use the mobile app and be the primary user of the system. They are able to arm/disarm, open/close the system. They can see input status. They view event logs and they will receive notifications when an event occurs (for example: if someone arms the CCTV). They can name an output or input. They can decide how the app should appear selecting which outputs and inputs should be displayed. Owner/Managers can invite Ordinary Users to join the site.

Ordinary Users and site visitors
These app users can arm/disarm a system. They can also see input status. They cannot see logs and will not receive event notifications.

System Installers
Installer level app users can do everything a Site/Owner can do plus they can set up input and output rules. Installers can also add Virtual Outputs such as Camect devices and virtual Inputs such as Sigfox devices.

Portal Users
Portal Users are normally ARC operators. This is the Super User level of the IPIO system. Portal Users have access to a powerful web view that allows full system access suitable for administration of all IPIO units under management of that ARC.

Feature Ordinary User Owner/Manager Installer Portal (web pages)
Add IPIO device
Remove IPIO device
Arm/Disarm
View Logs
View Users
Remove Users
Remove Managers/Installers
Add Users
Copy Users to a new IPIO device
Change User Role
Give Installer Access
Set Output Name
Set Output Status
Set Output Notifications Active
Make Output visible on main control screen
Set Input Name
Set Input Status
Set Input Notifications Active
Make Input visible on main control screen
Set/edit Output rules
Set/edit Input rules
Set/edit Schedules
Set edit Virtual Outputs (Camect)
Set edit Virtual Inputs (Sigfox devices)
View UIPIOID
Clear Logs
Suspend a device
Change IPIO ownership tag
Change Users role
Name an IPIO device on the portal
Set reminders (Custom feature)

For further information about IPIO please contact info@eyespyfx.com

IPIO Management Portal Update

The IPIO portal is used by Monitoring Centre (ARCs) and Installers to manage IPIO units.

We have just completed an upgrade to the Portal bringing even more power and features to monitoring centre professionals. Here are some of the key new features:

Web Interface

  • Cleaner, easier to read at a glance
  • Improved typography and spacing throughout
  • IPIO Inputs and Outputs in a pop up window just like in the app
  • Auto Refresh every 15 seconds
  • Hide offline units from the list of units
  • Pin states have been re-drawn to give a cleaner appearance
layerednewipio2530

Figure 1: The IPIO Portal offers comprehensive management features for IPIO units

webuiIPIO

Figure 2: WebUi for IPIO Controls matched with App rendering

Micro notifications

  • New notification alarms for online / offline events
  • Hide notifications from appearing
event_tray

Figure 3: Event tray for online/offline events

Event logs

    • Comprehensive event logs
    • New “change to schedule” event added
    • Colour coded easy to read event list
    • Transfer users from one unit to another
eventlogs

Figure 4: Cleaned up event logs

Users

  • Notification tray added so you can see missed online/offline events
  • Change a user’s role feature added
  • Can change portal password direct from the portal when logged in
usersettings

Figure 5: Move users from one unit to another

 

Team Matters

We are pleased to announce that Sean Duffy will be joining our team of Security Automation developers. Sean is not exactly new to EyeSpyFX. He spent a student placement year with us in 2018/9. He then worked with us part time while he finished his degree studies. He graduated in 2020 with first class honours in Computer Games Development from the University of Ulster. During his final year he won a prestigious prize for best Mobile Technologies project. Sean also has a keen interest in electronics and cars. He is an excellent all round “maker” and is a perfect fit for EyeSpyFX. We are delighted he is now joining us in a full time role.

Welcome aboard Sean.

seand

 

 

New IPIO rules feature

IPIOrulesIPIO has a new programmable rules feature. (IPIO app v3.03 onwards)

Using the rules feature the app can be programmed to carry out an action based on an input event. For example: If the gate opens (input 1) then disarm alarm (output 1) and switch on lights (output 2).

The rules feature is ideal for building up sophisticated I/O behaviours on monitored sites.

The IPIO rules feature does not appear to all users. It is a powerful feature and only appears to users who have Portal Access. This enables site managers working in the ARC to create rules while not burdening end users with user interface elements that they will not use.

IPIO rules are based on “if that then this” type logic. If input 1 is triggered, then output 2 will arm.

There is a rules simulator feature that visually models the rule. Outputs can be matched, flipped or oppose an Input state.

There is a second section to rules (not shown above) that allows multiple outputs to follow each other. For example, if Output 2 is armed, then arm Output 3.

We would be pleased to hear about your applications based on rules, and we look forward to making the rules section even more powerful and responsive and intelligent in due course.

Eight observations about IoT app development that have become our values.

We began working on IoT and security camera applications in 2002. Over the years we have made some observations that have become our development values.

Intelligent
An app is only part of an IoT system. It is the part of the system that the user touches and it is often the only way that the users experience the system. Behind the App screen there are appliances, cloud services, computation, storage, API’s, connectivity, time, etc. All of these elements combine to give the end user an intelligent effect and control rendered seamlessly in the mobile app. We think of the intelligence of the app in the context of the whole system performance.

Comprehensible
A powerful complex app cannot always be simple and easy to use but it must be comprehensible. IoT apps can be hard to understand because the app provides just a limited window on a partially hidden system. IoT apps often involve actions that occur automatically. This can disorientate a user. We work hard to make unavoidably complex merged physical and computational environments comprehensible.

Agency
Apps can be agents working on your behalf. The user interface is a place where you set up rules and adjust preferences. Once set up the app should run semi independently. When something happens in the system that requires human attention the app should bring the issue to the user’s attention setting out the causes and possible remedies.

Aware
An app should remember what you did in a particular context – and help you achieve that outcome again if the context is similar

Secure
We stand over all our code. There are no black boxes of unknown code components.  All storage is encrypted. All communications are encrypted and authenticated.

Fast
We count the clicks. Each click is valued. The UI time is measured. The server and appliance response times are also measured.  We indicate the total process expected and elapsed time. Communicating what is expected and when it is expected is part of making the app experience comprehensible.

Reliable
100% reliability is not possible even if the system is as simple as a kitchen light switch. Reporting, mitigation and notification are all strategies that we use to help manage reliability failures in complex IoT systems.

Authenticated
There are competing forces. It is critical to know who is doing what and that permissions are appropriate and manageable. It is also critical for the user to know that the system is secure, true and responsive. Competing against that is the chance that security layers are over burdensome for activities that don’t need to be secure. We get the balance right.

Also see Navihedrons

Arm and Disarm monitored video alarms

IPIO800

IO Device

IPIO is a cloud based I/O device. It is designed for arming and disarming monitored video alarms and or opening gates. It can be used to replace a keypad. The IPIO device is robust and can be wall or table mounted.

End user Apps

IPIO Android and iOS mobile apps can support many IPIO sites. We have some customers with 100’s of sites, other with 10’s and for those with just one site the app auto configures to skip the site selection page (left). There are two levels of user, Manager and Guest.

Once you have entered a site in the app you can arm all – to secure the premises entirely or simply arm a zone (centre). All buttons can be renamed or removed from the app interface.

A full log of events available to Managers provides a full evidence trace of who arms or disarms and when (right).

Monitoring Centre Portal

For monitoring centres there is a web portal where all IPIO units can be monitored and managed.

IPIOtriplefinal

Find out more here: https://www.eyespyfx.com/ipio.html