Technical FAQ

Be notified when the mac address of a supervised device disappears from the network.
The supervision is limited to checking whether the mac address of some devices which are deemed important are present or not on the network. The goal being to warn the installer in the shortest delays possible (5 minutes) if for whatever reason a device disappears from or reappears on the network. To place an important/critical device under supervision, click on the “Tool” button at the right of the device you want to supervise and click on “Supervise me”.

Be notified when a setting or a critical value changes inside a device
Krika uses the manufacturers’ communication protocols to retrieve operational information (status, up time, power usage, battery level, radio power signal…). Hypervision allows you to get a notification on internal events reading in the connected devices. Hypervision notifications  may also vary according to the device itself and depend on the information that Krika is able to read in the devices.

Here are example of what might be possible to hypervise:
– For a Control4 processor, the uptime that just drop of the battery level of one of the remote control
– For a Crestron processor, the loss of one of the devices in the Cresnet network or the back to factory default settings
– For a Sonos it might be the strength of the Wi-Fi or setting that just switched from Sonosnet to the Wi-Fi of the customer
– For a printer  the level of toner left


Brand, model, mac address, firmware…
These are all the informations that are needed to specifically identify a connected device. Thus, depending on the manufacturer, it is possible to detect the specific make and model, serial number, mac address, chassis number, firmware, hardware/software revision…
Warning: Some manufacturers do not allow these informations to be read.

Status, up time, power usage, battery level, radio power signal…
These are all the informations specific to the function or state of the connected device. Is it on, off, on standby, how long for, what is the charge of the unit. For a projector what you need to know is what is the remaining life of the lamp is for instance.
Warning: Some manufacturers do not allow these informations to be read.

Everything important and critical as Wi-Fi access points, IP cameras, switches, Home Automation Processors…
In order to avoid being flooded by alert emails and to save on your SMS credits, the only devices that should be supervised or hypervised are the infrastructural devices that are meant to remain permanently connected such as Wi-Fi access points, IP cameras, switches, Home Automation Processors… Generally speaking, it seems obvious to put under supervision all infrastructural devices, systematically and without exception.

As close as possible to the modem or the router.
Installations are generally composed of an Internet modem which also serves as a router. In such a case it is advised to connect Krika to one of this modem/router’s Ethernet ports. Keep in mind that the closer Krika is connected to the router, the better its ‘aerial’ view and the more efficient its supervision of the network will be. If you connect Krika on one of the switches of the installation, it will no longer relay the information to the router should the switch breakdown.
The routers supplied by Internet providers having often limited functions, it is sometimes necessary to short-circuit it and to add an additional router just after original modem/router from your supplier. In this specific case, you will need to connect Krika to the additional router as it will be this new router’s role to create the local network and to serve as DHCP.

Krika has a DHCP only client configuration.
Like all connected devices, it will send a request to the router which will allocate a lease for an IP. There is no setting in the Krika dashboard that can enable it to give it a static IP address. If you absolutely wish a static IP address for your Krika, you will need to do so through the router by entering the mac address appearing on the sticker placed on the side of the Krika unit.

One Krika per Vlan.
As Krika perform much more than a simple IP scan on the network it would have no time enough to do it with the same reliability and accuracy on multiple network. Keep in mind that Krika deeply query all devices for status, firwmare, up time… using all protocol possible and all those operation take a certain time.

Krika will only be able to supervise a class D operating range. To be more specific, if your DHCP has allocated your Krika an IP address in, Krika will discover/detect the connected devices between and If you have several vlan/networks that you wish to supervise, for instance a network in and another in, you need to use one Krika per vlan/network.

With Krika B.R.C. Feature, you can send Basic Remote Commands to a device. This operation is performed from the dashboard with no prior need to open any ports on your modem/router. You will be able to simply reboot a device, or easily access certain settings.
It is also possible to perform a Wake On Lan (W.O.L.) to devices that support this feature.

Operations executed by Krika on the local network of the end user produce a report sent every five minutes to the Krika cloud-hosted services.
UPNP detection is powered by Plugis

Scan and discovery of connected devices
Reading of operational informations
Creation of reports
Sending reports to Krika hosted services

The Server routine performs the analysis of all reports created by the local routines of all the Krika installed at clients’ premises. It is the routine that identifies the connected devices, processes the operational informations in order to generate the various dashboards that can be consulted on the web. This Server routine can only be executed by Krika hosted services or the Krika In-House servers that are directly connected to the client’s premises.
The Krika hosted services represent all remote operations in the Cloud that are managed by Krika servers. In the case of a Krika In-Da-House server, the services are hosted in the server itself at the end customer’s premises and not on the Krika servers on the Cloud. Hosted services are as follows:

Hosting of the Krika website
Processing of the reports issued by routine servers
Creation and management of dashboards
Management of slots and dispatching of email or SMS alerts.

Krika management FAQ

A yearly membership is necessary to access the dashboard of each Krika. This membership covers the management costs of our servers as well as all services updates. Like all supervision Tokens, you can purchase these memberships as ‘tokens’ that you can assign at any time to your chosen Krika. However, once a yearly membership has been assigned to one Krika, it is no longer possible to unsubscribe it and assign the membership to another.

Tokens are the Krika currency to enable active supervision or hypervision
Each Krika is supplied with a credit of 5 Tokens enabling you to receive notifications (email or SMS) from 5 devices selected from all the devices that are listed on the dashboard. If you need to receive notifications from more than 5 devices, Tokens can be purchased at any time from our online store. All Tokens acquired (with the Krika or in the online shop) are purchased for life and pooled in your account, making it possible for you to assign and re-assign them to any Krika as needed. Notifications can be either for Supervision & Hypervision.

Example of use:
– You buy 10 Krika, 50 Tokens will be pooled in your professional account.
– You can check at any time in the Token counter of your dashboard how many you have left
– You can assign/dispatch any of those tokens to any devices you need to supervise in any Krika you have by clicking on the button “Tools” and then “Supervise me” (10 Tokens to Mr Smith, 3 tokens to Mr Baker… and so on until you do not have anymore tokens)
-When a supervision or hypervision event occurs, you’ll get unlimited emails and SMS (as long as your SMS credit is positive).
– At any time, you can “un-supervise” a device and get your token back in your account.
– If you need more Tokens, you can buy some in our online shop. Tokens have no expiry date and are reusable.

Important to understand: Whatever if devices are supervised or not, you’ll always have access in the dashboard to the complete listing of all connected devices. You could if you want stay 24/7 in front of you internet browser, refresh it every 5 minutes and check what important device is missing without using any Tokens. (This is some kind of “passive supervision”).  Using a Token will enable “active supervision” for you to get automatically a notification if a device is missing or need attention.

Each Krika is supplied with a credit of 100 SMS which will be deducted each time a SMS is send by our online service for a Supervision or Hypervision notification. Additional SMS can also be purchased through our online  store. SMS are a powerful communication tool, you will receive them directly on your phone, anywhere in the world and with no need to activate data.

Advice: SMS are charged, so it is advisable to only use them in Tokens that carry out the supervision of critical devices.

No, but in likely yes.
You can pre-buy in our online store as much as yearly subscription as you want. Then you can dispatch them to all Krika you want. 5 years for Mr Smith, 3 years to Mr Baker… So let’s say you want to get involved with your client with 5 years, you can buy 5 yearly subscription, assign it to a particular Krika and you’ll never have to pay until the next 5 years.

This is very convenient for the quotation and the invoice to your customer as you can once for all buy one Krika + as much as extra tokens, yearly subscription, SMS you may need, set all this in your dashboard for a specific Krika and then forget it.

When you purchase a Krika, it does not appear automatically on your dashboard. To do so, you must activate it by entering its serial number and its mac address in your management home page. Only at that moment the yearly membership kicks in.

Advice: If you have purchased several Krika, we suggest that you only activate them at the last minute in order to maximise the duration of your membership.

Krika must never know the end user’s identity and the protection of their privacy is an absolute priority. Every care has been taken to ensure this, including the filtering of certain information even to the Krika itself. Personal information neither leave the end user’s nor are stored in our servers. The installer must also ensure from his side the protection of his own client’s privacy, for example:

  • Not associating a «custom name» identifying the Krika serial numbers, but rather using an index that only the installer can decode.
  • In certain cases, Krika is capable of identifying the name of a program loaded into a processor or the friendly name of a device. Use the same index as the serial numbers in order to protect the identity of your client.
  • Hundreds of new devices being released on the market every day, we cannot guarantee the real time analysis of all these information.
  • Despite all of these precautions, some information leading to the end user’s identification could appear on the dashboard, in such a case do not hesitate to inform us!
Non, désolé.