Closed ob1w4nken0b1 closed 2 years ago
Can you try with 0.3.6 please ? If you still encounter issues, please always attach debug logs
Hi,
With version 0.3.6 the program keeps destroying the socket and reconnecting back and forth until i manually stop it. It never gets to publish anything on mqtt. The behavior doesnt seem to be changed much from the previous version, but it doesnt throw the final error...here's the log
LOG:
delete
There is a new parameter in the latest release (v0.3.7) that produce a full commands log file, that would be helpful to analyze your issue.
Please update the panel config part adding commandsLog like this :
"panel": {
"panelIp": "XXXX",
"panelPassword": "YYYY",
"panelId": 1,
"watchDogInterval": 10000,
"commandsLog": true
},
Run your tests again and attach the risco-commands-xxx.csv file to the issue
Hi,
Here you have both debug logs and commands.csv of the same session. I manually stopped it after the first socket destruction as it just loops like that
delete
Also with the log in info mode, the loop looks like this:
deleted
I found the source of the bug in the frame decryption part. Looking for a fix I let you know
v0.3.8 available => Let me know
just want to say, nice progress here!!
Oh boy this puppy now works like a charm!!! The issue is gone...thanks for the awesome project man it really is a game changer for risco users.
Before closing the issue I'll attach here the logs as there is a single warn during device discovery saying that a device doesn't exist...it's probably nothing because all sensors and devices are there and work properly...
debug log:
deleted
p.s. closing the issue can i delete logs attached in previous messages? don't know if i censored them properly
I don't know. I think you can edit your previous messages and delete logs from them ?
we dont look :-)
thanks again...i'll close the issue
Describe the bug 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. The logs are from Docker image but running as addon gives the same result Any ideas?
Configuration
Logs
deleted