Envisalink_new integration can't connect to DscServer.jar

Configuration
1

I just tried moving from the old envisalink integration to envisalink_new and whatever I try, the integration always respond with a “Failed to connect” with the following in the log file when trying to connect to the DscServer.jar:

2024-02-27 11:40:56.014 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.alarm_panel] Unable to validate connection: ClientConnectorError(ConnectionKey(host=‘192.168.40.70’, port=80, is_ssl=False, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, “Connect call failed (‘192.168.40.70’, 80)”))

The following is what was entered in the basic configuration page

image
image373×861 16.9 KB

I don’t really understand why the log is reporting port=80 ??? should’nt it report 4025 as configured on the configuration page ?

I know my DscServer environment is working and that this is not a firewall issue or anything since prior installing the new envisalink_new, my envisalink.yaml was configured to connect to the same unchanged DscServer.jar with no issues, also, my other system is still connecting to the DscServer with same credentials.

I then made sure nothing was wrong with the installation and tried connecting with success directly to the Envisalink 3 bord.

As I am connecting two Automation system to my alarm, I need to have a way to connect both system hence the reason why I installed DscServer.jar

I tried removing completely the integration (including all HACS files) but that did not change a thing

Info: the DscServer.jar is not running on the same machine/VLAN as my HA

Anyone has been able to use DscServer with the new integration ?

2

I found connecting Homeseer and HA to one EVL was a bit of a nuisance using DSCServer.jar, so I installed a second EVL in the panel. That may be an option to consider. I have 1-EVL3 and 1-EVL4 This way there is no third party running a server bridge and eliminates a single point of failure.

Does DSCServer even use port 4025 ? Disregard this I see that the native DSC integration also uses 4025.

3

Tought of this but the problems isI would need two other EVL (i need 3 connection overall) plus my 24 port Unifi switch if full, I don’t feel like spending another few undreed CAD $$ to buy the envisalink and a new switch.

I am pretty sure that problem can be fixed without too much of a burden, both developers showed interest in fixing the issue, we just need to figure out what exactly is not working and my feeling is that someone will fix this and this would serve the community. I am pretty sure there are many users who would benefit from this.

If it come to a place where no one agrees to fix the problem then definitly i’ll have to find another solution.

thanks for this

1 Like
4

Just a note to let everyone know that Mike fixed the issue there was with the dscserver.jar, I have been running the new version for the last 4 days and everything is working perfectly, thanks Mike