Closed kkmaslowski closed 2 years ago
I need logs in debug mode to be able to analyze the issue. Only for correct code situation. Thx
Can you try again with 0.3.6 please ?
0.3.6:
Loading config from: /data/config.json
2/21/2022, 10:54:04 AM [info] autoConnect enabled, starting communication
2/21/2022, 10:54:04 AM [info] Connecting to mqtt server: mqtt://192.168.10.100:1883
2/21/2022, 10:54:04 AM [info] Connected on mqtt server: mqtt://192.168.10.100:1883
2/21/2022, 10:54:04 AM [info] Panel is not connected, waiting
2/21/2022, 10:54:10 AM [warn] Command[1] 'RMT=5678' Timeout
2/21/2022, 10:54:11 AM [warn] Bad Panel Id: 1. Trying to find the right one
2/21/2022, 10:54:14 AM [error] No remaining possible Panel Id, abandon
2/21/2022, 10:54:14 AM [error] Unable to connect to the control panel.
2/21/2022, 10:54:14 AM [warn] Command[NaN] Wrong CRC value for the response.
2/21/2022, 10:54:16 AM [warn] Command[NaN] Wrong CRC value for the response.
2/21/2022, 10:54:19 AM [warn] Command[NaN] Wrong CRC value for the response.
2/21/2022, 10:54:19 AM [warn] Command[4] 'DCN' Timeout
2/21/2022, 10:54:19 AM [info] TCP Socket Disconnected
2/21/2022, 10:54:19 AM [info] Won't attempt automatic reconnection
Debug log attached.
Well, that's very strange. The CRC returned by yout panel is only 3 chars long, whereas every other CRC I've seen and computed CRCs are always 4 chars long... I really don't understand why. Can you send the full debug logs for wrong password case ? I wan't to compare received buffers and CRCs in this situation
I see your firmware version is very outdated. Yours : FSVER=2.59 24/09/13 Mine : FSVER=5.72 23/01/18
I think the protocol is bugged in your version and produces wrong CRC in some situations. Can you update the firmware ?
I'll try to do it today. Do you know 'remote upgrade password'? I'm trying to run update from CS.
No sorry I never performed a firmware update by myself
Le lun. 21 févr. 2022 à 14:51, Kamil Maslowski @.***> a écrit :
I'll try to do it today. Do you know 'remote upgrade password'? I'm trying to run update from CS.
— Reply to this email directly, view it on GitHub https://github.com/vanackej/risco-mqtt-local/issues/20#issuecomment-1046902377, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAECPHJUKQ7DVE4VQ4P24TTU4I7ONANCNFSM5O4I75FA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were assigned.Message ID: @.***>
I found a bug in the decryption method. You don't need a firmware update. Fix coming soon, I'll let you know
v0.3.8 available => Let me know
I checked with an unit test and your CRC problem should be gone now. I close the issue, feel free to reopen or comment if not ok.
Great news, it works! Thank you for your hard work.
Loading config from: /data/config.json
2/23/2022, 7:44:22 AM [info] autoConnect enabled, starting communication
2/23/2022, 7:44:22 AM [info] Connecting to mqtt server: mqtt://192.168.10.100:1883
2/23/2022, 7:44:22 AM [info] Connected on mqtt server: mqtt://192.168.10.100:1883
2/23/2022, 7:44:22 AM [info] Panel is not connected, waiting
2/23/2022, 7:44:30 AM [warn] Command[1] 'RMT=5678' Timeout
2/23/2022, 7:44:30 AM [info] Panel info: LightSys/RP432, FW 2.70
2/23/2022, 7:44:30 AM [info] Panel options: 4 parts, 32 zones, 14 outputs, Pir Cam support: false
2/23/2022, 7:44:30 AM [info] Starting devices discovery
2/23/2022, 7:44:34 AM [warn] Command[21] Receipt of an error code: Device Doesn't Exists
2/23/2022, 7:44:34 AM [info] Output does not exists, stopping outputs discovery
2/23/2022, 7:44:34 AM [info] Panel is ready, subscribing to panel partitions and zones events
2/23/2022, 7:44:34 AM [info] Panel and MQTT communications are ready
2/23/2022, 7:44:34 AM [info] Publishing Home Assistant discovery info
2/23/2022, 7:44:34 AM [info] [Panel => MQTT][Discovery] Published alarm_control_panel to HA on partition 1
...
Describe the bug Connection to panel works only when bad password provided
Configuration
Logs Correct password:
Wrong password: