Closed doncarajo closed 1 year ago
That's very unfortunate to hear π€¬ I have an NX6v2 system with the NX595E network module installed with the ComNav 0.108O firmware revision installed on the latter.
SSL errors theoretically occur when attempting to connect via https to the web interface (and are caused by a deprecated TLS/SSL cipher suite that it uses). The installer manual explicitly states that SSL access is not supported anymore as its implementation is too old; the old manual mentions Location 19, option 2 as the SSL setting (has to be turned off to allow standard http connections), which can be set using the standard programming using the control panel of the alarm installation (typically starting with *8 -> [master PIN] -> 191#, and then changing the option value as usual). Please do note that tampering with the control panel and system settings can mess up your installation severely, so it would be best to do this with your security technician's help.
That being said, the plugin explicitly uses http:// calls, so other than the idea described above, I really have nothing else to suggest, and there is no practical way to force an SSL connection, short of installing a custom-build version of both node and the plugin itself to allow for the ancient cipher suite; needless to say, this is both dangerous and impractical, sadly.
I'll leave the issue open for a while; feel free to get back in touch with any kind of updates ππ»βπ»
Hi mate. I have become quite familiar with resetting the module. What happens is that everything is working fine then the module crashes and turns on the SSL by ITSELF. The only way to access the webpage then becomes by resetting the whole thing and disabling SSL (and redoing the options properly). I can crash the module now by just refreshing the webpage too many times. I suspect the polling from your plug in has the same effect.
On 18 Nov 2022, at 9:50 am, Spyros Smparounis @.***> wrote:
That's very unfortunate to hear π€¬ I have an NX6v2 system with the NX595E network module installed with the ComNav 0.108O firmware revision installed on the latter.
SSL errors theoretically occur when attempting to connect via https to the web interface (and are caused by a deprecated TLS/SSL cipher suite that it uses). The installer manual explicitly states that SSL access is not supported anymore as its implementation is too old; the old manual mentions Location 19, option 2 as the SSL setting (has to be turned off to allow standard http connections), which can be set using the standard programming using the control panel of the alarm installation (typically starting with *8 -> [master PIN] -> 191#, and then changing the option value as usual). Please do note that tampering with the control panel and system settings can mess up your installation severely, so it would be best to do this with your security technician's help.
That being said, the plugin explicitly uses http:// calls, so other than the idea described above, I really have nothing else to suggest, and there is no practical way to force an SSL connection, short of installing a custom-build version of both node and the plugin itself to allow for the ancient cipher suite; needless to say, this is both dangerous and impractical, sadly.
I'll leave the issue open for a while; feel free to get back in touch with any kind of updates ππ»βπ»
β Reply to this email directly, view it on GitHub https://github.com/flareman/homebridge-caddx-interlogix/issues/18#issuecomment-1319310044, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOFXUYSEWNI4VW7MHGL26WTWI2ZCPANCNFSM6AAAAAASCUARF4. You are receiving this because you authored the thread.
It really shouldn't lock up like this; all I can suggest is reducing the polling frequency (increasing the polling interval), to reduce calls to the web interface. EDIT: The web interface polls every 5500 ms from what I can see in their Javascript, so I guess that would work without faults; of course, that means waiting for 5,5 seconds for HomeKit to update the displayed sensor states. The NX-595E is a hot mess coding-wise, the integrated HTTP server that the module serves respects close to no common practices, and its behavior is erratic outside the web interface (and, sometimes, within the web interface as well). It's unfortunate that there are no firmware upgrades to be expected too. What versions are you running? You could see this in the web interface -> Feature Setup (firmware, hardware, bootload, and web version fields).
Hi. The module just has become increasingly sensitive to poll requests. It is quite brittle now. Firmware 2.0k, hardware 1.0, bootload 4.0, web version CN_0.106-j. I increased the polling time to 10 secs but it still crashes it. Surely the hardware is now faulty?
On 19 Nov 2022, at 4:17 am, Spyros Smparounis @.***> wrote:
It really shouldn't lock up like this; all I can suggest is reducing the polling frequency (increasing the polling interval), to reduce calls to the web interface. The NX-595E is a hot mess coding-wise, the integrated HTTP server that the module serves respects close to no common practices, and its behavior is erratic outside the web interface (and, sometimes, within the web interface as well). It's unfortunate that there are no firmware upgrades to be expected too. What versions are you running? You could see this in the web interface -> Feature Setup (firmware, hardware, bootload, and web version fields).
β Reply to this email directly, view it on GitHub https://github.com/flareman/homebridge-caddx-interlogix/issues/18#issuecomment-1320306477, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOFXUYQWXTIY7ZOYF4M6R6LWI62ZJANCNFSM6AAAAAASCUARF4. You are receiving this because you authored the thread.
My module is running firmware A55P003001-03, hardware 206144IX12, bootloader B0402002, web version CN_0.108-O; maybe this older version works bad with multiple polling requests? Then again it was working in the past, so maybe it is just going faulty. If you had access to a second network module that's known to work, you could replace the present one with the good one and check for crashes, but I'm guessing this is taking it a bit too far π€· I just don't see how or why the module should crash when polled multiple times; even the web interface polls every 5500 ms, and that's by design from Interlogix. If you log in the web interface and leave it logged in like that for an extended period of time, will it crash too?
If I leave the webpage open it doesnβt to crash. If I reload the webpage a few times it does crash. I agree that because it used to work, that the card is probably going faulty. Iβll see if I can get another card to check it out. Will keep you updated. You can probably close this issue as it seems related to the hardware not your software. Thank you.
On Sat, 19 Nov 2022 at 19:39, Spyros Smparounis @.***> wrote:
My module is running firmware A55P003001-03, hardware 206144IX12, bootloader B0402002, web version CN_0.108-O; maybe this older version works bad with multiple polling requests? Then again it was working in the past, so maybe it is just going faulty. If you had access to a second network module that's known to work, you could replace the present one with the good one and check for crashes, but I'm guessing this is taking it a bit too far π€· I just don't see how or why the module should crash when polled multiple times; even the web interface polls every 5500 ms, and that's by design from Interlogix. If you log in the web interface and leave it logged in like that for an extended period of time, will it crash too?
β Reply to this email directly, view it on GitHub https://github.com/flareman/homebridge-caddx-interlogix/issues/18#issuecomment-1320835553, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOFXUYR6PWNLHF6YQ3A4TKTWJCG23ANCNFSM6AAAAAASCUARF4 . You are receiving this because you authored the thread.Message ID: @.***>
Thanks so much for your continued support debugging the plugin ππ»
Hi again! So after your plug in was working very well for a number of days I started getting the dreaded SSL error again. They became more frequent after I reset the card from the security panel and now it's to the point that the card locks itself into SSL mode every few seconds. I downgraded to v1.22 and the same thing happens so I suspect it's a hardware thing. The only thing I haven't done is take the power off the card which I will probably try later, it's just awkward. Which card do you use? I remember you saying you had a different version to mine. I wonder if I can buy that and install it.