ioBroker.lupusec

Requires node.js 20.0 or higher and Admin v5!

This adapter connects the Lupusec alarm system XT1 Plus, XT2, XT2 Plus and XT3 with ioBroker. The XT1 (without Plus) will not be supported. You can read the status of the Lupusec sensors like door, windows, water, smoke sensors and the status of the alarm system. For example, you can turn on switches, control your shutter and arm/disarm the alarm system. Because the adapter has to call the alarm system a few times to get all the information for the status and device the CPU load and memory usage is high. To decrease the CPU load you can increase the polltime.

You can find detailed information here: Lupus

Installation

1. Install the adapter The easiest way is to configure the lupusec.iobroker adapter via the discovery adapter in ioBroker. The discovery adapter search for the right IP-address of the Lupusec alarm system. The other way is it, to configure it manually

2. Manually configuration of the adapter Choose the IP-Address or hostname and port from the Lupusec alarm system. If you use https, activate the https flag. The CPU load is higher with https insted without http. For only reading the status, select a user without write access. If you want to change the status (for example, turn on/off the light or arm/disarm the alarm) pick a user with write access. With polltime you can configure, how often the alarm system shall be called. A high polltime decrease the CPU load.

   If you have surveillance cams connected to your Lupusec alarm system you can provide them in ioBroker. The Lupusec adapter finds all Lupusec cams by it own. You have to enter a address (your ioBroker IP addrss or 0.0.0.0) and a port for later connecting to the cams. If you have your Nuki door opener connected to your Lupusec alarm system you can use it from ioBroker too. On the ioBroker instance admin menu, you can enter your Lupusec door sensor which is mounted to the Nuki door. If you now open the door where the Nuki is mounted you have the additional state 'door opened' instead only 'unlocked'. If you do not have a Lupusec door sensor at the Nuki door, you will only see the states 'locked' or 'locked'.

By default all Lupusec devices will be on the ioBroker object tab displayed. Fully supported and individually adapted are following devices:

• Door contact / window contact (Type 4)
• Water sensor (Type 5)
• Panic Button (Type 7)
• Motion detector / 360 degree motion detector (Type 9)
• CO sensor (Type 13)
• Smoke Detector / Heat Detector (Type 14)
• Temperature Sensor V2 (Type 20)
• Siren inside (Type 21)
• Status Indicator / Mini Indoor Siren (Type 22)
• Power Switch (Type 24)
• 1 channel relay with ZigBee repeater (Type 24)
• 2 channel relay with ZigBee repeater (Type 24)
• Repater V2 (Type 26)
• Keypad (Type 37)
• Glass sensor (Type 39)
• Siren inside (Type 45)
• Siren outside (Type 48)
• Power Switch Meter (Type 48)
• Electric Meter (Type 50)
• Universal IR Controller (Type 52)
• Room sensor V1 (Type 54)
• LCD temperature sensor (Type 54)
• Mini temperature (Type 54)
• Nuki door opener (Type 57)
• Heat detector (Type 58)
• Dimmer (Type 66)
• Light Switch V2 (Type 66)
• Hue (Type 74)
• Roller shutter relay V1 (Type 76)
• Radiator thermostat (Type 79)
• Radiator thermostat V2 (Type 79)
• Light sensor (Type 78)
• Scenario Switch V2 (Type 81)
• Shock sensor (Type 93)
• Smoke detector V2 (Type 14)
• Inwall relay with dimmer V3 (Type 66)
• Keypad Outdoor V2 (Type 17)

The two states apple_home_a1 and lupusec.0.status.apple_home_a2 for the Apple Homekit adapter yahka supported. You can turn in addition to the lupusec states the alarm system for area 1 and 2 on and off.

If you own a device that is not listed in the list above, please contact me at Thorsten Stueben .

Migration from adapter version 1.x.x to 2.x.x

If you have installed version 1.x.x installed and you would like to switch to version 2.0.0 or higher, you unfortunately have to configure the Lupusec instance again. The old configruation values from version 1.x.x ​​are not adopted.

This is due to the fact that the configuration interface has been completely revised.

To make the settings for the Nuki lock, you first have to enter the hostname, username and password and then save. The instance will now restart. As soon as it starts without errors, open the instance configuration again. You can now configure your Nuki lock on the Nuki tab.

Objects

Lupusec Status

ioBroker offers you the same status objects as in the Lupusec app does.

Lupusec Devices

You find all supported Lupsec sensors and devices under 'devices'. If a device is missing, please contact me. Detailed view of a sensor or device. In this example you see the CO sensor. On CO alarm the state 'alarm_status_ex' change to true and 'alarm_status' change to 'CO'.

Lupusec Webcams

You find all connected surveillance cams under 'webcams'. You can copy the link provided in the 'image' and 'stream' state to your web browser for opening.

Lupusec Nuki

You find your Nuki door opener under 'devices' like the Lupusec devices. The Nuki provides 2 states. The state nuki_state shows you the actuall state of the Nuki door opener like door is locked or unlocked. With the state nuki_action you can open, lock or unlock your door.

Lupusec SMS

If you ar using the Lupusec XT1+, XT2+ or XT3 with an SMS sim card, you can send SMS with following states:

Alternative you can send SMS from your JavaScript with following command:

sendTo('lupusec.0', 'sms', { number: '+4917247114711', text: 'Test message' });

if you are using the SMS gateway you can use following command in your script:

sendTo('lupusec.0', 'smsgw', { number: '+4917247114711', text: 'Test message' });

Troubleshooting

If you start the Lupusec Adapter and you get the error that the alarm system is not reachable please try to ping the system from a terminal window of your ioBroker system.

ssh @
sudo -u iobroker ping 

If you get the error ping: icmp open socket: Operation not permitted please do following and start afterwards the Lupusec adapter again.

ls -l `which ping`
sudo chmod u+s `which ping`

Changelog

2.0.8 (2025-04-19)

• (Stübi) Performance optimization by pplling Lupusec alarm system (Issue #123)
• (Stübi) Add actual_temperature to type 20 Sensor (Issue #124)

2.0.7 (2025-02-23)

• (Stübi) Fixing @iobroker/adapter-dev 1.0.1 specified. 1.3.0 is required as minimum, 1.3.0 is recommended (Issue #115)
• (Stübi) Fixiing problem, that state value jumps back to old value (Issue #116)
• (Stübi) Delete status switch and add 3 butteons (shutter_up, shutter_down, shutter_stop) for shutter (Issue #116)
• (Stübi) Fixing dependency (Issue #117)

2.0.6 (2025-02-10)

• (Stübi) Minus temperature degrees will be shown now (Issue #113)
• (Stübi) Deletes unnecessary device objects (Issue #114)

2.0.5 (2025-02-01)

• (Stübi) Adjust datapoints hue, sat with step 1
• (Stübi) Fixed, that unused states will be not be shwon.

2.0.4 (2025-01-05)

• (Stübi) Adjustments of test and release yml
• (Stübi) Readme expanded to include migration instructions (Issue #97)
• (Stübi) Fixed error with HUE lights (Issue #104)
• (Stübi) Added the following values ​​for type 54: air pressure, wind strength, wind angle, wind gust, co2, wind speed
• (Stübi) Added for HUE the values mode (hue or temperature) and tempererature
• (Stübi) Added not used states will be not be shwon.
• (Stübi) Fixed value range for HUE to 0 to 360 degree, saturation from 0% to 100% and temperature from 2200 to 6500 kelvin

2.0.3 (2024-12-29)

• (Stübi) Adjustments due to migration from ESLint 8x≤ to 9.x.x (Issue #91)
• (Stübi) Redesign - changed everything from JavaScript to TypeScript
• (Stübi) Using axios for http requests
• (Stübi) the configuration changed. You have to edit the configuration
• (Stübi) js-controller in version 6 and 7 will be supported (Issue #83, #84, #95)
• (Stübi) nodejs 20 and nodejs 22 will be suported (Issue #87)

Planed

Following things are planed in the future:

• support more sensors / devices
• writing a documentation for every sensor / device

License

The MIT License (MIT)

Copyright (c) 2025 Thorsten Stueben

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.