vanackej / risco-mqtt-local Goto Github PK

View Code? Open in Web Editor NEW

24.0 24.0 11.0 456 KB

Provide Risco alarm system integration to Home assistant using local TCP communication (no cloud required) and MQTT

License: MIT License

Dockerfile 3.51% TypeScript 90.80% JavaScript 5.69%

home-assistant home-automation mqtt risco

risco-mqtt-local's People

Contributors

Stargazers

Watchers

Forkers

mrbarbz markxroberts kkmaslowski teruggim racelandshop gawindx lukino2000 mita4kata neveride84 needles77

risco-mqtt-local's Issues

Restarting Home Assistant while Risco active causes sensors and switches to have 'unknown' state.

Describe the bug
If risco-mqtt-local is running and Home Assistant is restarted, sensors and switches have 'unknown' state

Configuration

Environment: Docker
Version: v0.4.1
Mode: direct
Command line (if not running as HA Addon):
Risco Panel model: Lightsys
Risco Panel firmware version:

Unsupported panel type : RW032:618V-MI

Salutations,
it also gives me the same error:

2/20/2022, 11:04:57 AM [debug] Command[4] Command response from Panel
2/20/2022, 11:04:57 AM [debug] Command[4] Emitting expected command response
2/20/2022, 11:04:57 AM [verbose] Command[4] Received data from panel: PNLCNF=RW032:618V-MI
2/20/2022, 11:04:57 AM [debug] Command[4] SendCommand receive this response : PNLCNF=RW032:618V-MI
/app/node_modules/@vanackej/risco-lan-bridge/dist/RiscoComm.js:344
throw new Error(Unsupported panel type : ${panelType});
^
Error: Unsupported panel type : RW032:618V-MI
at RiscoComm. (/app/node_modules/@vanackej/risco-lan-bridge/dist/RiscoComm.js:344:27)
at Generator.next ()
at fulfilled (/app/node_modules/tslib/tslib.js:114:62)

The alarm is a Agility4.

Thanks

Restart needed on cloud disconnect

Describe the bug
Hi @vanackej , using the addon with cloud proxy method... Yesteday i had a small internet interrupt, but after internet was restored, the addon was not able to connect to cloud anymore, i had to restart the addon to make it functional... It possible on this type of event as in screenshot, that the service can be restarted? I had watchdog enabled, but that doesnt help, since addon keeps on running

Thnx in advance

Configuration

Environment: Addon
Version: 0.5.0. beta 2
Mode: Proxy
Risco Panel model: Lightsys2
Risco Panel firmware version: 2.x

Logs

I only have a screenshot:

Node Red

Hi,

do you have any plan for making a Node-Red's palette with this project? Or how do you suggest to use it with Node red?
Thanks

Connection to panel works only when bad password provided

Describe the bug
Connection to panel works only when bad password provided

Configuration

Environment: docker
Version: 0.3.5
Command line: docker run -d -p 33000:33000 --name risco -v $(pwd)/config.json:/data/config.json vanackej/risco-mqtt-local:latest
Risco Panel model: LightSys/RP432,
Risco Panel firmware version: FW 2.59

Logs
Correct password:

Loading config from: /data/config.json
2/20/2022, 11:12:25 AM [info] autoConnect enabled, starting communication
2/20/2022, 11:12:25 AM [info] Connecting to mqtt server: mqtt://192.168.10.100:1883
2/20/2022, 11:12:26 AM [info] Connected on mqtt server: mqtt://192.168.10.100:1883
2/20/2022, 11:12:26 AM [info] Panel is not connected, waiting
2/20/2022, 11:12:34 AM [warn] Command[1] 'RMT=5678' Timeout
2/20/2022, 11:12:34 AM [warn] Bad Panel Id: 1. Trying to find the right one
2/20/2022, 11:12:37 AM [error] No remaining possible Panel Id, abandon
2/20/2022, 11:12:37 AM [error] Unable to connect to the control panel.
2/20/2022, 11:12:38 AM [warn] Command[51] Wrong CRC value for the response.
2/20/2022, 11:12:40 AM [warn] Command[51] receivedId is the same as lastReceivedId, ignoring this panel message
2/20/2022, 11:12:42 AM [warn] Command[4] 'DCN' Timeout
2/20/2022, 11:12:42 AM [warn] Command[NaN] Wrong CRC value for the response.
2/20/2022, 11:12:43 AM [warn] Command[50] Wrong CRC value for the response.
2/20/2022, 11:12:46 AM [warn] Command[50] receivedId is the same as lastReceivedId, ignoring this panel message
2/20/2022, 11:12:47 AM [warn] Command[4] 'DCN' Timeout
2/20/2022, 11:12:48 AM [warn] Command[NaN] Wrong CRC value for the response.
2/20/2022, 11:12:49 AM [warn] Command[50] receivedId is the same as lastReceivedId, ignoring this panel message
2/20/2022, 11:12:52 AM [warn] Command[53] Wrong CRC value for the response.
2/20/2022, 11:12:52 AM [warn] Command[4] 'DCN' Timeout
2/20/2022, 11:12:53 AM [warn] Command[NaN] Wrong CRC value for the response.
2/20/2022, 11:12:55 AM [warn] Command[53] receivedId is the same as lastReceivedId, ignoring this panel message
2/20/2022, 11:12:57 AM [warn] Command[4] 'DCN' Timeout
2/20/2022, 11:12:58 AM [warn] Command[NaN] Wrong CRC value for the response.
2/20/2022, 11:12:58 AM [warn] Command[53] receivedId is the same as lastReceivedId, ignoring this panel message
2/20/2022, 11:13:01 AM [warn] Command[52] Wrong CRC value for the response.
2/20/2022, 11:13:02 AM [warn] Command[4] 'DCN' Timeout
2/20/2022, 11:13:03 AM [warn] Command[NaN] Wrong CRC value for the response.
2/20/2022, 11:13:04 AM [warn] Command[52] receivedId is the same as lastReceivedId, ignoring this panel message
2/20/2022, 11:13:07 AM [warn] Command[52] receivedId is the same as lastReceivedId, ignoring this panel message
2/20/2022, 11:13:07 AM [warn] Command[4] 'DCN' Timeout
2/20/2022, 11:13:08 AM [warn] Command[NaN] Wrong CRC value for the response.
2/20/2022, 11:13:10 AM [error] Command[5] Too many bad CRC value.
2/20/2022, 11:13:12 AM [warn] Command[4] 'DCN' Timeout
2/20/2022, 11:13:13 AM [error] Command[NaN] Too many bad CRC value.
2/20/2022, 11:13:13 AM [warn] Command[5] receivedId is the same as lastReceivedId, ignoring this panel message

Wrong password:

Loading config from: /data/config.json
2/20/2022, 11:13:31 AM [info] autoConnect enabled, starting communication
2/20/2022, 11:13:31 AM [info] Connecting to mqtt server: mqtt://192.168.10.100:1883
2/20/2022, 11:13:31 AM [info] Connected on mqtt server: mqtt://192.168.10.100:1883
2/20/2022, 11:13:31 AM [info] Panel is not connected, waiting
2/20/2022, 11:13:36 AM [warn] Command[1] 'RMT=56788' Timeout
2/20/2022, 11:13:37 AM [warn] Command[1] Receipt of an error code: Invalid Value
2/20/2022, 11:13:37 AM [warn] Provided password is incorrect
2/20/2022, 11:13:37 AM [info] Trying to guess password (brut force)
2/20/2022, 11:13:37 AM [info] Trying passwords from 0000 to 9999...
2/20/2022, 11:13:37 AM [info] 0000 to 0099...
2/20/2022, 11:13:42 AM [info] 0100 to 0199...
2/20/2022, 11:13:47 AM [info] 0200 to 0299...
2/20/2022, 11:13:53 AM [info] 0300 to 0399...
2/20/2022, 11:13:58 AM [info] 0400 to 0499...
2/20/2022, 11:14:03 AM [info] 0500 to 0599...
2/20/2022, 11:14:08 AM [info] 0600 to 0699...
2/20/2022, 11:14:14 AM [info] 0700 to 0799...
2/20/2022, 11:14:19 AM [info] 0800 to 0899...
2/20/2022, 11:14:24 AM [info] 0900 to 0999...
...
2/20/2022, 11:19:22 AM [info] Discovered Access Code : 5678
2/20/2022, 11:19:23 AM [info] Panel info: LightSys/RP432, FW 2.59
2/20/2022, 11:19:23 AM [info] Panel options: 4 parts, 32 zones, 14 outputs, Pir Cam support: false
2/20/2022, 11:19:26 AM [warn] Command[16] Receipt of an error code: Device Doesn't Exists
2/20/2022, 11:19:26 AM [info] Output does not exists, stopping outputs discovery
2/20/2022, 11:19:26 AM [info] Panel is ready, subscribing to panel partitions and zones events
2/20/2022, 11:19:26 AM [info] Panel and MQTT communications are ready
2/20/2022, 11:19:26 AM [info] Publishing Home Assistant discovery info

Add-on Socketmode: Proxy not trying to connect to cloud

The config file has the necessary entries to run in Socketmode: proxy, but from the logs it seem to not even attempt to connect to cloud.

Environment: HA Addon - RPi4, built form instructions published on issue #27
Version: v0.4.2
Mode: proxy
Risco Panel model: Lightsys2 (2016 installed)
Risco Panel firmware version: 6.07

[services.d] starting services
[services.d] done.
Loading config from: /config/risco-mqtt.json
6/28/2022, 9:43:19 PM [info] autoConnect enabled, starting communication
6/28/2022, 9:43:19 PM [info] Connecting to mqtt server: mqtt://192.168.1.2:1883
6/28/2022, 9:43:20 PM [info] Connected on mqtt server: mqtt://192.168.1.2:1883
6/28/2022, 9:43:20 PM [info] Panel is not connected, waiting
6/28/2022, 9:43:20 PM [warn] Command[NaN] Wrong CRC value for the response.
6/28/2022, 9:43:21 PM [info] Panel info: LightSys/RP432, FW 6.07
6/28/2022, 9:43:21 PM [info] Panel options: 4 parts, 50 zones, 32 outputs, Pir Cam support: false
6/28/2022, 9:43:21 PM [info] Starting devices discovery
6/28/2022, 9:43:21 PM [info] Retrieving System Information
6/28/2022, 9:43:21 PM [info] Retrieving zones configuration
6/28/2022, 9:43:40 PM [info] Retrieving outputs configuration
6/28/2022, 9:43:45 PM [warn] Command[24] Receipt of an error code: Device Doesn't Exists
6/28/2022, 9:43:45 PM [warn] Got error while fetching output 23 data: N19
6/28/2022, 9:43:45 PM [info] Output 23 does not exists, stopping outputs discovery
6/28/2022, 9:43:45 PM [info] Retrieving partitions configuration
6/28/2022, 9:43:46 PM [info] Panel and MQTT communications are ready
6/28/2022, 9:43:47 PM [info] Publishing Home Assistant discovery info

Any assistance will be appreciated to get this running as intended. I have rebuild the add-on a few times, and cross checked my config against other forum users and it seems to be correct. I add my config below.

{
  "log": "info",
  "panel": {
    "panelIp": "192.168.1.4",
    "panelPort": 1000,
    "panelPassword": 5678,
    "panelId": "0001",
    "SocketMode": "proxy",
    "watchDogInterval": 10000,
    "DiscoverCode": true,
    "guessPasswordAndPanelId": false,
    "Disable_RiscoCloud": true,
    "Enable_RiscoCloud": true,
    "autoDiscover": false,
    "ListeningPort": 33000,
    "cloudUrl": "www.riscocloud.com",
    "cloudPort": 33000
  },
  "mqtt": {
    "url": "mqtt://192.168.1.2:1883",
    "username": "<redacted>",
    "password": "<redacted>"
  },
  "zones": {
    "default": {
      "off_delay": 0
    }
  }
}

Support group arming

Risco systems allow arming of groups.
There are 4 groups - A,B,C,D - and the list of zones associated with each one can be customized by the installer. This allows you to have more than just the default 2 arming modes (AWAY and STAY).
The native HA integration, based on Risco Cloud, has support for group arming. Through the integration options, you can control the mapping from Risco states to HA states (e.g. when group A or B is armed in Risco, HA will report this as Armed Night), and from HA to Risco (e.g. when arming in night mode in HA, arm group A in Risco). The integration documentation also lists the default mapping.

Can we add group arming support to local Risco version? More than happy to help in any way I can.

Cloud proxy issues after risco update on www.riscocloud.com

Describe the bug
Risco did today a maintenance update on riscocloud, so it was disconnected today, but after a few hours the disconencts were happening again, i see retrys, but it doesnt reconnect anymore...
When i do restart the add-on manually, then it works first time ?

maybe there are still issues on risco site, will see if it happens tomorrow also

Configuration

Environment: Addon
Version: 0.4.1
Mode: proxy
Command line (if not running as HA Addon):
Risco Panel model: Lightsys 2
Risco Panel firmware version: 2.73

Logs

3/8/2022, 4:31:38 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:31:56 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:32:01 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:32:18 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:32:23 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:32:44 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:32:49 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:33:10 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:33:15 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:33:35 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:33:37 PM [warn] [Panel => Cloud] Cloud socket not connected, discarding packet: [2,19,53,52,4,112,0,10,0,11,0,0,21,129,0,16,3,0,0,4,55,51,22,34,16,3,8,0,0,7,0,0,0,0,0,0,1,5,0,0,0,0,0,16,3,5,0,0,0,0,0,4,5,0,0,0,0,0,5,10,0,0,0,0,0,0,0,0,0,0,7,11,0,0,0,0,0,0,0,0,0,0,0,8,7,0,0,0,0,0,0,0,9,11,0,0,0,0,0,0,0,0,0,0,0,11,16,3,0,0,0,12,4,131,0,0,0,13,4,15,0,0,0,23,53,49,70,50,3]
3/8/2022, 4:33:40 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:34:00 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:34:05 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:34:25 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:34:30 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:34:48 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:34:53 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:35:11 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:35:16 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:35:32 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:35:37 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:35:55 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:36:00 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:36:23 PM [error] RiscoCloud Socket: close. Retrying within 5sec...
3/8/2022, 4:36:28 PM [info] RiscoCloud Socket: ready
3/8/2022, 4:36:48 PM [error] RiscoCloud Socket: close. Retrying within 5sec...

Errors duirng communication with the Agility 4 panel and unavailable entities in HA

Describe the bug
Tried to use app for first time. Getting a lot of errors(attached) and unavailable devices in HA.

Configuration

Environment: Docker
Mode: direct
Risco Panel model: Agility 4/RW032:618VGMI

Logs

Copy/paste the application logs here (or add them as attachement) :
- With debug log level enabled
- Including startup logs
- You are responsible of removing any sensitive information, like MQTT and panel credentials

Copy/paste the commands csv logs here (or add them as attachemnts) :
See commandsLog option in documentation

Additional context
Add any other context about the problem here.

{
"log": "info",
"panel": {
"panelIp": "192.168.10.111",
"panelPort": 1000,
"panelPassword": "xxxx",
"panelId": 1,
"watchDogInterval": 10000,
"commandsLog": false,
"autoConnect": true,
"socketMode": "direct",
"encoding": "latin1"
},
"ha_discovery_prefix_topic": "homeassistant",
"panel_name": "MyHome Alarm",
"mqtt": {
"url": "mqtt://192.168.10.105:1883",
"username": "xxxx",
"password": "xxxx"
},
"zones": {
"default": {
"off_delay": 30,
"name_prefix": "Sensor - "
}
}
}

No MQTT

Hey, as discussed on other thread, i dont see any mqtt ?

what could be wrong? i dont see any mqtt login in my add-on eiter, that means the addon is not even trying to connect and send data?
what could be wrong?
this is my config.json i use for the add-on

{
  "name": "Risco MQTT Bridge",
  "version": "2",
  "slug": "risco-mqtt-local",
  "description": "Risco Local/Cloud Integration",
  "startup": "application",
  "arch": ["aarch64", "amd64", "armhf", "armv7", "i386"],
  "host_network": true,
  "ports": {
    "33000/tcp": 33000
  },	
  "log": "debug",
  "panel": {
    "Panel_IP": "192.168.0.232",
    "Panel_Port": 1000, 
    "Panel_Password": 5678,
    "Panel_Id": "0001",
    "WatchDogInterval": 10000,
	"Disable_RiscoCloud":  true,
	"Enable_RiscoCloud":  true,
	"DiscoverCode":  false,
	"SocketMode": "proxy",
	"ListeningPort": 33000,
	"CloudPort": 33000,
	"CloudUrl": "www.riscocloud.com"
  },
  "mqtt": {
    "url": "mqtt://localhost:1833",
    "username": "xxx",
    "password": "xxx",
    "zone-label-prefix": ""
  }  
}

i actually stuff bout the zones, but i dont see there mqtt messages either?

Command CRC Value : A18D
CRC Ok
Data from Panel, need to send an ACK.
Sending Ack.
Command CRC Value : 5E37
Received From Panel : ZSTT5=O---------
Zone Status datas.
Zones Status Changed :
 Zone Id 5
 New Status: Open

Error with amd64 image at launch

Hi,

Since beta 1, I have this error message when I start risco local mqtt

Image ghcr.io/vanackej/risco-mqtt-local-addon-amd64:0.5.0-beta.2 does not exist for addon_c774f33c_risco-mqtt-local-addon

Any clue?

Thank you ,

Cheers

container does not work on ARM (raspberry pi)

Describe the bug
Container image does not work on arm raspberry pi (arm).
When I downloaded image I saw message like above:

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

Configuration

Environment: Docker
Version: latest

Logs

standard_init_linux.go:219: exec user process caused: exec format error
standard_init_linux.go:219: exec user process caused: exec format error
standard_init_linux.go:219: exec user process caused: exec format error

Seperete proxy addon/container

Hey @vanackej

Local is coming verry soon to HA as an official integration , thnx to OnFreund
home-assistant/core#75874

But it lacks a proxy....

Can you help me setting up just an addon to act as a proxy? nothing more, nothing less, so we can make use of the official integration, witt our older boards ( cloud enabled )

The proxy is already part of this addon, would be great if you can split it up into a new addon

Or if you can give me a hand so can start with it?

much appreciated

ProSYS Plus issue

Hi,

I've been testing this addon on ProSYS Plus with the example json config, I've been able to connect to the panel but the log shows this timeout loop on startup and after a while it just throws an error and stops.
Any ideas?

Add delay between socket connect and RMT command

I cannot get working my LightSys 2 with RW132IP.
I think it can be fixed with:
TJForc/risco-lan-bridge#12
Can you add delay to your code for older panels?

I see that code loops and panel timeouts. When I stop container it instantly logs panel model, info about partitions, etc and exits. So it's working for a sec before exiting container.

Discussion about problem: TJForc/risco-lan-bridge#10

RiscoCloud Socket Destroyed

Hi @vanackej , updated to new 0.3.1, did some restarts of the add-on, but still seeing error below , if this error occurs, then the add-on is in a crashed state...

thnx for looking into it


1/3/2022, 1:39:18 PM [debug] [Panel => Cloud] Forwarding panel packet to cloud: [2,19,57,51,4,6,0,5,0,16,3,0,0,0,23,54,49,70,51,3]
1/3/2022, 1:39:18 PM [error] Panel Socket Closed.
1/3/2022, 1:39:18 PM [debug] RiscoCloud Socket Destroyed.
1/3/2022, 1:39:18 PM [error] TCP Socket Disconnected
1/3/2022, 1:39:29 PM [verbose] Start Connection to Panel
1/3/2022, 1:39:29 PM [debug] TCP Socket is already created, Connect It
1/3/2022, 1:39:29 PM [debug] TCP Socket must be created now
1/3/2022, 1:39:29 PM [info] Listening on IP :: and Port 33000
1/3/2022, 1:39:29 PM [info] Waiting for panel incoming connection... This can take up to 1 or 2 minutes
node:internal/process/promises:246
          triggerUncaughtException(err, true /* fromPromise */);
          ^
AssertionError [ERR_ASSERTION]: Expected 'isPanelSocketConnected' to be true, but received false. Socket failed to connect after 100ms delay
    at new AssertionError (node:internal/assert/assertion_error:466:5)
    at assertIsTrue (/usr/src/app/node_modules/@vanackej/risco-lan-bridge/dist/Assertions.js:15:15)
    at RiscoProxyTCPSocket.<anonymous> (/usr/src/app/node_modules/@vanackej/risco-lan-bridge/dist/RiscoBaseSocket.js:522:43)
    at Generator.next (<anonymous>)
    at /usr/src/app/node_modules/tslib/tslib.js:117:75
    at new Promise (<anonymous>)
    at __awaiter (/usr/src/app/node_modules/tslib/tslib.js:113:16)
    at RiscoProxyTCPSocket.panelConnect (/usr/src/app/node_modules/@vanackej/risco-lan-bridge/dist/RiscoBaseSocket.js:521:38)
    at RiscoProxyTCPSocket.<anonymous> (/usr/src/app/node_modules/@vanackej/risco-lan-bridge/dist/RiscoProxySocket.js:157:32)
    at Generator.next (<anonymous>) {
  generatedMessage: false,
  code: 'ERR_ASSERTION',
  actual: undefined,
  expected: undefined,
  operator: undefined
}

mqtt auto discovery problem

Hi. Zones with polish letters (ą,ę, etc) and other characters like dot (.) cannot be autoregistered. I see warning in Home Assistant log and entity is not added:

2022-01-13 10:05:05 WARNING (MainThread) [homeassistant.components.mqtt.discovery] Received message on illegal discovery topic 'homeassistant/binary_sensor/Garaż/11/config'
2022-01-13 10:16:21 WARNING (MainThread) [homeassistant.components.mqtt.discovery] Received message on illegal discovery topic 'homeassistant/binary_sensor/P.Klary/8/config'

I think that for auto configuration object_id should be based on unique_id like risco-alarm-panel-1-zone-7, not the current name of zone (P.Franka):
2022-01-13 10:16:21 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on homeassistant/binary_sensor/P.Franka/7/config: b'{"availability":{"topic":"riscopanel/alarm/status"},"unique_id":"risco-alarm-panel-1-zone-7","payload_on":"1","payload_off":"0","device_class":"motion","qos":1,"state_topic":"riscopanel/alarm/1/sensor/7/status","json_attributes_topic":"riscopanel/alarm/1/sensor/7","name":"P.Franka"}'

See: https://www.home-assistant.io/docs/mqtt/discovery/#discovery-topic
<object_id>: The ID of the device. This is only to allow for separate topics for each device and is not used for the entity_id. The ID of the device must only consist of characters from the character class [a-zA-Z0-9_-] (alphanumerics, underscore and hyphen).
This will allow adding partitions with any name.

Update issue to 0.4.3

Hey @vanackej

I saw an update for addon, but it doesn't start anymore with error below

Image ghcr.io/vanackej/risco-mqtt-local-addon-amd64:0.4.3 does not exist for addon_c774f33c_risco-mqtt-local-addon

Can't find panel id

Trying to do a proxy install of risco-mqtt-local, have changed ip on panel to point to my docker instance. When i enable debug i can see that the proxy sends commands back and forth, so that part works.
I can also see in the logs below that the app can retrieve the zones, but it does complain about the panel id not being able to find it. I tried entering the CPID (11 characters) and also panel_id = 1 as seen in the doc, none works.

I just realised i used a forked version from @markxroberts , but i can't create issues on his fork.
Edit: i just tried the vanackej version also, latest from docker hub.

{
	"log": "verbose",
	"panel": {
		"panelIp": "192.168.0.5",
		"panelPort": 1000,
		"panelPassword": 5678,
		"panelId": 1,
		"watchDogInterval": 10000,
		"socketMode": "proxy",
		"commandsLog": false,
		"cloudUrl": "www.riscocloud.com",
		"cloudPort": 33000
	},

[+] Running 1/0
 ✔ Container risco-mqtt-local  Created                                                                                                                            0.0s
Attaching to risco-mqtt-local
risco-mqtt-local  | Loading config from: /data/config.json
risco-mqtt-local  | 3/19/2024, 4:33:07 PM [info] autoConnect enabled, starting communication
risco-mqtt-local  | 3/19/2024, 4:33:07 PM [verbose] Start Connection to Panel
risco-mqtt-local  | 3/19/2024, 4:33:07 PM [info] [RML] Connecting to mqtt server: mqtt://192.168.0.1:1883
risco-mqtt-local  | 3/19/2024, 4:33:07 PM [info] Listening on IP :: and Port 33000
risco-mqtt-local  | 3/19/2024, 4:33:07 PM [info] Waiting for panel incoming connection... This can take up to 1 or 2 minutes
risco-mqtt-local  | 3/19/2024, 4:33:07 PM [info] [RML] Connected on mqtt server: mqtt://192.168.0.1:1883
risco-mqtt-local  | 3/19/2024, 4:33:07 PM [info] [RML] Panel is not connected, waiting
risco-mqtt-local  | 3/19/2024, 4:33:08 PM [info] Incoming connection from panel received
risco-mqtt-local  | 3/19/2024, 4:33:08 PM [info] RiscoCloud Socket: ready
risco-mqtt-local  | 3/19/2024, 4:33:08 PM [info] Setting a timer for panel connection in 30000 ms
risco-mqtt-local  | 3/19/2024, 4:33:38 PM [verbose] Authenticating to the panel
risco-mqtt-local  | 3/19/2024, 4:33:38 PM [verbose] Command[1] Sending Command: RMT=5678
risco-mqtt-local  | 3/19/2024, 4:33:39 PM [verbose] Command[1] Received data: ACK, crcOk: true
risco-mqtt-local  | 3/19/2024, 4:33:39 PM [verbose] Command[2] Sending Command: LCL
risco-mqtt-local  | 3/19/2024, 4:33:39 PM [verbose] Command[2] Received data: ACK, crcOk: true
risco-mqtt-local  | 3/19/2024, 4:33:39 PM [verbose] Setting up encryption using Panel Id
risco-mqtt-local  | 3/19/2024, 4:33:39 PM [verbose] Command[50] Received data: CLOCK=19/03/2024 16:33, crcOk: true
risco-mqtt-local  | 3/19/2024, 4:33:39 PM [verbose] Command[3] Sending Command: ZLBL*1:8?
risco-mqtt-local  | 3/19/2024, 4:33:40 PM [verbose] Command[3] Received data: ZLBL*1:8=R�kdetektor Uppe R�relse Kontoret        R�relse Ovanv�ni        Kamera VardagsrMagnet Grov-ing Magnet Fin-ing  Kamera Entre    Magnet Altan, crcOk: false
risco-mqtt-local  | 3/19/2024, 4:33:40 PM [verbose] Command[3] inCryptTest enabled, emitting response without checks to latest sent command
risco-mqtt-local  | 3/19/2024, 4:33:40 PM [warn] Bad Panel Id: 1. Trying to find the right one
risco-mqtt-local  | 3/19/2024, 4:33:41 PM [error] No remaining possible Panel Id, abandon
risco-mqtt-local  | 3/19/2024, 4:33:41 PM [error] Unable to connect to the control panel.
risco-mqtt-local  | 3/19/2024, 4:33:41 PM [verbose] Command[4] Sending Command: DCN
risco-mqtt-local  | 3/19/2024, 4:33:41 PM [verbose] Command[NaN] Received data: L5, crcOk: false
risco-mqtt-local  | 3/19/2024, 4:33:41 PM [warn] Command[NaN] Wrong CRC value for the response.
risco-mqtt-local  | 3/19/2024, 4:33:42 PM [verbose] Command[75] Received data: 75, crcOk: false
risco-mqtt-local  | 3/19/2024, 4:33:42 PM [warn] Command[75] Wrong CRC value for the response.
risco-mqtt-local  | 3/19/2024, 4:33:45 PM [verbose] Command[75] Received data: 75, crcOk: false
risco-mqtt-local  | 3/19/2024, 4:33:45 PM [warn] Command[75] Wrong CRC value for the response.
risco-mqtt-local  | 3/19/2024, 4:33:46 PM [warn] Command[4] 'DCN' Timeout
risco-mqtt-local  | 3/19/2024, 4:33:46 PM [warn] Risco command error: TIMEOUT. Command: {"panelId":0,"commandId":4,"attempts":1,"crcOk":false,"commandStr":"DCN","sentBuffer":{"type":"Buffer","data":[2,17,48,52,68,67,78,23,65,53,50,52,3]}}
risco-mqtt-local  | 3/19/2024, 4:33:46 PM [warn] Error while sending DCN command
risco-mqtt-local  | 3/19/2024, 4:33:46 PM [info] TCP Socket Disconnected
risco-mqtt-local  | 3/19/2024, 4:33:46 PM [info] Won't attempt automatic reconnection

HA add-on won't start

Describe the bug
I'm stuck in getting the add-on to run in Home Assistant. Installation of the add-on works fine, and even got an update notification a few days ago, so that seems ok. However when I try to start the add-on, I immediately get errors that it fails to start. risco-mqtt.json is in place in the config folder, but whether or not it is there, same result. Any idea what I'm missing here? The logs don't tell much, except it fails to start.

Configuration

Environment: HA Addon (Home Assistant OS 7.4)
Version: v0.4.1
Docker version: 20.10.9

Logs
In the add-on log;

[FATAL tini (8)] exec docker-entrypoint.sh failed: Exec format error

In the HA supervisor log:

22-03-02 19:31:20 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on c774f33c/aarch64-addon-risco-mqtt-local-addon with version 0.4.1
22-03-02 19:31:21 ERROR (SyncWorker_7) [supervisor.docker.interface] Container addon_c774f33c_risco-mqtt-local-addon is not running

Device Doesnt Exists LightSys

Here is my log output, the panel connects but stops discovery after saying device doesn't exists

Loading config from: /config/risco-mqtt.json
2/20/2022, 8:17:16 PM [info] autoConnect enabled, starting communication
2/20/2022, 8:17:16 PM [info] Connecting to mqtt server: mqtt://192.168.3.159:1883
2/20/2022, 8:17:16 PM [info] Connected on mqtt server: mqtt://192.168.3.159:1883
2/20/2022, 8:17:16 PM [info] Panel is not connected, waiting
2/20/2022, 8:17:17 PM [info] Panel info: LightSys/RP432, FW 5.93
2/20/2022, 8:17:17 PM [info] Panel options: 4 parts, 50 zones, 32 outputs, Pir Cam support: false
2/20/2022, 8:17:26 PM [warn] Command[7] Receipt of an error code: Device Doesn't Exists
2/20/2022, 8:17:26 PM [info] Output does not exists, stopping outputs discovery
/app/node_modules/@vanackej/risco-lan-bridge/dist/RiscoComm.js:680
Item.Label = PLabels[j].trim();
^
TypeError: Cannot read properties of undefined (reading 'trim')
at RiscoComm. (/app/node_modules/@vanackej/risco-lan-bridge/dist/RiscoComm.js:680:45)
at Generator.next ()
at fulfilled (/app/node_modules/tslib/tslib.js:114:62)

Configuration

Environment: [HA Addon]
Version: [Latest as of today 20-2-22]
Risco Panel model: LightSys RP432
Risco Panel firmware version: FW 5.93

The panel connects correctly through the official "cloud" app, so it does exist on my network and the panel does indeed have an internet connection.

Wrong CRC value

Hi there,

I'm trying to get this package to work in proxy mode but I get an error saying that the CRC is not valid.

3/13/2022, 9:35:28 AM [debug] Local GMT Timezone is : +00:00
3/13/2022, 9:35:28 AM [info] autoConnect enabled, starting communication
3/13/2022, 9:35:28 AM [verbose] Start Connection to Panel
3/13/2022, 9:35:28 AM [debug] TCP Socket is not already created, Create It
3/13/2022, 9:35:28 AM [debug] TCP Socket must be created now
3/13/2022, 9:35:28 AM [info] Connecting to mqtt server: mqtt://x.x.x.x:1883
3/13/2022, 9:35:28 AM [info] Listening on IP :: and Port 33000
3/13/2022, 9:35:28 AM [info] Waiting for panel incoming connection... This can take up to 1 or 2 minutes
3/13/2022, 9:35:28 AM [info] Connected on mqtt server: mqtt://x.x.x.x:1883
3/13/2022, 9:35:28 AM [info] Panel is not connected, waiting
3/13/2022, 10:56:05 AM [info] Incoming connection from panel received
3/13/2022, 10:56:05 AM [debug] RiscoCloud Socket: connect
3/13/2022, 10:56:05 AM [info] RiscoCloud Socket: ready
3/13/2022, 10:56:05 AM [info] Setting a timer for panel connection in 30000 ms
3/13/2022, 10:56:06 AM [debug] [Panel => Bridge] Received unencrypted data Buffer from Panel : [71,69,84,32,47,32,...
3/13/2022, 10:56:06 AM [debug] Received data Buffer : [71,69,84,32,47,...
3/13/2022, 10:56:06 AM [debug] Command[NaN] CRC Value : FFFF
3/13/2022, 10:56:06 AM [debug] Command[NaN] CRC Not Ok
3/13/2022, 10:56:06 AM [warn] Command[NaN] Wrong CRC value for the response.
3/13/2022, 10:56:22 AM [error] Panel Socket Closed.
3/13/2022, 10:56:22 AM [debug] RiscoCloud Socket Destroyed.
3/13/2022, 10:56:22 AM [error] TCP Socket Disconnected

I haven't found anything point me in the right direction in the docs. Does anybody have a clue what is going wrong here?

Kr,
Thomas

Readme is wrong?

@vanackej
In readme you speak about config.json
But the actually file is config/risco-mqtt.json
A bit confusing :-)

Bind mount failed

I'm running Docker on Synology 918+ and when I put the below docker run command via SSH using putty

docker run -v $(pwd)/config.json:/volume1/docker/riscolocal/config/config.json vanackej/risco-mqtt-local

I get this error

docker: Error response from daemon: Bind mount failed: '/root/config.json' does not exists.
ERRO[0003] error waiting for container: context canceled

What am I doing wrong?
I have created the config.json and placed it config folder

Provide ARMv7 image

Please consider providing official addon images for ARMv7 (i.e. 32-bit RPi).

I have built such image myself and it's been running without issues on my RPi 3B+.

https://hub.docker.com/layers/swiergot/risco-mqtt-local/v0.4.2/images/sha256-4fd6a9fe4bacda0911603038a2eaaddbb9f0e8a6321b5a769ff21e227d7845eb?context=explore

Cannot read properties of undefined (reading sybstring) at risco ...

i rebooted my HassOS, and i noticed your addon was in a stopped state, sorry, i only have a screenshot of the issue, nog log .txt file

i think this one is related to your add-on?
sorry for creating so many issues, but just posting issues/errors i have, i think its usefull for later when more and more people are using it

Add ability to bypass a zone

Thanks for a terrific project.
It is working well for me.
I would love an option to bypass a zone. This would then be a complete replacement for RiscoCloud integration in HA for me. If it exists and I've missed it, my apologies!

Debugging possible?

hey @vanackej

as you know i have proxy enabled, i have the docker running for 1 day now, works verry good
but this night i got a mail notification that the panel was offline for a 10 minutes

can i debug this? how can i save thos debug to a file while running the addon?

thnx

Connection to panel works only when bad password provided

Hi. I tried 0.3.0 and 0.3.2 version and when panel password is correct I got warning about timeout and it starts guessing panel Id without success:

Loading config from: /usr/src/app/config.json
1/5/2022, 3:32:25 PM [info] autoConnect enabled, starting communication
1/5/2022, 3:32:25 PM [info] Connecting to mqtt server: mqtt://192.168.10.100:1883
1/5/2022, 3:32:25 PM [warn] Command[5] Command response was unexpected, ignoring. Data[N05]. sequenceId[1]
1/5/2022, 3:32:25 PM [warn] Command[5] Receipt of an error code: Invalid parameter
1/5/2022, 3:32:25 PM [info] Connected on mqtt server: mqtt://192.168.10.100:1883
1/5/2022, 3:32:25 PM [info] Panel is not connected, waiting
1/5/2022, 3:32:30 PM [warn] Command[1] 'RMT=5678' Timeout
1/5/2022, 3:32:30 PM [warn] Bad Panel Id: 1. Trying to find the right one
1/5/2022, 3:32:34 PM [error] No remaining possible Panel Id, abandon
1/5/2022, 3:32:34 PM [error] Unable to connect to the control panel.
1/5/2022, 3:32:34 PM [warn] Command[NaN] Wrong CRC value for the response.
1/5/2022, 3:32:35 PM [warn] Command[NaN] Wrong CRC value for the response.
1/5/2022, 3:32:38 PM [warn] Command[NaN] Wrong CRC value for the response.
1/5/2022, 3:32:39 PM [warn] Command[4] 'DCN' Timeout
1/5/2022, 3:32:39 PM [warn] Command[NaN] Wrong CRC value for the response.
1/5/2022, 3:32:41 PM [warn] Command[NaN] Wrong CRC value for the response.
1/5/2022, 3:32:44 PM [warn] Command[4] 'DCN' Timeout

But when I set bad panel password (1234 like in your example) it starts guessing password till 5678 and after that everything starts working correctly!!

Loading config from: /usr/src/app/config.json
1/5/2022, 3:37:11 PM [info] autoConnect enabled, starting communication
1/5/2022, 3:37:11 PM [info] Connecting to mqtt server: mqtt://192.168.10.100:1883
1/5/2022, 3:37:12 PM [warn] Command[null] Receipt of an error code: CRC Error
1/5/2022, 3:37:12 PM [info] Connected on mqtt server: mqtt://192.168.10.100:1883
1/5/2022, 3:37:12 PM [info] Panel is not connected, waiting
1/5/2022, 3:37:12 PM [warn] Command[null] Receipt of an error code: CRC Error
1/5/2022, 3:37:17 PM [warn] Command[1] 'RMT=56788' Timeout
1/5/2022, 3:37:17 PM [warn] Command[1] Receipt of an error code: Invalid Value
1/5/2022, 3:37:17 PM [warn] Provided password is incorrect
1/5/2022, 3:37:17 PM [info] Trying to guess password (brut force)
1/5/2022, 3:37:17 PM [info] Trying passwords from 0000 to 9999...
1/5/2022, 3:37:17 PM [info] 0000 to 0099...
1/5/2022, 3:37:22 PM [info] 0100 to 0199...
1/5/2022, 3:37:27 PM [info] 0200 to 0299...
1/5/2022, 3:37:32 PM [info] 0300 to 0399...
1/5/2022, 3:37:38 PM [info] 0400 to 0499...
1/5/2022, 3:37:43 PM [info] 0500 to 0599...
1/5/2022, 3:37:48 PM [info] 0600 to 0699...
1/5/2022, 3:37:54 PM [info] 0700 to 0799...
1/5/2022, 3:37:59 PM [info] 0800 to 0899...
1/5/2022, 3:38:04 PM [info] 0900 to 0999...
1/5/2022, 3:38:10 PM [info] 1000 to 1099...
1/5/2022, 3:38:17 PM [warn] Command[10] 'RMT=1037' Timeout
1/5/2022, 3:38:20 PM [info] 1100 to 1199...
...
1/5/2022, 3:42:48 PM [info] 5600 to 5699...
1/5/2022, 3:42:52 PM [info] Discovered Access Code : 5678
1/5/2022, 3:42:52 PM [info] Panel info: LightSys/RP432, FW 2.59
1/5/2022, 3:42:52 PM [info] Panel options: 4 parts, 32 zones, 14 outputs, Pir Cam support: false
1/5/2022, 3:43:00 PM [warn] Command[45] 'ZLBL*25:32?' Timeout
1/5/2022, 3:43:01 PM [warn] Command[16] Receipt of an error code: Device Doesn't Exists
1/5/2022, 3:43:01 PM [info] Output does not exists, stopping outputs discovery
1/5/2022, 3:43:01 PM [info] Panel is ready, subscribing to panel partitions and zones events
1/5/2022, 3:43:01 PM [info] Panel and MQTT communications are ready
1/5/2022, 3:43:01 PM [info] Publishing Home Assistant discovery info
1/5/2022, 3:43:01 PM [info] [Panel => MQTT][Discovery] Published alarm_control_panel to HA on partition 1
1/5/2022, 3:43:01 PM [info] [Panel => MQTT][Discovery] Published alarm_control_panel to HA on partition 2
1/5/2022, 3:43:01 PM [info] [Panel => MQTT][Discovery] Published alarm_control_panel to HA on partition 3
1/5/2022, 3:43:01 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Wiatrołap, HA name = Wiatrołap
...
Kotłownia
1/5/2022, 3:43:02 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Garaż, HA name = Garaż
1/5/2022, 3:43:02 PM [info] Subscribing to Home assistant commands topics
1/5/2022, 3:43:02 PM [info] Subscribe on riscopanel/alarm/1/set topic
1/5/2022, 3:43:02 PM [info] Subscribe on riscopanel/alarm/2/set topic
1/5/2022, 3:43:02 PM [info] Subscribe on riscopanel/alarm/3/set topic
1/5/2022, 3:43:02 PM [info] Publishing initial partitions and zones state to Home assistant
1/5/2022, 3:43:02 PM [info] [Panel => MQTT] Published alarm status disarmed on partition 1
1/5/2022, 3:43:02 PM [info] [Panel => MQTT] Published alarm status disarmed on partition 2
1/5/2022, 3:43:02 PM [info] [Panel => MQTT] Published alarm status disarmed on partition 3
1/5/2022, 3:43:02 PM [info] Initialization completed

Please check if it's not the same problem as described in: TJForc/risco-lan-bridge#11
Or maybe it's still problem with lack of 10s delay on start: #6
You also wrote in other thread:
I should maybe Introduce an option to disable panel crypto check at startup, and just assume that CRC errors are CRC errors, not an encryption issue...

correct_password.txt
wrong_password.txt

Failed to send CLOCK command && Add-on Crash

Describe the bug

Hi @vanackej , i had the error before also in the past, sure if its the same now, but i use the proxy method, when i take out the UTP cable or my network is down for a little white, it never reconnects again, i see a continues loop like below

I attached the logs, copy/pasted from where i took out the network cable

Seems also at the bottom of the log, it crashed the add-on, i think this is the first time i see this
The logs are starting when i took out the cable

thnx for looking into it!

Configuration

Environment: HA Addon
Version: 0.4.1
Mode: Proxy
Risco Panel model: Lightsys 2
Risco Panel firmware version: 2.72

Logs

3/15/2022, 7:43:53 AM [�[32minfo�[39m] Initialization completed
3/15/2022, 7:43:53 AM [�[36mverbose�[39m] System initialization completed.
3/15/2022, 7:43:56 AM [�[34mdebug�[39m] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,48,72,91,96,29,246,71,197,221,255,145,113,170,57,38,31,104,149,91,225,151,110,128,127,149,229,113,180,3]
3/15/2022, 7:43:56 AM [�[34mdebug�[39m] Received data Buffer : [2,17,55,48,72,91,96,29,246,71,197,221,255,145,113,170,57,38,31,104,149,91,225,151,110,128,127,149,229,113,180,3]
3/15/2022, 7:43:56 AM [�[34mdebug�[39m] Command[55] crcOK : true, Computed CRC : ED23, Message CRC: ED23
3/15/2022, 7:43:56 AM [�[36mverbose�[39m] Command[55] Received data: CLOCK=15/03/2022 07:44, crcOk: true
3/15/2022, 7:43:56 AM [�[34mdebug�[39m] Command[55] Data from Panel, need to send an ACK
3/15/2022, 7:43:56 AM [�[34mdebug�[39m] Command[55] Sending Ack.
3/15/2022, 7:43:56 AM [�[34mdebug�[39m] Command[55] Data type: Clock
3/15/2022, 7:43:56 AM [�[36mverbose�[39m] [Panel => MQTT] Published alarm online
3/15/2022, 7:44:03 AM [�[36mverbose�[39m] Command[14] Sending Command: CLOCK
3/15/2022, 7:44:03 AM [�[34mdebug�[39m] Command[14] Writing command buffer to socket: [2,17,51,49,72,91,96,29,246,109,176,219,231,152,3]
3/15/2022, 7:44:03 AM [�[34mdebug�[39m] Command[14] Data Sent : CLOCK
3/15/2022, 7:44:03 AM [�[34mdebug�[39m] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,51,49,72,91,96,29,246,71,197,221,255,145,113,170,57,38,31,104,149,91,225,151,110,128,127,229,229,113,197,3]
3/15/2022, 7:44:03 AM [�[34mdebug�[39m] Received data Buffer : [2,17,51,49,72,91,96,29,246,71,197,221,255,145,113,170,57,38,31,104,149,91,225,151,110,128,127,229,229,113,197,3]
3/15/2022, 7:44:03 AM [�[34mdebug�[39m] Command[14] crcOK : true, Computed CRC : 5D2B, Message CRC: 5D2B
3/15/2022, 7:44:03 AM [�[36mverbose�[39m] Command[14] Received data: CLOCK=15/03/2022 07:44, crcOk: true
3/15/2022, 7:44:03 AM [�[34mdebug�[39m] Command[14] Command response from Panel
3/15/2022, 7:44:03 AM [�[34mdebug�[39m] Command[14] Emitting expected command response
3/15/2022, 7:44:03 AM [�[34mdebug�[39m] Command[14] Data type: Clock
3/15/2022, 7:44:03 AM [�[36mverbose�[39m] [Panel => MQTT] Published alarm online
3/15/2022, 7:44:03 AM [�[34mdebug�[39m] Command[14] command response : CLOCK=15/03/2022 07:44
3/15/2022, 7:44:13 AM [�[36mverbose�[39m] Command[15] Sending Command: CLOCK
3/15/2022, 7:44:13 AM [�[34mdebug�[39m] Command[15] Writing command buffer to socket: [2,17,51,48,72,91,96,29,246,109,197,219,230,152,3]
3/15/2022, 7:44:13 AM [�[34mdebug�[39m] Command[15] Data Sent : CLOCK
3/15/2022, 7:44:18 AM [�[33mwarn�[39m] Command[15] 'CLOCK' Timeout
3/15/2022, 7:44:18 AM [�[36mverbose�[39m] Command[15] retrying command
3/15/2022, 7:44:18 AM [�[36mverbose�[39m] Command[15] Sending Command: CLOCK
3/15/2022, 7:44:18 AM [�[34mdebug�[39m] Command[15] Writing command buffer to socket: [2,17,51,48,72,91,96,29,246,109,197,219,230,152,3]
3/15/2022, 7:44:18 AM [�[34mdebug�[39m] Command[15] Data Sent : CLOCK
3/15/2022, 7:44:23 AM [�[33mwarn�[39m] Command[15] 'CLOCK' Timeout
3/15/2022, 7:44:23 AM [�[36mverbose�[39m] Command[15] retrying command
3/15/2022, 7:44:23 AM [�[36mverbose�[39m] Command[15] Sending Command: CLOCK
3/15/2022, 7:44:23 AM [�[34mdebug�[39m] Command[15] Writing command buffer to socket: [2,17,51,48,72,91,96,29,246,109,197,219,230,152,3]
3/15/2022, 7:44:23 AM [�[34mdebug�[39m] Command[15] Data Sent : CLOCK
3/15/2022, 7:44:28 AM [�[33mwarn�[39m] Command[15] 'CLOCK' Timeout
3/15/2022, 7:44:28 AM [�[36mverbose�[39m] Command[15] retrying command
3/15/2022, 7:44:28 AM [�[36mverbose�[39m] Command[15] Sending Command: CLOCK
3/15/2022, 7:44:28 AM [�[34mdebug�[39m] Command[15] Writing command buffer to socket: [2,17,51,48,72,91,96,29,246,109,197,219,230,152,3]
3/15/2022, 7:44:28 AM [�[34mdebug�[39m] Command[15] Data Sent : CLOCK
3/15/2022, 7:44:33 AM [�[33mwarn�[39m] Command[15] 'CLOCK' Timeout
3/15/2022, 7:44:33 AM [�[34mdebug�[39m] Command[15] command response : undefined

deleted some loops here

3/15/2022, 7:59:04 AM [�[33mwarn�[39m] Failed to send CLOCK command: RiscoCommandError: Risco command error: TIMEOUT. Command: {"panelId":1,"commandId":44,"attempts":4,"crcOk":false,"commandStr":"CLOCK","sentBuffer":{"type":"Buffer","data":[2,17,54,49,72,91,96,29,246,109,177,171,146,152,3]}}
3/15/2022, 7:59:13 AM [�[31merror�[39m] RiscoCloud Socket: close. Retrying within 5sec...
3/15/2022, 7:59:14 AM [�[36mverbose�[39m] Command[45] Sending Command: CLOCK
3/15/2022, 7:59:14 AM [�[34mdebug�[39m] Command[45] Writing command buffer to socket: [2,17,54,48,72,91,96,29,246,109,198,171,145,152,3]
3/15/2022, 7:59:14 AM [�[34mdebug�[39m] Command[45] Data Sent : CLOCK
3/15/2022, 7:59:18 AM [�[34mdebug�[39m] RiscoCloud Socket: connect
3/15/2022, 7:59:18 AM [�[32minfo�[39m] RiscoCloud Socket: ready
3/15/2022, 7:59:19 AM [�[33mwarn�[39m] Command[45] 'CLOCK' Timeout
3/15/2022, 7:59:19 AM [�[36mverbose�[39m] Command[45] retrying command
3/15/2022, 7:59:19 AM [�[36mverbose�[39m] Command[45] Sending Command: CLOCK
3/15/2022, 7:59:19 AM [�[34mdebug�[39m] Command[45] Writing command buffer to socket: [2,17,54,48,72,91,96,29,246,109,198,171,145,152,3]
3/15/2022, 7:59:19 AM [�[34mdebug�[39m] Command[45] Data Sent : CLOCK
3/15/2022, 7:59:24 AM [�[33mwarn�[39m] Command[45] 'CLOCK' Timeout
3/15/2022, 7:59:24 AM [�[36mverbose�[39m] Command[45] retrying command
3/15/2022, 7:59:24 AM [�[36mverbose�[39m] Command[45] Sending Command: CLOCK
3/15/2022, 7:59:24 AM [�[34mdebug�[39m] Command[45] Writing command buffer to socket: [2,17,54,48,72,91,96,29,246,109,198,171,145,152,3]
3/15/2022, 7:59:24 AM [�[34mdebug�[39m] Command[45] Data Sent : CLOCK
3/15/2022, 7:59:29 AM [�[33mwarn�[39m] Command[45] 'CLOCK' Timeout
3/15/2022, 7:59:29 AM [�[36mverbose�[39m] Command[45] retrying command
3/15/2022, 7:59:29 AM [�[36mverbose�[39m] Command[45] Sending Command: CLOCK
3/15/2022, 7:59:29 AM [�[34mdebug�[39m] Command[45] Writing command buffer to socket: [2,17,54,48,72,91,96,29,246,109,198,171,145,152,3]
3/15/2022, 7:59:29 AM [�[34mdebug�[39m] Command[45] Data Sent : CLOCK
3/15/2022, 7:59:34 AM [�[33mwarn�[39m] Command[45] 'CLOCK' Timeout
3/15/2022, 7:59:34 AM [�[34mdebug�[39m] Command[45] command response : undefined
3/15/2022, 7:59:34 AM [�[33mwarn�[39m] Failed to send CLOCK command: RiscoCommandError: Risco command error: TIMEOUT. Command: {"panelId":1,"commandId":45,"attempts":4,"crcOk":false,"commandStr":"CLOCK","sentBuffer":{"type":"Buffer","data":[2,17,54,48,72,91,96,29,246,109,198,171,145,152,3]}}
3/15/2022, 7:59:37 AM [�[31merror�[39m] RiscoCloud Socket: close. Retrying within 5sec...
3/15/2022, 7:59:42 AM [�[34mdebug�[39m] RiscoCloud Socket: connect
3/15/2022, 7:59:42 AM [�[32minfo�[39m] RiscoCloud Socket: ready
3/15/2022, 7:59:44 AM [�[36mverbose�[39m] Command[46] Sending Command: CLOCK
3/15/2022, 7:59:44 AM [�[34mdebug�[39m] Command[46] Writing command buffer to socket: [2,17,54,51,72,91,96,29,246,109,198,171,233,224,3]
3/15/2022, 7:59:44 AM [�[34mdebug�[39m] Command[46] Data Sent : CLOCK
3/15/2022, 7:59:49 AM [�[33mwarn�[39m] Command[46] 'CLOCK' Timeout
3/15/2022, 7:59:49 AM [�[36mverbose�[39m] Command[46] retrying command
3/15/2022, 7:59:49 AM [�[36mverbose�[39m] Command[46] Sending Command: CLOCK
3/15/2022, 7:59:49 AM [�[34mdebug�[39m] Command[46] Writing command buffer to socket: [2,17,54,51,72,91,96,29,246,109,198,171,233,224,3]
3/15/2022, 7:59:49 AM [�[34mdebug�[39m] Command[46] Data Sent : CLOCK
3/15/2022, 7:59:54 AM [�[33mwarn�[39m] Command[46] 'CLOCK' Timeout
3/15/2022, 7:59:54 AM [�[36mverbose�[39m] Command[46] retrying command
3/15/2022, 7:59:54 AM [�[36mverbose�[39m] Command[46] Sending Command: CLOCK
3/15/2022, 7:59:54 AM [�[34mdebug�[39m] Command[46] Writing command buffer to socket: [2,17,54,51,72,91,96,29,246,109,198,171,233,224,3]
3/15/2022, 7:59:54 AM [�[34mdebug�[39m] Command[46] Data Sent : CLOCK
3/15/2022, 7:59:55 AM [�[31merror�[39m] Panel Socket Error : Error: read EHOSTUNREACH
3/15/2022, 7:59:55 AM [�[34mdebug�[39m] RiscoCloud Socket Destroyed.
3/15/2022, 7:59:55 AM [�[32minfo�[39m] TCP Socket Disconnected
3/15/2022, 7:59:55 AM [�[32minfo�[39m] Automatic reconnection will be attempted in 10000 ms
3/15/2022, 7:59:55 AM [�[36mverbose�[39m] [Panel => MQTT] Published alarm offline
3/15/2022, 7:59:55 AM [�[31merror�[39m] Command[46] error: Error: read EHOSTUNREACH
3/15/2022, 7:59:55 AM [�[31merror�[39m] Panel Socket Closed.
3/15/2022, 7:59:55 AM [�[36mverbose�[39m] [Panel => MQTT] Published alarm offline
3/15/2022, 7:59:55 AM [�[34mdebug�[39m] Command[46] command response : undefined
3/15/2022, 7:59:55 AM [�[33mwarn�[39m] Failed to send CLOCK command: RiscoCommandError: Risco command error: TIMEOUT. Command: {"panelId":1,"commandId":46,"attempts":3,"crcOk":false,"commandStr":"CLOCK","sentBuffer":{"type":"Buffer","data":[2,17,54,51,72,91,96,29,246,109,198,171,233,224,3]}}
3/15/2022, 8:00:05 AM [�[36mverbose�[39m] Start Connection to Panel
3/15/2022, 8:00:05 AM [�[34mdebug�[39m] A TCP Socket already exists, clearing its listeners before creating a new one
3/15/2022, 8:00:05 AM [�[34mdebug�[39m] Pseudo Buffer Created for Panel Id(1)
3/15/2022, 8:00:05 AM [�[34mdebug�[39m] TCP Socket created
3/15/2022, 8:00:05 AM [�[32minfo�[39m] Listening on IP :: and Port 33000
3/15/2022, 8:00:05 AM [�[32minfo�[39m] Waiting for panel incoming connection... This can take up to 1 or 2 minutes
3/15/2022, 8:01:57 AM [�[32minfo�[39m] Incoming connection from panel received
3/15/2022, 8:01:57 AM [�[34mdebug�[39m] RiscoCloud Socket: connect
3/15/2022, 8:01:57 AM [�[32minfo�[39m] RiscoCloud Socket: ready
3/15/2022, 8:01:57 AM [�[32minfo�[39m] Setting a timer for panel connection in 30000 ms
3/15/2022, 8:01:57 AM [�[34mdebug�[39m] [Panel => Cloud] Forwarding panel packet to cloud: [2,19,56,54,4,81,0,16,3,0,51,48,48,53,48,48,50,48,52,49,50,32,32,32,32,32,65,65,65,65,65,65,32,32,32,32,32,32,32,32,32,32,0,0,23,23,69,76,16,2,112,1,255,255,255,255,255,255,49,16,2,49,0,0,0,0,6,255,30,236,60,0,0,16,2,15,49,57,50,46,49,54,56,46,48,48,48,46,48,50,54,1,23,51,68,56,67,3]
3/15/2022, 8:01:57 AM [�[34mdebug�[39m] [Panel => Cloud] Forwarding panel packet to cloud: [2,19,56,54,4,81,0,16,3,0,51,48,48,53,48,48,50,48,52,49,50,32,32,32,32,32,65,65,65,65,65,65,32,32,32,32,32,32,32,32,32,32,0,0,23,23,69,76,16,2,112,1,255,255,255,255,255,255,49,16,2,49,0,0,0,0,6,255,30,236,60,0,0,16,2,15,49,57,50,46,49,54,56,46,48,48,48,46,48,50,54,1,23,51,68,56,67,3]
3/15/2022, 8:01:58 AM [�[34mdebug�[39m] [Cloud => Panel] Forwarding Cloud data Buffer to panel: [2,19,56,54,0,9,0,16,3,0,87,1,8,34,16,3,21,16,3,23,65,51,53,69,3,2,19,48,48,4,16,3,0,10,0,255,23,51,48,49,65,3]
3/15/2022, 8:01:58 AM [�[34mdebug�[39m] [Panel => Cloud] Forwarding panel packet to cloud: [2,19,56,55,4,81,0,16,3,0,51,48,48,53,48,48,50,48,52,49,50,32,32,32,32,32,65,65,65,65,65,65,32,32,32,32,32,32,32,32,32,32,0,0,23,23,69,76,16,2,112,1,255,255,255,255,255,255,49,16,2,49,0,0,0,0,6,255,30,236,60,0,0,16,2,15,49,57,50,46,49,54,56,46,48,48,48,46,48,50,54,1,23,53,50,55,52,3]
3/15/2022, 8:02:03 AM [�[34mdebug�[39m] [Panel => Cloud] Forwarding panel packet to cloud: [2,19,56,55,4,81,0,16,3,0,51,48,48,53,48,48,50,48,52,49,50,32,32,32,32,32,65,65,65,65,65,65,32,32,32,32,32,32,32,32,32,32,0,0,23,23,69,76,16,2,112,1,255,255,255,255,255,255,49,16,2,49,0,0,0,0,6,255,30,236,60,0,0,16,2,15,49,57,50,46,49,54,56,46,48,48,48,46,48,50,54,1,23,53,50,55,52,3]
3/15/2022, 8:02:09 AM [�[34mdebug�[39m] [Panel => Cloud] Forwarding panel packet to cloud: [2,19,56,55,4,81,0,16,3,0,51,48,48,53,48,48,50,48,52,49,50,32,32,32,32,32,65,65,65,65,65,65,32,32,32,32,32,32,32,32,32,32,0,0,23,23,69,76,16,2,112,1,255,255,255,255,255,255,49,16,2,49,0,0,0,0,6,255,30,236,60,0,0,16,2,15,49,57,50,46,49,54,56,46,48,48,48,46,48,50,54,1,23,53,50,55,52,3]
3/15/2022, 8:02:15 AM [�[34mdebug�[39m] [Cloud => Panel] Forwarding Cloud data Buffer to panel: [2,19,48,48,4,16,3,0,10,0,255,23,51,48,49,65,3]
3/15/2022, 8:02:27 AM [�[36mverbose�[39m] Authenticating to the panel
3/15/2022, 8:02:27 AM [�[36mverbose�[39m] Command[1] Sending Command: RMT=1014
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[1] Writing command buffer to socket: [2,48,49,82,77,84,61,49,48,49,52,23,70,57,69,67,3]
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[1] Data Sent : RMT=1014
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] [Panel => Bridge] Received unencrypted data Buffer from Panel : [2,48,49,65,67,75,23,51,57,69,66,3]
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Received data Buffer : [2,48,49,65,67,75,23,51,57,69,66,3]
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[1] crcOK : true, Computed CRC : 39EB, Message CRC: 39EB
3/15/2022, 8:02:27 AM [�[36mverbose�[39m] Command[1] Received data: ACK, crcOk: true
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[1] Command response from Panel
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[1] Emitting expected command response
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[1] command response : ACK
3/15/2022, 8:02:27 AM [�[36mverbose�[39m] Command[2] Sending Command: LCL
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[2] Writing command buffer to socket: [2,48,50,76,67,76,23,65,53,65,70,3]
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[2] Data Sent : LCL
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] [Panel => Bridge] Received unencrypted data Buffer from Panel : [2,48,50,65,67,75,23,51,57,65,70,3]
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Received data Buffer : [2,48,50,65,67,75,23,51,57,65,70,3]
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[2] crcOK : true, Computed CRC : 39AF, Message CRC: 39AF
3/15/2022, 8:02:27 AM [�[36mverbose�[39m] Command[2] Received data: ACK, crcOk: true
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[2] Command response from Panel
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[2] Emitting expected command response
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[2] command response : ACK
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] LCL command result OK
3/15/2022, 8:02:27 AM [�[36mverbose�[39m] Setting up encryption using Panel Id
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,50,91,68,123,10,140,71,217,197,253,140,111,168,38,59,127,119,240,70,251,128,119,153,127,145,152,122,181,3]
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Received data Buffer : [2,17,55,50,91,68,123,10,140,71,217,197,253,140,111,168,38,59,127,119,240,70,251,128,119,153,127,145,152,122,181,3]
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Command[57] crcOK : true, Computed CRC : A992, Message CRC: A992
3/15/2022, 8:02:27 AM [�[36mverbose�[39m] Command[57] Received data: PSTT1=--------R-E-----, crcOk: true
3/15/2022, 8:02:27 AM [�[36mverbose�[39m] Command[2] inCryptTest enabled, emitting response without checks to latest sent command
3/15/2022, 8:02:27 AM [�[31merror�[39m] Panel Socket Closed.
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] RiscoCloud Socket Destroyed.
3/15/2022, 8:02:27 AM [�[32minfo�[39m] TCP Socket Disconnected
3/15/2022, 8:02:27 AM [�[32minfo�[39m] Automatic reconnection will be attempted in 10000 ms
3/15/2022, 8:02:27 AM [�[33mwarn�[39m] sendCommand(ZLBL*1:8?): Socket is destroyed, ignoring command
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] cryptTableTester response: , attempt: 1
3/15/2022, 8:02:27 AM [�[36mverbose�[39m] Connection to the control panel successfully established.
3/15/2022, 8:02:27 AM [�[34mdebug�[39m] Risco Panel Connected.
3/15/2022, 8:02:27 AM [�[33mwarn�[39m] sendCommand(PNLCNF): Socket is destroyed, ignoring command
/app/node_modules/@vanackej/risco-lan-bridge/dist/RiscoComm.js:304
                    throw new Error(`Unsupported panel type : ${panelType}`);
                          ^
Error: Unsupported panel type : 
    at RiscoComm.<anonymous> (/app/node_modules/@vanackej/risco-lan-bridge/dist/RiscoComm.js:304:27)
    at Generator.next (<anonymous>)
    at fulfilled (/app/node_modules/tslib/tslib.js:114:62)

MQTT sensors gone, clock timeouts

Describe the bug
Hi @vanackej , i had the issue below, seems the sensors became unavailble, while the arming state was still present... i havent had the issue before the new releases lately?
I dont have the full debug logs, just normal log, but you see a lot of error/warnigs, allthough its still running

Configuration

Environment: HA Addon
Version: 0.4.1
Mode: Proxy
Command line (if not running as HA Addon):
Risco Panel model: Lighsts
Risco Panel firmware version: 2.72

Logs

2/26/2022, 3:34:51 PM [info] Subscribing to Home assistant commands topics
2/26/2022, 3:34:51 PM [info] Subscribing to riscopanel/alarm/1/set topic
2/26/2022, 3:34:51 PM [info] Subscribing to riscopanel/alarm/zone/1-bypass/set topic
2/26/2022, 3:34:51 PM [info] Subscribing to riscopanel/alarm/zone/2-bypass/set topic
2/26/2022, 3:34:51 PM [info] Subscribing to riscopanel/alarm/zone/3-bypass/set topic
2/26/2022, 3:34:51 PM [info] Subscribing to riscopanel/alarm/zone/4-bypass/set topic
2/26/2022, 3:34:51 PM [info] Subscribing to riscopanel/alarm/zone/5-bypass/set topic
2/26/2022, 3:34:51 PM [info] Subscribing to riscopanel/alarm/zone/6-bypass/set topic
2/26/2022, 3:34:51 PM [info] Subscribing to riscopanel/alarm/zone/7-bypass/set topic
2/26/2022, 3:34:51 PM [info] Subscribing to riscopanel/alarm/zone/8-bypass/set topic
2/26/2022, 3:34:51 PM [info] Subscribing to riscopanel/alarm/zone/9-bypass/set topic
2/26/2022, 3:34:51 PM [info] Subscribing to panel partitions events
2/26/2022, 3:34:51 PM [info] Subscribing to panel zones events
2/26/2022, 3:34:51 PM [info] Initialization completed
2/26/2022, 3:59:56 PM [warn] Command[15] 'CLOCK' Timeout
2/26/2022, 4:12:11 PM [error] RiscoCloud Socket Timeout.
2/26/2022, 4:12:32 PM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/26/2022, 4:12:32 PM [info] [MQTT => Panel] DISARM command sent on partition 1
2/26/2022, 4:12:33 PM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/26/2022, 4:12:33 PM [info] [MQTT => Panel] DISARM command sent on partition 1
2/26/2022, 5:58:12 PM [info] [Panel => MQTT] Published alarm status armed_away on partition 1
2/26/2022, 6:25:29 PM [error] RiscoCloud Socket Timeout.
2/26/2022, 6:57:14 PM [warn] Command[42] 'CLOCK' Timeout
2/26/2022, 10:33:45 PM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/26/2022, 10:33:45 PM [info] [MQTT => Panel] DISARM command sent on partition 1
2/26/2022, 10:33:47 PM [info] [Panel => MQTT] Published alarm status disarmed on partition 1
2/26/2022, 11:22:35 PM [warn] Command[7] 'CLOCK' Timeout
2/26/2022, 11:49:31 PM [warn] Command[20] 'CLOCK' Timeout
2/27/2022, 1:45:12 AM [warn] Command[23] 'CLOCK' Timeout
2/27/2022, 4:03:47 AM [error] RiscoCloud Socket Timeout.
2/27/2022, 5:16:31 AM [warn] Command[8] 'CLOCK' Timeout
2/27/2022, 7:30:00 AM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/27/2022, 7:30:00 AM [info] [MQTT => Panel] DISARM command sent on partition 1
2/27/2022, 7:41:46 AM [error] RiscoCloud Socket Timeout.
2/27/2022, 8:28:32 AM [warn] Command[25] 'CLOCK' Timeout
2/27/2022, 10:19:45 AM [error] RiscoCloud Socket Timeout.
2/27/2022, 10:26:24 AM [warn] Command[41] 'CLOCK' Timeout
2/27/2022, 10:35:45 AM [error] RiscoCloud Socket Timeout.
2/27/2022, 10:45:57 AM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/27/2022, 10:45:57 AM [info] [MQTT => Panel] DISARM command sent on partition 1
2/27/2022, 10:50:00 AM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/27/2022, 10:50:00 AM [info] [MQTT => Panel] DISARM command sent on partition 1
2/27/2022, 10:51:25 AM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/27/2022, 10:51:25 AM [info] [MQTT => Panel] DISARM command sent on partition 1
2/27/2022, 11:46:31 AM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/27/2022, 11:46:31 AM [info] [MQTT => Panel] DISARM command sent on partition 1
2/27/2022, 2:07:09 PM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/27/2022, 2:07:09 PM [info] [MQTT => Panel] DISARM command sent on partition 1
2/27/2022, 2:48:17 PM [warn] Command[33] 'CLOCK' Timeout
2/27/2022, 3:12:20 PM [info] [Panel => MQTT] Published alarm status armed_away on partition 1
2/27/2022, 4:35:11 PM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/27/2022, 4:35:11 PM [info] [MQTT => Panel] DISARM command sent on partition 1
2/27/2022, 4:35:12 PM [info] [Panel => MQTT] Published alarm status disarmed on partition 1
2/27/2022, 4:41:12 PM [error] RiscoCloud Socket Timeout.
2/27/2022, 4:46:21 PM [warn] Command[2] 'CLOCK' Timeout
2/27/2022, 5:11:17 PM [warn] Command[3] 'CLOCK' Timeout
2/27/2022, 5:50:14 PM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/27/2022, 5:50:14 PM [info] [MQTT => Panel] DISARM command sent on partition 1
2/27/2022, 6:15:59 PM [warn] Command[45] 'CLOCK' Timeout
2/27/2022, 6:24:58 PM [warn] Command[49] 'CLOCK' Timeout
2/27/2022, 7:01:13 PM [error] RiscoCloud Socket Timeout.
2/27/2022, 7:53:12 PM [error] RiscoCloud Socket Timeout.
2/27/2022, 8:43:40 PM [warn] Command[42] 'CLOCK' Timeout
2/27/2022, 10:33:01 PM [info] [Panel => MQTT] Published alarm status armed_home on partition 1
2/28/2022, 1:18:04 AM [warn] Command[11] 'CLOCK' Timeout
2/28/2022, 4:02:16 AM [error] RiscoCloud Socket Timeout.
2/28/2022, 4:33:13 AM [warn] Command[47] 'CLOCK' Timeout
2/28/2022, 7:21:12 AM [info] [Panel => MQTT] Published alarm status disarmed on partition 1
2/28/2022, 7:27:13 AM [error] RiscoCloud Socket Timeout.
2/28/2022, 8:44:10 AM [info] [MQTT => Panel] Received change state command DISARM on topic riscopanel/alarm/1/set in partition 1
2/28/2022, 8:44:10 AM [info] [MQTT => Panel] DISARM command sent on partition 1
2/28/2022, 8:46:29 AM [warn] Command[37] 'CLOCK' Timeout

Additional context
Add any other context about the problem here.

Bypassing zone errors

Describe the bug
Thanks for all the excellent work you've done on this project.
Bypass zone bypasses the wrong zone or offers an error that zone can't be bypassed.
Renaming zones doesn't always work as per closed issue #23

Configuration

Environment: Docker
Version: 0.4.0
Mode: direct
Command line: node /app/dist/main.js
Risco Panel model: Lightsys
Risco Panel firmware version: 5.93
risco-commands-2022-02-25T20:27:31.891Z.csv

Logs

2/25/2022, 8:27:07 PM [warn] Command[null] Receipt of an error code: CRC Error
2/25/2022, 8:27:12 PM [warn] Command[46] 'DCN' Timeout
2/25/2022, 8:27:12 PM [warn] Risco command error: TIMEOUT. Command: {"panelId":1,"commandId":46,"attempts":1,"crcOk":false,"commandStr":"DCN","sentBuffer":{"type":"Buffer","data":[2,54,51,79,84,97,73,248,75,193,171,3]}}
2/25/2022, 8:27:12 PM [warn] Error while sending DCN command
2/25/2022, 8:27:12 PM [info] TCP Socket Disconnected
2/25/2022, 8:27:12 PM [info] Won't attempt automatic reconnection
Loading config from: /data/config.json
2/25/2022, 8:27:31 PM [info] Logging commands to risco-commands-2022-02-25T20:27:31.891Z.csv
2/25/2022, 8:27:32 PM [info] autoConnect enabled, starting communication
2/25/2022, 8:27:32 PM [info] Connecting to mqtt server: mqtt://192.168.3.81:1883
2/25/2022, 8:27:33 PM [info] Connected on mqtt server: mqtt://192.168.3.81:1883
2/25/2022, 8:27:33 PM [info] Panel is not connected, waiting
2/25/2022, 8:27:34 PM [info] Panel info: LightSys/RP432, FW 5.93
2/25/2022, 8:27:34 PM [info] Panel options: 4 parts, 50 zones, 32 outputs, Pir Cam support: false
2/25/2022, 8:27:34 PM [info] Starting devices discovery
2/25/2022, 8:27:34 PM [info] Retrieving System Information
2/25/2022, 8:27:34 PM [info] Retrieving zones configuration
2/25/2022, 8:28:13 PM [info] Retrieving outputs configuration
2/25/2022, 8:28:16 PM [warn] Command[42] Receipt of an error code: Device Doesn't Exists
2/25/2022, 8:28:16 PM [warn] Got error while fetching output 7 data: N19
2/25/2022, 8:28:16 PM [info] Output 7 does not exists, stopping outputs discovery
2/25/2022, 8:28:16 PM [info] Retrieving partitions configuration
2/25/2022, 8:28:17 PM [info] Panel and MQTT communications are ready
2/25/2022, 8:28:17 PM [info] Publishing Home Assistant discovery info
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published alarm_control_panel to HA on partition 1
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published alarm_control_panel to HA on partition 2
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Front Door, HA name = Front door
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Hall PIR, HA name = Hall PIR
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Kitchen PIR, HA name = Kitchen PIR
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Lounge PIR, HA name = Lounge PIR
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Grnd Flr Bath, HA name = Downstairs bathroom window
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Study PIR, HA name = Study PIR
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Study Window, HA name = Study window
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Utility Door, HA name = Utility door
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Utility Window, HA name = Utility window
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Kitchen LH Wndow, HA name = Kitchen LH Wndow
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Kitchen RH Wndow, HA name = Kitchen RH Wndow
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Kitchen Patio Dr, HA name = Kitchen patio door
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Lounge Patio Dr, HA name = Lounge patio door
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Landing PIR, HA name = Landing PIR
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = M Bed PIR, HA name = Master bedroom PIR
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = 1st Flr Bath, HA name = Main bathroom window
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Plum Bed Window, HA name = Plum bedroom window
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Landing Window, HA name = Landing Window
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Oak Bed Window, HA name = Oak bedroom window
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Beach Bed Window, HA name = Beach bedroom window
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = M Bed French, HA name = Master bedroom patio door
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Dining PIR, HA name = Dining room PIR
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Dining Windows, HA name = Dining room windows
2/25/2022, 8:28:17 PM [info] [Panel => MQTT][Discovery] Published binary_sensor to HA: Zone label = Garage Door, HA name = Garage door
2/25/2022, 8:28:17 PM [info] Publishing initial partitions and zones state to Home assistant
2/25/2022, 8:28:17 PM [info] [Panel => MQTT] Published alarm status disarmed on partition 1
2/25/2022, 8:28:17 PM [info] [Panel => MQTT] Published alarm status armed_away on partition 2
2/25/2022, 8:28:17 PM [info] Subscribing to Home assistant commands topics
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/1/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/2/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/1-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/2-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/3-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/4-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/5-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/6-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/7-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/9-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/10-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/11-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/12-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/13-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/14-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/17-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/18-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/19-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/20-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/21-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/22-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/23-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/24-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/25-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/26-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to riscopanel/alarm/zone/27-bypass/set topic
2/25/2022, 8:28:17 PM [info] Subscribing to panel partitions events
2/25/2022, 8:28:17 PM [info] Subscribing to panel zones events
2/25/2022, 8:28:17 PM [info] Initialization completed
2/25/2022, 8:31:56 PM [info] [MQTT => Panel] Received bypass zone command true on topic riscopanel/alarm/zone/4-bypass/set for zone 4
2/25/2022, 8:31:57 PM [info] [MQTT => Panel] toggle bypass command sent on zone 4
2/25/2022, 8:32:23 PM [info] [MQTT => Panel] Received bypass zone command true on topic riscopanel/alarm/zone/17-bypass/set for zone 7
2/25/2022, 8:32:23 PM [info] [MQTT => Panel] toggle bypass command sent on zone 7
2/25/2022, 8:32:55 PM [info] [MQTT => Panel] Received bypass zone command true on topic riscopanel/alarm/zone/17-bypass/set for zone 7
2/25/2022, 8:32:55 PM [info] [MQTT => Panel] Zone is already on the desired bypass state
2/25/2022, 8:34:04 PM [info] [MQTT => Panel] Received bypass zone command false on topic riscopanel/alarm/zone/7-bypass/set for zone 7
2/25/2022, 8:34:05 PM [info] [MQTT => Panel] toggle bypass command sent on zone 7
2/25/2022, 8:34:17 PM [info] [MQTT => Panel] Received bypass zone command true on topic riscopanel/alarm/zone/21-bypass/set for zone 1
2/25/2022, 8:34:17 PM [warn] Command[26] Receipt of an error code: Invalid Value
2/25/2022, 8:34:17 PM [error] [MQTT => Panel] Failed to send toggle bypass command on zone 1
2/25/2022, 8:34:36 PM [info] [MQTT => Panel] Received bypass zone command true on topic riscopanel/alarm/zone/19-bypass/set for zone 9
2/25/2022, 8:34:36 PM [warn] Command[31] Receipt of an error code: Invalid Value
2/25/2022, 8:34:36 PM [error] [MQTT => Panel] Failed to send toggle bypass command on zone 9
2/25/2022, 8:35:10 PM [info] [MQTT => Panel] Received bypass zone command true on topic riscopanel/alarm/zone/17-bypass/set for zone 7
2/25/2022, 8:35:11 PM [info] [MQTT => Panel] toggle bypass command sent on zone 7
2/25/2022, 8:36:07 PM [info] [MQTT => Panel] Received bypass zone command true on topic riscopanel/alarm/zone/21-bypass/set for zone 1
2/25/2022, 8:36:07 PM [warn] Command[1] Receipt of an error code: Invalid Value
2/25/2022, 8:36:07 PM [error] [MQTT => Panel] Failed to send toggle bypass command on zone 1
2/25/2022, 8:36:25 PM [info] [MQTT => Panel] Received bypass zone command true on topic riscopanel/alarm/zone/21-bypass/set for zone 1
2/25/2022, 8:36:26 PM [warn] Command[6] Receipt of an error code: Invalid Value
2/25/2022, 8:36:26 PM [error] [MQTT => Panel] Failed to send toggle bypass command on zone 1
2/25/2022, 8:36:47 PM [info] [MQTT => Panel] Received bypass zone command true on topic riscopanel/alarm/zone/14-bypass/set for zone 4
2/25/2022, 8:36:47 PM [info] [MQTT => Panel] Zone is already on the desired bypass state

Additional context
Add any other context about the problem here.

Prefix Partition name to zone name

Currently the integration creates the zone names using binary_sensor.<zone_name>.

To align with the cloud integration, and to easily mimic the Risco app to group zone switches in UI (see example below). The suggestion is to prefix the partition name to the zone.
For Example:
The partition name (label) is Living Area,
The zone name (label) is Entrance Hall.

So the binary sensor will be binary_sensor.living_area_entrance_hall and the bypass switch will be switch.living_area_entrance_hall

                  - type: custom:fold-entity-row
                    head:
                      type: section
                      label: Living Area
                    group_config:
                      secondary_info: last-changed
                    entities:
                      - type: custom:auto-entities
                        filter:
                          include:
                            - entity_id: "switch.living_area_*bypass"
                        card:
                          type: entities

Bypass Zone - Attribute to show bypassed state

Thank you for this - it is awesome to have control of the alarm without being dependent on cloud infrastructure.

I was using the Risco integration prior, and on the binary sensors they had an attribute which showed the status of the sensor's bypassed state.

bypassed: false

bypassed: true

If this is possible it will be awesome - I have automations which are dependent on knowing this state and will be awesome to be able to it again.

Thank you!

Zone config override issue

Hi,
As I try to override config (e.g. "device class":"door" or "name": "xxxx") for a given zone, it changes it for several other random zones. I think it depends from zone label as I tried configuring several different zones (one at a time) and it does that only for some...for example if i configure it like this:

"zones": {
  "default": {
    "off_delay": 0,
    "name_prefix": "Sensor "
  },
  "Porta Ingresso": {
    "device_class": "door"
  }

it changes class to door for a bunch of other random zones

while if i configre it like this:

"zones": {
  "default": {
    "off_delay": 0,
    "name_prefix": "Sensor "
  },
  "Tamper SIR": {
    "device_class": "tamper"
  }

the configuration is fine and it doesnt change class to other zones.
It does the same thing with "name"

let me know if u need logs for this

Configuration

Environment: Addon
Version: 0.3.8
Mode: direct
Command line (if not running as HA Addon):
Risco Panel model: ProSYS Plus
Risco Panel firmware version: 01.04.04.0010

ProSYS Plus issue

Describe the bug
Hi,

Configuration

Environment: Docker
Version: 0.3.5 (latest docker image at 20/02/2022)
Mode: direct
Command line (if not running as HA Addon):
Risco Panel model: ProSYS Plus
Risco Panel firmware version: 01.04.04.0010

Logs

deleted

Connection reset RW432MP panel

Describe the bug
The HomeAssistant addon is unable to connect to my RW432MP panel (connection is being reset)

Configuration

Environment: HA Addon
Version: v0.5.0-beta.2
Mode: direct
Risco Panel model: RW432MP (I think that's Lightsys+)
Risco Panel firmware version: Unknown

Logs

Debug logs:

Loading config from: /config/risco-mqtt.json
1/25/2024, 12:42:17 PM [debug] User config:
{
  "log": "debug",
  "panel": {
    "panelIp": “RISCO_IP”,
    "panelPort": 1000,
    "panelPassword": “RISCO_PIN,
    "watchDogInterval": 10000,
    "commandsLog": true
  },
  "panel_name": "alarm",
  "mqtt": {
    "url": "mqtt://HA_IP:1883",
    "username": "MQTT_USER",
    "password": "MQTT_PASS"
  },
  "zones": {}
}
1/25/2024, 12:42:18 PM [debug] Merged config:
{
  "log": "debug",
  "logColorize": false,
  "ha_discovery_prefix_topic": "homeassistant",
  "panel_name": "alarm",
  "panel_node_id": "alarm",
  "panel": {
    "panelIp": "RISCO_IP",
    "panelPort": 1000,
    "panelPassword": "RISCO_PW",
    "watchDogInterval": 10000,
    "commandsLog": true
  },
  "zones": {
    "default": {
      "off_delay": 0,
      "device_class": "motion",
      "name_prefix": ""
    }
  },
  "mqtt": {
    "url": "mqtt://HA_IP:1883",
    "username": "MQTT_USER",
    "password": "MQTT_PASS",
    "reconnectPeriod": 5000,
    "clientId": null,
    "will": {
      "topic": null,
      "payload": "offline",
      "qos": 1,
      "retain": true,
      "properties": {
        "willDelayInterval": 30
      }
    }
  }
}
1/25/2024, 12:42:18 PM [info] Logging commands to risco-commands-2024-01-25T11:42:18.033Z.csv
1/25/2024, 12:42:18 PM [debug] Local GMT Timezone is : +01:00
1/25/2024, 12:42:18 PM [info] autoConnect enabled, starting communication
1/25/2024, 12:42:18 PM [verbose] Start Connection to Panel
1/25/2024, 12:42:18 PM [debug] Pseudo Buffer Created for Panel Id(1)
1/25/2024, 12:42:18 PM [debug] TCP Socket created
1/25/2024, 12:42:18 PM [info] Connecting to mqtt server: mqtt://HA_IP:1883
1/25/2024, 12:42:18 PM [error] Socket Error : Error: connect ECONNRESET RISCO_IP:1000
1/25/2024, 12:42:18 PM [info] TCP Socket Disconnected
1/25/2024, 12:42:18 PM [info] Automatic reconnection will be attempted in 10000 ms
1/25/2024, 12:42:18 PM [debug] Socket Disconnected.
1/25/2024, 12:42:18 PM [error] Socket Closed.
1/25/2024, 12:42:18 PM [info] Connected on mqtt server: mqtt://HA_IP:1883
1/25/2024, 12:42:18 PM [info] Panel is not connected, waiting
1/25/2024, 12:42:28 PM [verbose] Start Connection to Panel
1/25/2024, 12:42:28 PM [debug] A TCP Socket already exists, clearing its listeners before creating a new one
1/25/2024, 12:42:28 PM [debug] Pseudo Buffer Created for Panel Id(1)
1/25/2024, 12:42:28 PM [debug] TCP Socket created
1/25/2024, 12:42:28 PM [verbose] Socket Connected, log in to panel
1/25/2024, 12:42:28 PM [verbose] Authenticating to the panel
1/25/2024, 12:42:28 PM [verbose] Command[1] Sending Command: RMT=RISCO_PW
1/25/2024, 12:42:28 PM [debug] Command[1] Writing command buffer to socket: [INT_ARRAY]
1/25/2024, 12:42:28 PM [debug] Command[1] Data Sent : RMT=RISCO_PW
1/25/2024, 12:42:28 PM [error] Socket Error : Error: write ECONNRESET
1/25/2024, 12:42:28 PM [info] TCP Socket Disconnected
1/25/2024, 12:42:28 PM [info] Automatic reconnection will be attempted in 10000 ms
1/25/2024, 12:42:28 PM [debug] Socket Disconnected.
1/25/2024, 12:42:28 PM [error] Command[1] error: Error: write ECONNRESET
1/25/2024, 12:42:28 PM [error] Socket Closed.
1/25/2024, 12:42:28 PM [debug] Command[1] command response : undefined
1/25/2024, 12:42:28 PM [error] Risco command error: TIMEOUT. Command: {"panelId":1,"commandId":1,"attempts":1,"crcOk":false,"commandStr":"RMT=RISCO_PW","sentBuffer":{"type":"Buffer","data":[INT_ARRAY]}}

where INT_ARRAY is an arbitrary-looking array of integers (removed because unsure if it's sensitive data).

Command log:

Unable to find the command log file.

Additional context
No additional context

proxy mode not working

Hi.
I don't see anything in mqtt. I have LightSys 2 and try to configure it in proxy mode.

My config:

{
  "log": "debug",
  "panel": {
    "Panel_Id": "0001",
    "Panel_IP": "192.168.10.33",
    "Panel_Port": 1000,
    "Panel_Password": "5678",
    "AutoDiscover": false,
    "DiscoverCode": false,
    "WatchDogInterval": 10000,
    "SocketMode": "proxy",
    "CloudPort": 33000,
    "CloudUrl": "www.riscocloud.com",
    "Enable_RiscoCloud":  true,
    "ListeningPort": 33000
  },
  "mqtt": {
    "url": "mqtt://192.168.10.100:1883",
    "username": "guest",
    "password": "guest"
  },
  "zones": {
    "default": {
      "off_delay": 30,
      "name_prefix": "Sensor - "
    }
  }
}

Logs attached.
proxy.log

I see a lot of timeouts like: 'CUSTLST??' Timeout!!!

error on launch: TCP Socket Disconnected

Hello @vanackej ,

First of all, thanks for your work.

So, to begin, i've found the installer password through Risco Configuration Sofware and i disabled the cloud part.

Then i try your code, but i encountered the error bellow:

Loading config from: /usr/src/app/config.json 2/8/2022, 10:47:44 AM [debug] User config: { "log": "debug", "panel": { "panelIp": "192.168.100.182", "panelPort": 1000, "panelPassword": "5678", "panelId": "0001", "watchDogInterval": 10000 }, "mqtt": { "url": "mqtt://192.168.100.235:1883" }, "zones": { "default": { "off_delay": 30, "name_prefix": "Sensor - " } } } 2/8/2022, 10:47:44 AM [debug] Merged config: { "log": "debug", "logColorize": false, "ha_discovery_prefix_topic": "homeassistant", "ha_discovery_include_nodeId": false, "panel": { "panelIp": "192.168.100.182", "panelPort": 1000, "panelPassword": "5678", "panelId": "0001", "watchDogInterval": 10000 }, "zones": { "default": { "off_delay": 30, "device_class": "motion", "name_prefix": "Sensor - " } }, "mqtt": { "url": "mqtt://192.168.100.235:1883", "reconnectPeriod": 5000, "clientId": "risco-mqtt-37a0fd", "will": { "topic": "riscopanel/alarm/status", "payload": "offline", "qos": 1, "retain": true, "properties": { "willDelayInterval": 30 } } } } 2/8/2022, 10:47:44 AM [debug] Pseudo Buffer Created for Panel Id(0001): [2,5,11,23,47,94,189,122,244,232,208,161,66,133,11,22,45,90,181,107,214,173,90,180,104,208,161,67,135,15,31,63,126,253,251,247,239,223,191,127,255,255,254,252,249,242,229,202,149,43,86,172,8 8,176,96,193,131,6,12,25,50,100,200,144,32,65,130,5,11,23,47,95,190,125,250,245,234,213,170,85,170,84,168,81,162,68,136,17,35,70,140,24,49,98,197,138,21,42,85,171,87,175,94,188,121,243,230,2 04,152,49,98,197,138,21,43,86,172,88,177,99,198,141,27,54,109,218,180,105,210,165,74,149,42,85,171,86,173,90,181,106,212,168,80,160,64,129,2,4,9,19,39,78,157,58,117,234,213,170,85,170,85,171 ,87,175,95,190,124,248,240,225,195,135,15,30,60,120,240,224,193,131,6,12,25,51,102,205,154,53,107,215,175,94,189,122,245,235,215,175,95,190,125,251,246,236,216,176,96,192,129,2,4,8,17,34,68, 137,19,39,78,156,56,113,227,199,143,30,61,122,245,234,213,171,86,172,89,179,102,205,154,53,107,215,174,92,185,115,231,207,158,61,123,247,239,223,191] 2/8/2022, 10:47:44 AM [debug] Local GMT Timezone is : +00:00 2/8/2022, 10:47:44 AM [info] autoConnect enabled, starting communication 2/8/2022, 10:47:44 AM [verbose] Start Connection to Panel 2/8/2022, 10:47:44 AM [debug] TCP Socket is not already created, Create It 2/8/2022, 10:47:44 AM [debug] TCP Socket must be created now 2/8/2022, 10:47:44 AM [info] Connecting to mqtt server: mqtt://192.168.100.235:1883 2/8/2022, 10:47:44 AM [info] Connected on mqtt server: mqtt://192.168.100.235:1883 2/8/2022, 10:47:44 AM [info] Panel is not connected, waiting 2/8/2022, 10:47:44 AM [verbose] Socket Connected, log in to panel 2/8/2022, 10:47:44 AM [verbose] Authenticating to the panel 2/8/2022, 10:47:44 AM [verbose] Command[1] Sending Command: RMT=5678 2/8/2022, 10:47:44 AM [debug] Command[1] Writing command buffer to socket: [2,48,49,82,77,84,61,53,54,55,56,23,66,48,70,56,3] 2/8/2022, 10:47:44 AM [debug] Command[1] Data Sent : RMT=5678 2/8/2022, 10:47:49 AM [warn] Command[1] 'RMT=5678' Timeout 2/8/2022, 10:47:49 AM [debug] Command[1] retrying with a new command Id 2/8/2022, 10:47:49 AM [verbose] Command[1] Sending Command: RMT=5678 2/8/2022, 10:47:49 AM [debug] Command[1] Writing command buffer to socket: [2,48,49,82,77,84,61,53,54,55,56,23,66,48,70,56,3] 2/8/2022, 10:47:49 AM [debug] Command[1] Data Sent : RMT=5678 2/8/2022, 10:47:49 AM [debug] Received data Buffer : [2,48,49,65,67,75,23,51,57,69,66,3] 2/8/2022, 10:47:49 AM [debug] Command[1] CRC Value : 39EB 2/8/2022, 10:47:49 AM [debug] Command[1] CRC Ok 2/8/2022, 10:47:49 AM [debug] Command[1] Command response from Panel 2/8/2022, 10:47:49 AM [debug] Command[1] Emitting expected command response 2/8/2022, 10:47:49 AM [verbose] Command[1] Received data from panel: ACK 2/8/2022, 10:47:49 AM [debug] Command[1] SendCommand receive this response : ACK 2/8/2022, 10:47:49 AM [verbose] Command[2] Sending Command: LCL 2/8/2022, 10:47:49 AM [debug] Command[2] Writing command buffer to socket: [2,48,50,76,67,76,23,65,53,65,70,3] 2/8/2022, 10:47:49 AM [debug] Command[2] Data Sent : LCL 2/8/2022, 10:47:49 AM [debug] Received data Buffer : [2,48,50,65,67,75,23,51,57,65,70,3] 2/8/2022, 10:47:49 AM [debug] Command[2] CRC Value : 39AF 2/8/2022, 10:47:49 AM [debug] Command[2] CRC Ok 2/8/2022, 10:47:49 AM [debug] Command[2] Command response from Panel 2/8/2022, 10:47:49 AM [debug] Command[2] Emitting expected command response 2/8/2022, 10:47:49 AM [verbose] Command[2] Received data from panel: ACK 2/8/2022, 10:47:49 AM [debug] Command[2] SendCommand receive this response : ACK 2/8/2022, 10:47:49 AM [debug] LCL command result OK 2/8/2022, 10:47:49 AM [verbose] Setting up encryption using Panel Id 2/8/2022, 10:47:49 AM [verbose] Command[3] Sending Command: CUSTLST? 2/8/2022, 10:47:49 AM [debug] Command[3] Writing command buffer to socket: [2,17,50,54,72,66,124,10,241,41,160,215,199,148,115,188,60,3] 2/8/2022, 10:47:49 AM [debug] Command[3] Data Sent : CUSTLST? 2/8/2022, 10:47:49 AM [debug] Received data Buffer : [2,17,50,54,69,39,26,73,132,76,192,217,3] 2/8/2022, 10:47:49 AM [debug] Command[3] CRC Value : 9641 2/8/2022, 10:47:49 AM [debug] Command[3] CRC Ok 2/8/2022, 10:47:49 AM [verbose] Command[3] inCryptTest enabled, emitting response without checks 2/8/2022, 10:47:49 AM [debug] Command[3] SendCommand receive this response : N05 2/8/2022, 10:47:49 AM [debug] cryptTableTester response: N05 2/8/2022, 10:47:49 AM [verbose] Command[4] Sending Command: CUSTLST? 2/8/2022, 10:47:49 AM [debug] Command[4] Writing command buffer to socket: [2,17,50,49,72,66,124,10,241,41,160,215,199,153,0,183,61,3] 2/8/2022, 10:47:49 AM [debug] Command[4] Data Sent : CUSTLST? 2/8/2022, 10:47:50 AM [debug] Received data Buffer : [2,17,50,49,69,39,26,73,136,76,178,220,3] 2/8/2022, 10:47:50 AM [debug] Command[4] CRC Value : 56F4 2/8/2022, 10:47:50 AM [debug] Command[4] CRC Ok 2/8/2022, 10:47:50 AM [verbose] Command[4] inCryptTest enabled, emitting response without checks 2/8/2022, 10:47:50 AM [debug] Command[4] SendCommand receive this response : N05 2/8/2022, 10:47:50 AM [debug] cryptTableTester response: N05 2/8/2022, 10:47:50 AM [verbose] Command[5] Sending Command: CUSTLST? 2/8/2022, 10:47:50 AM [debug] Command[5] Writing command buffer to socket: [2,17,50,48,72,66,124,10,241,41,160,215,199,149,7,178,60,3] 2/8/2022, 10:47:50 AM [debug] Command[5] Data Sent : CUSTLST? 2/8/2022, 10:47:50 AM [debug] Received data Buffer : [2,17,50,48,69,39,26,73,132,76,183,209,3] 2/8/2022, 10:47:50 AM [debug] Command[5] CRC Value : 96C9 2/8/2022, 10:47:50 AM [debug] Command[5] CRC Ok 2/8/2022, 10:47:50 AM [verbose] Command[5] inCryptTest enabled, emitting response without checks 2/8/2022, 10:47:50 AM [debug] Command[5] SendCommand receive this response : N05 2/8/2022, 10:47:50 AM [debug] cryptTableTester response: N05 2/8/2022, 10:47:50 AM [error] Unable to connect to the control panel. 2/8/2022, 10:47:50 AM [verbose] Command[6] Sending Command: DCN 2/8/2022, 10:47:50 AM [debug] Command[6] Writing command buffer to socket: [2,17,50,51,79,84,97,73,139,79,193,172,3] 2/8/2022, 10:47:50 AM [debug] Command[6] Data Sent : DCN 2/8/2022, 10:47:50 AM [debug] Received data Buffer : [2,17,50,51,74,84,100,73,251,67,193,173,3] 2/8/2022, 10:47:50 AM [debug] Command[6] CRC Value : F95E 2/8/2022, 10:47:50 AM [debug] Command[6] CRC Ok 2/8/2022, 10:47:50 AM [debug] Command[6] Command response from Panel 2/8/2022, 10:47:50 AM [debug] Command[6] Emitting expected command response 2/8/2022, 10:47:50 AM [verbose] Command[6] Received data from panel: ACK 2/8/2022, 10:47:50 AM [debug] Command[6] SendCommand receive this response : ACK 2/8/2022, 10:47:50 AM [debug] Socket Destroyed. 2/8/2022, 10:47:50 AM [info] TCP Socket Disconnected 2/8/2022, 10:47:50 AM [debug] Socket Disconnected.
i dont understand why its not working, maybe my firmware is too old? (05 2018), or i missed something? Does i have to configure the ip of the machine wich contains your app instead of the risco cloud url?

Any clue?

Thanks for your return.

Can't discover panel password

Describe the bug
I am unaware of the password set by my previous installer, I am trying to make it bruteforce it but with no luck. Tried all 4, 5 and 6 cyphers codes without success.

Configuration

Environment: HA Addon
Version: [v0.4.2]
Mode: direct
Risco Panel model: LightSYS2
Risco Panel firmware version: unknown, can't access

Logs

Copy/paste the application logs here (or add them as attachement) :

Loading config from: /config/risco-mqtt.json
9/12/2022, 7:34:07 PM [info] autoConnect enabled, starting communication
9/12/2022, 7:34:07 PM [info] Connecting to mqtt server: mqtt://192.168.178.77:1883
9/12/2022, 7:34:07 PM [warn] Command[1] Receipt of an error code: Invalid Value
9/12/2022, 7:34:07 PM [warn] Provided password is incorrect
9/12/2022, 7:34:07 PM [info] Trying to guess password (brut force)
9/12/2022, 7:34:07 PM [info] Trying passwords from 0000 to 9999...
9/12/2022, 7:34:07 PM [info] 0000 to 0099...
9/12/2022, 7:34:07 PM [info] Connected on mqtt server: mqtt://192.168.178.77:1883
9/12/2022, 7:34:07 PM [info] Panel is not connected, waiting
9/12/2022, 7:34:07 PM [warn] Command[1] Command response was unexpected, ignoring. Data[N06]
9/12/2022, 7:34:14 PM [info] 0100 to 0199...
9/12/2022, 7:34:20 PM [info] 0200 to 0299...
9/12/2022, 7:34:27 PM [info] 0300 to 0399...
9/12/2022, 7:34:33 PM [info] 0400 to 0499...

Output status doesn't update

I'm working on adding Outputs to the code. I can get all config data to pull through, but Output.Status doesn't seem to update. The only way I can get the status to pull through is to set an initial null state and publish the state via OStatusChanged.

Configuration

Environment: Docker
Version: ghcr.io/markxroberts/risco-mqtt-local:v0.5.0-beta4.6
Mode: direct
Command line (if not running as HA Addon):
Risco Panel model: LightSys
Risco Panel firmware version: 5.93

Additional context
Status consistently shows as undefined when I publish the raw state. I've tried stipulating '--', '-', 'a', 'Deactivated', 'Activated', 'Pulsed'.
Do you have any thoughts about this? What am I missing?

Connect two or more panels

Hello,
is posible connect two o more panels?

Thanks.

Errors on running

Running this as a package under official node.js docker build
2 errors on running the package with command:

npx @vanackej/risco-mqtt-local

/home/node/app/node_modules/.bin/risco-mqtt-local: 1: use strict: not found
/home/node/app/node_modules/.bin/risco-mqtt-local: 2: Syntax error: word unexpected (expecting ")")

Can you help?

Question: Available as custom repository for add-on

Hey

Good work, just a question, are you going to add it to HACS too? Or as a custom repository in HACS?
Would be more easy for us to keep up to date with new updates/fixed and makes it easier to install

thnx for the effor

vanackej / risco-mqtt-local Goto Github PK

risco-mqtt-local's People

Contributors

Stargazers

Watchers

Forkers

risco-mqtt-local's Issues

Recommend Projects

Recommend Topics

Recommend Org