Types of equipment

Tools → Equipment types

The sensors and actuators in Jeedom are managed by plugins, which create equipment with commands Info (sensor) or Action (actuator). This then makes it possible to trigger actions based on the change of certain sensors, such as turning on a light on motion detection. But the Jeedom Core, and plugins like Mobile, Homebridge, Google Smart Home, Alexa Smart Home etc., do not know what this equipment is : A socket, a light, a shutter, etc.

To overcome this problem, especially with voice assistants (Turn on the room light), Core introduced the Generic Types, used by these plugins.

This makes it possible to identify a piece of equipment by The light of the room for example.

Most of the time the generic types are set automatically when configuring your module (inclusion in Z-wave for example). But there may be times when you need to reconfigure them. The configuration of these Generic Types can be done directly in certain plugins, or by command in Advanced configuration of it.

This page allows these Generic Types to be configured in a more direct and simpler way, and even offers automatic assignment once the devices have been correctly assigned.

Equipment type

This page offers storage by type of equipment : Socket, Light, Shutter, Thermostat, Camera, etc. Initially, most of your equipment will be classified in Equipment without type. To assign them a type, you can either move them to another type, or right click on the equipment to move it directly. The Equipment Type is not really useful in itself, the most important being the Order Types. You can thus have an Equipment without a Type, or a Type that does not necessarily correspond to its commands. You can of course mix control types within the same equipment. For now, it is more of a storage, a logical organization, which will serve perhaps in future versions.

Advice

• When you move equipment in the game Equipment without type, Jeedom suggests that you remove Generic Types from its orders.
• You can move several pieces of equipment at once by checking the checkboxes to the left of them.

Command type

Once an item of equipment is positioned in the correct Kind, by clicking on it you access the list of its orders, colored differently if it is a Info (Blue) or a Action (Orange).

By right-clicking on an order, you can then assign it a Generic Type corresponding to the specifications of this order (Info / Action type, Numeric, Binary subtype, etc).

Advice

• The contextual menu of commands displays the type of equipment in bold, but still allows to assign any Generic Type of any type of equipment.

On each device, you have two buttons :

• Auto Types : This function opens a window offering you the appropriate Generic Types according to the type of equipment, the specifics of the order, and its name. You can then adjust the proposals and uncheck the application for certain commands before accepting or not. This function is compatible with selection by checkboxes.

• Reset types : This function removes Generic Types from all equipment commands.

Attention

No changes are made before saving, with the button at the top right of the page.

Generic types and scenarios

In v4.2, the Core has integrated the generic types in the scenarios. You can thus trigger a scenario if a lamp comes on in a room, if movement is detected in the house, turn off all the lights or close all the shutters with a single action, etc. In addition, if you add an equipment, you only have to indicate the correct types on its orders, it will not be necessary to edit such scenarios.

Trigger

You can trigger a scenario from sensors. For example, if you have motion detectors in the house, you can create an alarm scenario with each detector triggering : #[Living room][Move Salon][Presence]# == 1, #[Cuisine][Move Cuisine][Presence]# == 1, etc.. In such a scenario, you will therefore need all your motion detectors, and if you add one, you will have to add it to the triggers. Logic.

Thanks to generic types, you will be able to use a single trigger : #genericType(PRESENCE)# == 1. Here, no object is indicated, so the slightest movement throughout the house will trigger the scenario. If you add a new detector in the house, no need to edit the scenario (s)).

Here, a trigger on the switching on of a light in the Living room : #genericType(LIGHT_STATE,#[Living room]#)# > 0

Expression

If, in a scenario, you want to know if a light is on in the Living Room, you can do :

IF #[Living room][Lumiere Canapé][State]# == 1 OR #[Living room][Lumiere Salon][State]# == 1 OR #[Living room][Lumiere Angle][State]# == 1

Or more simply : IF genericType (LIGHT_STATE,#[Living room]#) > 0 or if one or more light (s) are on in the Living room.

If tomorrow you add a light in your living room, no need to retouch your scenarios !

Action

If you want to turn on all the lights in the Living Room, you can create a light action:

#[Living room][Lumiere Canapé][We]#
#[Living room][Lumiere Salon][We]#
#[Living room][Lumiere Angle][We]#

Or more simply, create a genericType action with LIGHT_ON in Salon. If tomorrow you add a light in your living room, no need to retouch your scenarios !

List of Generic Core Types

Advice

• You can find this list directly in Jeedom, on this same page, with the button List top right.