homebridge-envisalink
homebridge-envisalink copied to clipboard
Is there a setting to try and reconnect if connection is lost?
Hello,
I've been getting the following error, then I reboot the bridge and everything works fine again for a few hours:
1/20/2022, 8:13:55 AMEnvisalink BridgeEnvisalinksendcommand 0311C5 1/20/2022, 8:13:58 AMEnvisalink BridgeERROR[Envisalink Bridge E38B@Security System Target State] The write handler for the characteristic 'Security System Target State' on the accessory 'Alarm' was slow to respond! 1/20/2022, 8:14:04 AMEnvisalink BridgeERROR[Envisalink Bridge E38B@Security System Target State] The write handler for the characteristic 'Security System Target State' on the accessory 'Alarm' didn't respond at all!. Please check that you properly call the callback! 1/20/2022, 8:14:51 AMEnvisalink BridgeEnvisalinkFailed to connect to Envisalink Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:220:20) { errno: -104, code: 'ECONNRESET', syscall: 'read' }
My settings:
{ "platform": "Envisalink", "deviceType": "DSC", "host": "192.168.X.X", "suppressZoneAccessories": false, "pin": "XXXX", "port": 4025, "password": "XXXXXXXXXX", "suppressClockReset": false, "proxyPort": 4026, "enableVerboseLogging": true, "ambulancePanic": { "name": "Ambulance Panic", "enabled": false }, "policePanic": { "name": "Police Panic", "enabled": false }, "firePanic": { "name": "Fire Panic", "enabled": false }, "partitions": [ { "enableChimeSwitch": false, "name": "Alarm", "pin": "XXXX" } ], "zones": [ { "zoneNumber": 1, "name": "Puerta Principal", "partition": 1, "type": "door" }, { "zoneNumber": 19, "name": "Corrediza Recamara Principal", "partition": 1, "type": "door" }, { "zoneNumber": 23, "name": "Movimiento Recamara Principal", "partition": 1, "type": "motion" }, { "zoneNumber": 25, "name": "Pasillo Planta Alta", "partition": 1, "type": "motion" }, { "zoneNumber": 20, "name": "Corrediza Recamara Sofia", "partition": 1, "type": "door" }, { "zoneNumber": 24, "name": "Movimiento Recamara Sofia", "partition": 1, "type": "motion" }, { "zoneNumber": 13, "name": "Movimiento Comedor", "partition": 1, "type": "motion" }, { "zoneNumber": 14, "name": "Movimiento Cocina", "partition": 1, "type": "motion" }, { "zoneNumber": 4, "name": "Corrediza Cocina Y Cine", "partition": 1, "type": "door" }, { "zoneNumber": 11, "name": "Movimiento Vestibulo", "partition": 1, "type": "motion" }, { "zoneNumber": 5, "name": "Puerta Cochera Vestibulo", "partition": 1, "type": "door" }, { "zoneNumber": 12, "type": "motion", "partition": 1, "name": "Movimiento Recamara De Visitas" }, { "zoneNumber": 15, "name": "Movimiento Cine", "partition": 1, "type": "motion" }, { "zoneNumber": 22, "name": "Corrediza Recamara David", "partition": 1, "type": "door" }, { "zoneNumber": 26, "name": "Movimiento Recamara David", "partition": 1, "type": "motion" }, { "zoneNumber": 27, "name": "Movimiento Escalera Principal Pasillo PA ", "partition": 1, "type": "motion" }, { "zoneNumber": 2, "name": "Corrediza Sala", "partition": 1, "type": "door" }, { "zoneNumber": 3, "name": "Corrediza Comedor", "partition": 1, "type": "door" }, { "zoneNumber": 7, "name": "Puerta Lavanderia", "partition": 1, "type": "door" }, { "zoneNumber": 17, "name": "Movimiento Lavanderia", "partition": 1, "type": "motion" }, { "zoneNumber": 10, "name": "Puerta Cristal Cochera", "partition": 1, "type": "door" }, { "zoneNumber": 16, "name": "Movimiento Pasillo Servicio", "partition": 1, "type": "motion" } ] }
I replicated the issue by causing a disconnect from the evl 4 module but don't really know what is causing the disconnect.
Thanks.
Same issue still happening, for some reason it now takes longer to disconnect (2-3 days), couldn’t find any other device (besides my hoobs) in my network talking the evl4 module.