Satel Integra (Security System) with ethernet module Topic is solved
Moderator: leecollings
-
- Posts: 1
- Joined: Sunday 20 April 2014 9:31
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Satel Integra (Security System) with ethernet module
Does anyone know why I can't see a Satel Smoke Detector (ASD-100) in domoticz? All other sensors are transmitted by the Integra system though.
Regards, Andreas
Regards, Andreas
-
- Posts: 269
- Joined: Thursday 26 March 2015 10:40
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Poland
- Contact:
Re: Satel Integra (Security System) with ethernet module
I didn't implementing this type of device.
Fantom
Fantom
-
- Posts: 31
- Joined: Saturday 07 July 2018 22:08
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Poland
- Contact:
Re: Satel Integra (Security System) with ethernet module
After last updates Beta version (build 14374 and one before) i have a strange issue: after restart Domoticz sevice some switches connected to Satel Integra are turning on and off. For example: after restarting Domoticz my garage door starts openning. It looks like serious security issue. Can You check it?
-
- Posts: 15
- Joined: Sunday 03 March 2019 12:47
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.10532
- Location: the Netherlands
- Contact:
Re: Satel Integra (Security System) with ethernet module
Hi All,
I have an INTEGRA 256+ like many I have the same problem that I cannot read after zone/output 128, Satel told me that there needs to be an additional byte added in the script. (This was also mentioned in this topic) but was not successful.
There has been updates for the INTEGRA and for the ETHM+ module INTEGRA V1.20 build 2022-02-10 ETHM+ V2.09 build 2022-03-17 maybe this is fixed.
Also i think it should be possible to read Temperature/Power usage from the ABAX2 (wireless receiver INTEGRA) devices according to the integration document.
I cannot test these options in Domoticz because I don’t know how to program this, however I know a lot about the Satel INTEGRA panel so hopefully we can get these functions added and working.
Best regards,
Jero.
I have an INTEGRA 256+ like many I have the same problem that I cannot read after zone/output 128, Satel told me that there needs to be an additional byte added in the script. (This was also mentioned in this topic) but was not successful.
There has been updates for the INTEGRA and for the ETHM+ module INTEGRA V1.20 build 2022-02-10 ETHM+ V2.09 build 2022-03-17 maybe this is fixed.
Also i think it should be possible to read Temperature/Power usage from the ABAX2 (wireless receiver INTEGRA) devices according to the integration document.
I cannot test these options in Domoticz because I don’t know how to program this, however I know a lot about the Satel INTEGRA panel so hopefully we can get these functions added and working.
Best regards,
Jero.
OrangePi Plus 2e with Armbian Buster.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
-
- Posts: 15
- Joined: Sunday 03 March 2019 12:47
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.10532
- Location: the Netherlands
- Contact:
Re: Satel Integra (Security System) with ethernet module
Hello Fantom,
The ETHM-1 PLUS does send 32 bits, if I sent the command with the additional byte in the command (two times the command).
I did the following command and got an output in 32 bits (this also works with the 128, 64, 32, 24 and PLUS type of panels)
I want to know the violated zones state CMD "00"
Input: [FE FE] [00 00] [50 8A] [FE 0D]
Output: [FE FE] [00] [06 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00] [CA 00] [FE 0D]
For the output state I sent CMD "17"
input: [FE FE] [17 17] [50 73] [FE 0D]
output: [FE FE] [17] [1F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00] [8E 05] [FE 0D]
as you can see, I sent the command two times and calculated the CRC.high and crc.low with two times the command.
I hope this helps.
The ETHM-1 PLUS does send 32 bits, if I sent the command with the additional byte in the command (two times the command).
I did the following command and got an output in 32 bits (this also works with the 128, 64, 32, 24 and PLUS type of panels)
I want to know the violated zones state CMD "00"
Input: [FE FE] [00 00] [50 8A] [FE 0D]
Output: [FE FE] [00] [06 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00] [CA 00] [FE 0D]
For the output state I sent CMD "17"
input: [FE FE] [17 17] [50 73] [FE 0D]
output: [FE FE] [17] [1F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00] [8E 05] [FE 0D]
as you can see, I sent the command two times and calculated the CRC.high and crc.low with two times the command.
I hope this helps.
OrangePi Plus 2e with Armbian Buster.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
-
- Posts: 15
- Joined: Sunday 03 March 2019 12:47
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.10532
- Location: the Netherlands
- Contact:
Re: Satel Integra (Security System) with ethernet module
If I look at the script CRC calculation table at line 1222 domoticz/SatelIntegra.cpp at developmen ... ithub.com)
I see that an additional byte (0xFF) is added, however I do not see that the CRC outcome of the command is calculated again with 0xFF.
What I mean is: the following normally you start the CRC with 0x14 0x7A let’s say we want to calculate 32 bytes for command 17 (output state).
we do: 0x14 0x7A {147A} (1-bit rotate Left)
147A to bit = 0001 0100 0111 1010
0001 0100 0111 1010 RL = 0010 1000 1111 0100
Then recalculate it back to HEX
0010 1000 1111 0100 to HEX = 28F4
XOR with 0xFFFF
28F4 XOR FFFF = D70B
finally, we calculate the D70B with it first bit "D7" and the command "17"
D70B + D7 + 17 = D7F9
so far, we now have a CRC for 16 Bit "128 outputs" however we want to know "256 outputs"
we do the following: Instead of starting with 0x14 0x7A {147A} we start with 0xD7 0xF9 {D7F9} this is the outcome of our first calculation.
we do: 0xD7 0xF9 {C7F9} (1-bit rotate Left)
D7F9 to bit = 1101 0111 1111 1001
1101 0111 1111 1001 RL = 1010 1111 1111 0011
Then recalculate it back to HEX
1010 1111 1111 0011 to HEX = AFF3
XOR with 0xFFFF
AFF3 XOR FFFF = 500C
finally, we calculate the 500C with it first bit "50" and the command "FF" (FF is the additional byte)
500C + 50 + FF = 515B
the complete command to the INTEGRA should look like this:
FE FE 17 ff 51 5B FE 0D
The reply from my INTEGRA:
FE FE 17 BF 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 46 91 FE 0D
In my last post I mentioned that you calculate twice the command however sent FF is easier to program I think and also works.
the commands that should work like this are:
0x00 zones violation
0x01 zones tamper
0x02 zones alarm
0x03 zones tamper alarm
0x04 zones alarm memory
0x05 zones tamper alarm memory
0x06 zones bypass
0x07 zones 'no violation' trouble
0x08 zones 'long violation' trouble
0x17 outputs state
0x26 zones isolate
0x28 zones masked
0x29 zones masked memory
it does not matter to what type of INTEGRA you sent this 32bit command. the INTEGRA will reply.
Hopefully this can be implented.
Best regards,
Jero-Neo
I see that an additional byte (0xFF) is added, however I do not see that the CRC outcome of the command is calculated again with 0xFF.
What I mean is: the following normally you start the CRC with 0x14 0x7A let’s say we want to calculate 32 bytes for command 17 (output state).
we do: 0x14 0x7A {147A} (1-bit rotate Left)
147A to bit = 0001 0100 0111 1010
0001 0100 0111 1010 RL = 0010 1000 1111 0100
Then recalculate it back to HEX
0010 1000 1111 0100 to HEX = 28F4
XOR with 0xFFFF
28F4 XOR FFFF = D70B
finally, we calculate the D70B with it first bit "D7" and the command "17"
D70B + D7 + 17 = D7F9
so far, we now have a CRC for 16 Bit "128 outputs" however we want to know "256 outputs"
we do the following: Instead of starting with 0x14 0x7A {147A} we start with 0xD7 0xF9 {D7F9} this is the outcome of our first calculation.
we do: 0xD7 0xF9 {C7F9} (1-bit rotate Left)
D7F9 to bit = 1101 0111 1111 1001
1101 0111 1111 1001 RL = 1010 1111 1111 0011
Then recalculate it back to HEX
1010 1111 1111 0011 to HEX = AFF3
XOR with 0xFFFF
AFF3 XOR FFFF = 500C
finally, we calculate the 500C with it first bit "50" and the command "FF" (FF is the additional byte)
500C + 50 + FF = 515B
the complete command to the INTEGRA should look like this:
FE FE 17 ff 51 5B FE 0D
The reply from my INTEGRA:
FE FE 17 BF 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 46 91 FE 0D
In my last post I mentioned that you calculate twice the command however sent FF is easier to program I think and also works.
the commands that should work like this are:
0x00 zones violation
0x01 zones tamper
0x02 zones alarm
0x03 zones tamper alarm
0x04 zones alarm memory
0x05 zones tamper alarm memory
0x06 zones bypass
0x07 zones 'no violation' trouble
0x08 zones 'long violation' trouble
0x17 outputs state
0x26 zones isolate
0x28 zones masked
0x29 zones masked memory
it does not matter to what type of INTEGRA you sent this 32bit command. the INTEGRA will reply.
Hopefully this can be implented.
Best regards,
Jero-Neo
OrangePi Plus 2e with Armbian Buster.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
- waltervl
- Posts: 5741
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: Satel Integra (Security System) with ethernet module
If you make a pull request in the domoticz GitHub repository it will be implemented in latest beta. You should first build domoticz yourself to validate the proposed change.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
- Posts: 15
- Joined: Sunday 03 March 2019 12:47
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.10532
- Location: the Netherlands
- Contact:
Re: Satel Integra (Security System) with ethernet module
Thank you Walter for you reply, i am not a programmer and know nothing about the C++ language. I am a product manager for the Satel products on the Dutch market.
i think that a C++ programmer could fix this in a few hours or so. for me it would take weeks only to understand the basics of C++.
best regards
Jero-Neo
i think that a C++ programmer could fix this in a few hours or so. for me it would take weeks only to understand the basics of C++.
best regards
Jero-Neo
OrangePi Plus 2e with Armbian Buster.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
- waltervl
- Posts: 5741
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: Satel Integra (Security System) with ethernet module
You could ask one of the Satel C programmers to take a quick look at the Domoticz integration 

Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
- Posts: 15
- Joined: Sunday 03 March 2019 12:47
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.10532
- Location: the Netherlands
- Contact:
Re: Satel Integra (Security System) with ethernet module
After compiling Domoticz i have modified the following lines this works to read past zone/output 128, i have tested this on a INTEGRA 265+/64+ with ETHM-1 plus. please note that the ETHM-1 and ETHM-1 plus type both are 32bit, in my test I have tested also with the 64+ to look at possible issues regarding the zone/output count.
Line 347 original
could some people verify these changes on their system? and share the outcome of this? it does not matter what type of INTEGRA panel is connected this is only to see if there are no errors rises the surface.
Line 347 original
Line 347 modifiedbuffer[1], buffer[2], buffer[3], buffer[4], buffer[5], buffer[6], buffer[7], buffer[8], buffer[9], buffer[10], buffer[11], m_data32 ? "true" : "false");
Line 382-386 originalbuffer[1], buffer[2], buffer[3], buffer[4], buffer[5], buffer[6], buffer[7], buffer[8], buffer[9], buffer[10], buffer[11], m_data32 ? "false" : "true");
Line 382-386 modifiedunsigned int zonesCount = models[m_modelIndex].zones;
if ((zonesCount > 128) && (!m_data32))
{
zonesCount = 128;
}
Line 458-462 originalunsigned int zonesCount = models[m_modelIndex].zones;
if ((zonesCount > 256) && (!m_data32))
{
zonesCount = 256;
}
Line 458-462 modifiedunsigned int zonesCount = models[m_modelIndex].zones;
if ((zonesCount > 128) && (!m_data32))
{
zonesCount = 128;
}
Line 538-542 originalunsigned int zonesCount = models[m_modelIndex].zones;
if ((zonesCount > 256) && (!m_data32))
{
zonesCount = 256;
}
Line 538-542 modifiedunsigned int outputsCount = models[m_modelIndex].outputs;
if ((outputsCount > 128) && (!m_data32))
{
outputsCount = 128;
}
In my previous post I mentioned that the CRC did not calculate correctly, this was mis interpreted.unsigned int outputsCount = models[m_modelIndex].outputs;
if ((outputsCount > 256) && (!m_data32))
{
outputsCount = 256;
}
could some people verify these changes on their system? and share the outcome of this? it does not matter what type of INTEGRA panel is connected this is only to see if there are no errors rises the surface.
OrangePi Plus 2e with Armbian Buster.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
-
- Posts: 31
- Joined: Saturday 07 July 2018 22:08
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Poland
- Contact:
Re: Satel Integra (Security System) with ethernet module
Hi,
After the last few updates, the state of the blinds has changed. The OPEN key closes and the CLOSE key opens. In the Satel menu (TNT-TSI) it works properly and nothing has been modified. Was anything changed in this code in Domoticz?
Tom
After the last few updates, the state of the blinds has changed. The OPEN key closes and the CLOSE key opens. In the Satel menu (TNT-TSI) it works properly and nothing has been modified. Was anything changed in this code in Domoticz?
Tom
-
- Posts: 269
- Joined: Thursday 26 March 2015 10:40
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Poland
- Contact:
Re: Satel Integra (Security System) with ethernet module
Only JeroNeo changed the code.
And I don't understand these changes at all - it is inconsistent with the documentation.
And I don't understand these changes at all - it is inconsistent with the documentation.
- waltervl
- Posts: 5741
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: Satel Integra (Security System) with ethernet module
For blinds in 2022.2 , please check the settings of the blinds devices. see wiki https://www.domoticz.com/wiki/Blinds
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
- Posts: 15
- Joined: Sunday 03 March 2019 12:47
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.10532
- Location: the Netherlands
- Contact:
Re: Satel Integra (Security System) with ethernet module
Hi Tom,
There have no changes taken place regarding output control or zone readout.
The only thing that has changed is the full compatibility for the INTEGRA 256 Plus model.
how is your setup build? Do the blinds be controlled from the INTEGRA, with the function 105, shutter up/106, shutter down? or different?
Jero
OrangePi Plus 2e with Armbian Buster.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
1x Evohome setup (6x radiators), 1x Tuya floorheater bathroom,
1x RGBW led strip, Satel INTEGRA 256+
IKEA-Trädfri Gateway with 48 controlable lights COAP-Client,
SolarEdge inverter, homebrew P1 meter.
-
- Posts: 31
- Joined: Saturday 07 July 2018 22:08
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Poland
- Contact:
Re: Satel Integra (Security System) with ethernet module
Hi,
Yes, there is a standard connection 105 Up, 106 Down. It works right for 3 years in Integra Controll, INT-TSI Tablet and Domoticz as well. But now only in Domoticz directions are changed. Enabling "Reverse Open/Close State" fix it, but it is not right.
On my side Domoticz 2022.2 (build 14880) and as a hardware Integra 128 Plus with 1.20PL firmware date 2021-09-01.
Yes, there is a standard connection 105 Up, 106 Down. It works right for 3 years in Integra Controll, INT-TSI Tablet and Domoticz as well. But now only in Domoticz directions are changed. Enabling "Reverse Open/Close State" fix it, but it is not right.
On my side Domoticz 2022.2 (build 14880) and as a hardware Integra 128 Plus with 1.20PL firmware date 2021-09-01.
- waltervl
- Posts: 5741
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: Satel Integra (Security System) with ethernet module
With reference to 2022.1 to 2022.2 the blinds behavior in Domoticz has changed. There are no Blinds Inverted devices anymore.
So yes the user has to do the invertion manually when a new device has been created.
@tomes Is the Blinds device created in Domoticz 2022.1 or 2022.2?
So yes the user has to do the invertion manually when a new device has been created.
@tomes Is the Blinds device created in Domoticz 2022.1 or 2022.2?
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
- Posts: 31
- Joined: Saturday 07 July 2018 22:08
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Poland
- Contact:
Re: Satel Integra (Security System) with ethernet module
The Blinds are created 3 years before, so they are imported from version to version. So, i can use it in reverse mode.
-
- Posts: 48
- Joined: Monday 10 December 2018 23:32
- Target OS: Linux
- Domoticz version:
- Location: Poland
- Contact:
Re: Satel Integra (Security System) with ethernet module
I'v done some Domoticz beta updates and I don't when it start something wrong with Satel Integra addon.
I suspect that was a few days ago. Today tried update to the latest beta and it didn't helps.
Now I have lot of re-connections and errors like:
I suspect that was a few days ago. Today tried update to the latest beta and it didn't helps.
Now I have lot of re-connections and errors like:
2023-12-05 14:40:16.724 Satel: General/Alert (Test kuch)
2023-12-05 14:40:16.744 Satel: General/Alert (Wejście 126)
2023-12-05 14:40:18.808 Satel: General/Alert (Test kuch)
2023-12-05 14:40:18.828 Satel: General/Alert (Wejście 126)
2023-12-05 14:40:19.981 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:40:20.084 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:40:23.413 Satel: General/Alert (Salon PIR)
2023-12-05 14:40:25.724 Satel: General/Alert (Salon PIR)
2023-12-05 14:40:26.982 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:40:27.004 Satel: General/Alert (Salon PIR)
2023-12-05 14:40:27.024 Satel: General/Alert (Test kuch)
2023-12-05 14:40:27.048 Satel: General/Alert (Wejście 126)
2023-12-05 14:40:28.279 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:40:28.310 Satel: General/Alert (Test kuch)
2023-12-05 14:40:28.322 Satel: General/Alert (Wejście 126)
2023-12-05 14:40:32.788 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:40:32.762 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:40:32.762 Error: Satel: Send 'Read Outputs' failed
2023-12-05 14:40:35.783 Satel: General/Alert (Salon PIR)
2023-12-05 14:40:40.003 Msensors: General/Percentage (Memory Usage)
2023-12-05 14:40:40.030 Msensors: General/Custom Sensor (Process Usage)
2023-12-05 14:40:50.014 Msensors: Temp (Internal Temperature)
2023-12-05 14:40:50.028 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:41:16.662 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:41:16.677 Satel: General/Alert (Test kuch)
2023-12-05 14:41:16.696 Satel: General/Alert (Wejście 126)
2023-12-05 14:41:17.749 Satel: General/Alert (Test kuch)
2023-12-05 14:41:17.774 Satel: General/Alert (Wejście 126)
2023-12-05 14:41:19.077 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:41:20.026 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:41:45.601 Satel: General/Alert (Salon PIR)
2023-12-05 14:41:49.266 Satel: General/Alert (Salon PIR)
2023-12-05 14:41:50.055 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:41:50.066 Msensors: General/Percentage (HDD /)
2023-12-05 14:41:50.068 Msensors: General/Percentage (HDD /home)
2023-12-05 14:41:50.070 Msensors: General/Percentage (HDD /media/dysk)
2023-12-05 14:42:00.059 Msensors: Temp (Internal Temperature)
2023-12-05 14:42:00.071 Msensors: General/Percentage (Memory Usage)
2023-12-05 14:42:00.074 Msensors: General/Custom Sensor (Process Usage)
2023-12-05 14:42:05.596 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:08.362 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:08.398 Satel: General/Alert (Test kuch)
2023-12-05 14:42:12.407 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:42:12.407 Error: Satel: Get info about new data is failed
2023-12-05 14:42:13.736 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:13.758 Satel: General/Alert (Test kuch)
2023-12-05 14:42:13.420 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:42:15.483 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:16.526 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:16.575 Satel: General/Alert (Test kuch)
2023-12-05 14:42:17.622 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:17.643 Satel: General/Alert (Test kuch)
2023-12-05 14:42:19.143 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:20.069 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:42:20.198 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:25.309 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:28.369 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:28.398 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:28.419 Satel: General/Alert (Test kuch)
2023-12-05 14:42:29.666 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:29.695 Satel: General/Alert (Test kuch)
2023-12-05 14:42:30.993 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:32.040 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:32.069 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:32.083 Satel: General/Alert (Test kuch)
2023-12-05 14:42:33.117 Satel: General/Alert (Test kuch)
2023-12-05 14:42:34.230 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:36.314 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:36.337 Satel: General/Alert (Test kuch)
2023-12-05 14:42:37.380 Satel: General/Alert (Test kuch)
2023-12-05 14:42:38.452 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:39.492 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:39.501 Satel: General/Alert (Test kuch)
2023-12-05 14:42:40.591 Satel: General/Alert (Test kuch)
2023-12-05 14:42:41.668 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:43.741 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:43.778 Satel: General/Alert (Test kuch)
2023-12-05 14:42:44.822 Satel: General/Alert (Test kuch)
2023-12-05 14:42:45.910 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:47.967 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:47.989 Satel: General/Alert (Test kuch)
2023-12-05 14:42:49.074 Satel: General/Alert (Test kuch)
2023-12-05 14:42:50.099 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:42:50.401 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:51.416 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:51.442 Satel: General/Alert (Test kuch)
2023-12-05 14:42:52.494 Satel: General/Alert (Test kuch)
2023-12-05 14:42:53.586 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:53.603 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:55.644 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:56.682 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:58.769 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:42:58.799 Satel: General/Alert (Salon PIR)
2023-12-05 14:42:58.811 Satel: General/Alert (Test kuch)
2023-12-05 14:43:00.049 Satel: General/Alert (Test kuch)
2023-12-05 14:43:01.847 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:43:03.156 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:43:04.261 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:43:10.114 Msensors: Temp (Internal Temperature)
2023-12-05 14:43:20.128 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:43:20.160 Msensors: General/Percentage (Memory Usage)
2023-12-05 14:43:20.174 Msensors: General/Custom Sensor (Process Usage)
2023-12-05 14:43:20.485 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:43:20.532 Satel: General/Alert (Test kuch)
2023-12-05 14:43:21.838 Satel: General/Alert (Test kuch)
2023-12-05 14:43:22.898 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:43:23.947 Satel: General/Alert (Salon PIR)
2023-12-05 14:43:29.247 Satel: General/Alert (Salon PIR)
2023-12-05 14:43:50.156 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:44:20.156 Msensors: Temp (Internal Temperature)
2023-12-05 14:44:20.161 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:44:22.646 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:44:22.646 Error: Satel: Get info about new data is failed
2023-12-05 14:44:38.978 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:44:40.164 Msensors: General/Percentage (Memory Usage)
2023-12-05 14:44:40.176 Msensors: General/Custom Sensor (Process Usage)
2023-12-05 14:44:40.183 Msensors: General/Percentage (HDD /)
2023-12-05 14:44:40.189 Msensors: General/Percentage (HDD /home)
2023-12-05 14:44:40.194 Msensors: General/Percentage (HDD /media/dysk)
2023-12-05 14:44:41.982 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:44:41.982 Error: Satel: Get info about new data is failed
2023-12-05 14:44:42.993 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:44:43.009 Error: Satel: busy
2023-12-05 14:44:43.009 Error: Satel: Get info about new data is failed
2023-12-05 14:44:44.009 Error: Satel: bad data length received (totalRet 0)
2023-12-05 14:44:44.009 Error: Satel: Get info about new data is failed
2023-12-05 14:44:45.020 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:44:45.036 Error: Satel: busy
2023-12-05 14:44:45.037 Error: Satel: Get info about new data is failed
2023-12-05 14:44:46.037 Error: Satel: bad data length received (totalRet 0)
2023-12-05 14:44:46.037 Error: Satel: Get info about new data is failed
2023-12-05 14:44:47.048 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:44:47.063 Error: Satel: busy
2023-12-05 14:44:47.064 Error: Satel: Get info about new data is failed
2023-12-05 14:44:48.064 Error: Satel: bad data length received (totalRet 0)
2023-12-05 14:44:48.064 Error: Satel: Get info about new data is failed
2023-12-05 14:44:49.074 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:44:50.186 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:44:51.988 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:00.084 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:02.356 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:04.424 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:07.522 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:10.784 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:11.845 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:14.568 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:20.197 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:45:28.057 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:30.107 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:45:30.135 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:30.161 Satel: General/Alert (Test kuch)
2023-12-05 14:45:30.166 Satel: General/Alert (Wejście 126)
2023-12-05 14:45:30.202 Msensors: Temp (Internal Temperature)
2023-12-05 14:45:31.215 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:31.261 Satel: General/Alert (Test kuch)
2023-12-05 14:45:31.264 Satel: General/Alert (Wejście 126)
2023-12-05 14:45:32.300 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:45:34.366 Satel: General/Alert (Salon PIR)
2023-12-05 14:45:36.646 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:45:36.670 Satel: General/Alert (Test kuch)
2023-12-05 14:45:36.677 Satel: General/Alert (Wejście 126)
2023-12-05 14:45:37.734 Satel: General/Alert (Test kuch)
2023-12-05 14:45:37.757 Satel: General/Alert (Wejście 126)
2023-12-05 14:45:38.852 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:45:39.880 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:45:39.893 Satel: General/Alert (Test kuch)
2023-12-05 14:45:39.908 Satel: General/Alert (Wejście 126)
2023-12-05 14:45:40.981 Satel: General/Alert (Test kuch)
2023-12-05 14:45:41.007 Satel: General/Alert (Wejście 126)
2023-12-05 14:45:42.079 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:45:50.213 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:45:54.558 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:45:54.561 Satel: General/Alert (Test kuch)
2023-12-05 14:45:54.591 Satel: General/Alert (Wejście 126)
2023-12-05 14:45:55.707 Satel: General/Alert (Test kuch)
2023-12-05 14:45:55.730 Satel: General/Alert (Wejście 126)
2023-12-05 14:45:56.769 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:45:57.810 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:45:57.833 Satel: General/Alert (Test kuch)
2023-12-05 14:45:57.854 Satel: General/Alert (Wejście 126)
2023-12-05 14:45:58.921 Satel: General/Alert (Test kuch)
2023-12-05 14:45:58.933 Satel: General/Alert (Wejście 126)
2023-12-05 14:46:00.023 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:46:00.228 Msensors: General/Percentage (Memory Usage)
2023-12-05 14:46:00.241 Msensors: General/Custom Sensor (Process Usage)
2023-12-05 14:46:01.092 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:46:01.107 Satel: General/Alert (Test kuch)
2023-12-05 14:46:01.115 Satel: General/Alert (Wejście 126)
2023-12-05 14:46:03.167 Satel: General/Alert (Test kuch)
2023-12-05 14:46:03.178 Satel: General/Alert (Wejście 126)
2023-12-05 14:46:04.242 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:46:06.283 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:46:06.311 Satel: General/Alert (Test kuch)
2023-12-05 14:46:06.333 Satel: General/Alert (Wejście 126)
2023-12-05 14:46:07.375 Satel: General/Alert (Test kuch)
2023-12-05 14:46:07.390 Satel: General/Alert (Wejście 126)
2023-12-05 14:46:08.457 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:46:09.491 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:46:09.518 Satel: General/Alert (Test kuch)
2023-12-05 14:46:09.521 Satel: General/Alert (Wejście 126)
2023-12-05 14:46:10.589 Satel: General/Alert (Salon PIR)
2023-12-05 14:46:10.645 Satel: General/Alert (Test kuch)
2023-12-05 14:46:10.650 Satel: General/Alert (Wejście 126)
2023-12-05 14:46:11.705 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:46:16.051 Satel: General/Alert (Salon PIR)
2023-12-05 14:46:20.265 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:46:40.277 Msensors: Temp (Internal Temperature)
2023-12-05 14:46:50.296 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:46:53.453 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:46:53.454 Error: Satel: Get info about new data is failed
2023-12-05 14:46:54.464 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:47:02.143 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:47:02.144 Error: Satel: Get info about new data is failed
2023-12-05 14:47:06.173 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:47:09.176 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:47:09.176 Error: Satel: Get info about new data is failed
2023-12-05 14:47:13.213 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:47:18.894 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:47:18.894 Error: Satel: Get info about new data is failed
2023-12-05 14:47:20.310 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:47:20.324 Msensors: General/Percentage (Memory Usage)
2023-12-05 14:47:20.337 Msensors: General/Custom Sensor (Process Usage)
2023-12-05 14:47:30.305 Msensors: General/Percentage (HDD /)
2023-12-05 14:47:30.309 Msensors: General/Percentage (HDD /home)
2023-12-05 14:47:30.312 Msensors: General/Percentage (HDD /media/dysk)
2023-12-05 14:47:35.360 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:47:50.333 Msensors: Temp (Internal Temperature)
2023-12-05 14:47:50.337 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:48:15.238 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:48:15.238 Error: Satel: Get info about new data is failed
2023-12-05 14:48:16.249 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:48:19.346 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:48:19.346 Error: Satel: Send 'Read outputs' failed
2023-12-05 14:48:20.341 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:48:20.358 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:48:40.351 Msensors: General/Percentage (Memory Usage)
2023-12-05 14:48:40.379 Msensors: General/Custom Sensor (Process Usage)
2023-12-05 14:48:41.736 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:48:41.736 Error: Satel: Get info about new data is failed
2023-12-05 14:48:42.747 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:48:50.359 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:48:54.574 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:48:54.574 Error: Satel: Get info about new data is failed
2023-12-05 14:48:56.605 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:49:00.370 Msensors: Temp (Internal Temperature)
2023-12-05 14:49:20.379 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:49:25.006 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:49:25.006 Error: Satel: Get info about new data is failed
2023-12-05 14:49:26.017 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:49:50.390 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:49:51.283 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:49:51.283 Error: Satel: Get info about new data is failed
2023-12-05 14:49:52.293 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:50:00.394 Msensors: General/Percentage (Memory Usage)
2023-12-05 14:50:00.415 Msensors: General/Custom Sensor (Process Usage)
2023-12-05 14:50:10.405 Msensors: Temp (Internal Temperature)
2023-12-05 14:50:20.428 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:50:20.433 Msensors: General/Percentage (HDD /)
2023-12-05 14:50:20.436 Msensors: General/Percentage (HDD /home)
2023-12-05 14:50:20.438 Msensors: General/Percentage (HDD /media/dysk)
2023-12-05 14:50:25.123 Satel: General/Alert (Salon PIR)
2023-12-05 14:50:27.181 Satel: General/Alert (Salon PIR)
2023-12-05 14:50:28.898 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:50:30.188 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:50:31.231 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:50:33.842 Satel: General/Alert (PIRKuchnia)
2023-12-05 14:50:43.914 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:50:43.914 Error: Satel: Get info about new data is failed
2023-12-05 14:50:47.965 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:50:50.464 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:50:50.969 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:50:50.969 Error: Satel: Get info about new data is failed
2023-12-05 14:50:51.981 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:50:51.997 Error: Satel: busy
2023-12-05 14:50:51.997 Error: Satel: Get info about new data is failed
2023-12-05 14:50:52.997 Error: Satel: bad data length received (totalRet 0)
2023-12-05 14:50:52.997 Error: Satel: Get info about new data is failed
2023-12-05 14:50:54.009 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:50:54.233 Error: Satel: busy
2023-12-05 14:50:54.233 Error: Satel: Get info about new data is failed
2023-12-05 14:50:55.233 Error: Satel: bad data length received (totalRet 0)
2023-12-05 14:50:55.234 Error: Satel: Get info about new data is failed
2023-12-05 14:50:57.278 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:50:57.291 Error: Satel: busy
2023-12-05 14:50:57.291 Error: Satel: Get info about new data is failed
2023-12-05 14:50:58.291 Error: Satel: bad data length received (totalRet 0)
2023-12-05 14:50:58.291 Error: Satel: Get info about new data is failed
2023-12-05 14:51:00.317 Status: Satel: connected to 192.168.22.8:7094
2023-12-05 14:51:03.318 Error: Satel: bad data length received (totalRet -1)
2023-12-05 14:51:03.318 Error: Satel: Get info about new data is failed
2023-12-05 14:51:20.473 Msensors: Temp (Internal Temperature)
2023-12-05 14:51:20.493 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:51:20.504 Msensors: General/Percentage (Memory Usage)
2023-12-05 14:51:20.518 Msensors: General/Custom Sensor (Process Usage)
2023-12-05 14:51:50.518 Msensors: General/Percentage (CPU_Usage)
2023-12-05 14:51:56.037 Error: Satel hardware (3) thread seems to have ended unexpectedly
2023-12-05 14:52:10.052 Error: Satel hardware (3) thread seems to have ended unexpectedly
2023-12-05 14:52:20.526 Msensors: General/Percentage (CPU_Usage)
Who is online
Users browsing this forum: No registered users and 1 guest