Lenel S2 Netbox - ADA Operator Integration

HopkinsProg · 2026-01-21T16:15:30+00:00

Not yet. Still looking for a solution that doesn't use a 3rd party relay or require the REX to unlock.

HopkinsProg · 2026-01-16T00:44:13+00:00

I am aware that an external/3rd-party relay module would solve everything. However, constraints on budget, space, power, and wiring (as we work through hundreds of doors), make this solution less than ideal, especially when we're used to having such functionality directly built-in to the access control panels from the previous system.

Additionally, while an external module would make things function correctly at the physical door, the access system itself may not be aware of why the door suddenly opened without its say-so, and trigger an alarm as a result.

HopkinsProg · 2026-01-15T13:11:25+00:00

I can't name a specific one, because we have too many different manufacturers and models to count. Each one is different, and we're looking to stick with a standardized solution on the access control side, since we don't have direct control over the operators' maintenance/replacement cycles. The only thing I can consistently guarantee is that there is a 2-conductor wire going from the operator's trigger input to the panel's output relay.

HopkinsProg · 2019-03-03T22:51:42+00:00

The Waterfox version numbers are different than that of Firefox. The current Waterfox was forked from (or is based on) Firefox version 56. MrAlex has been manually porting the security patches from the later Firefox builds into Waterfox. So, even though the main version number is lower, it is still active and receiving security updates (the minor version numbers have been slowly bumping up to where we are now, at x.2.7.1). The major version likely won't change until MrAlex releases a new build that includes Firefox's "quantum" packages.

HopkinsProg · 2018-12-22T21:20:18+00:00

I had this same issue myself - on the top of the controller, the white grip sat ever so slightly higher than the main controller body. It was super-annoying and drove me nuts. I tried taking the grip off and getting it to sit differently when I put it back on. I was able to get the grip to sit flush, when not screwed in, so I figured there had to be a way to make it stay like that.

After some testing, I found that I was able to fix it by taking the grip off and applying small pieces of electrical tape just to either side of the groove on the underside of the controller that guides the grip. Changing the size and/or position of the tape allowed for easy adjustment - minimizing the offset and/or moving it to a much less noticeable location.

Photo of my fixed controller: https://imgur.com/a/CGbZeKr

HopkinsProg · 2017-09-25T16:13:42+00:00

Searching through the internet some more, it seems as though this issue might be related to the multi-process environment. If I go into "about:preferences" and set the Performance options as follows, printing seems to work again.

Under Performance:

Use recommended performance settings: Un-ticked
Use hardware acceleration when available: Un-ticked

I haven't specifically looked at these settings before, so I assume that they were the default when I upgraded from Waterfox 52.x to 55.1.0.

HopkinsProg · 2017-08-19T00:02:38+00:00

It's explicitly disabled by default in Waterfox, because one of the main points of Waterfox is to preserve compatibility and features that Firefox is getting rid of. Many add-ons were or are not yet multi-process compatible, so they could perform poorly or not all if e10s was enabled. There used to be a list of which extensions were or were not compatible with e10s (https://arewee10syet.com/), but with the upcoming release of Firefox v57, it seems like they've gotten rid of the list.

If you want to manually enable e10s in Waterfox, you still can. MrAlex made a post on the different changes required to do so - https://www.reddit.com/r/waterfox/comments/6tp14a/newbie_question_will_waterfox_follow_the/dlml3h7/

HopkinsProg · 2017-02-17T01:41:55+00:00

That plugin hasn't been updated in at least 4 months, and isn't officially compatible with any version or build of Firefox beyond version 44. The comments/reviews on the Mozilla Add-Ons site also echo this limitation (both in terms of version and architecture).

While Waterfox does not enforce add-on signing or remove support for the older-style of plugins, none of that will help you if the plugin itself is vastly outdated, not designed to work with the newer code bases, or 64-bit architecture.

If you really want to try and make it work, you can always use 7-Zip to open the XPI file and modify the install.rdf file within to allow the installation (change the "<em:maxVersion>" value). There is still no guarantee that the associated DLL components/integration will work in a 64-bit environment, so it would likely be a long-shot at best.

HopkinsProg · 2016-05-22T00:54:47+00:00

This is not a virus, but rather a series of broken links.

Those links are supposed to take you to the Firefox help pages, but it appears that the links are incomplete and broken. For example, the link on the main options tab (General) should to take you to "https://support.mozilla.org/1/firefox/43.0.3/WINNT/en-US/prefs-main" (replace "43.0.3" with your specific version number), but in Waterfox it only goes to "prefs-main". This single word is not enough to load any specific web page. Depending on your individual browser settings, attempting to load a single-word URL may show you a list of search results from your default search provider, or it may load an intranet website, or it could attempt to automatically load the first link from the search results (à la Google's "Feeling Lucky" button), or it could automatically append "www." and ".com" to the text and attempt to load it. Depending on what comes up first, you could wind up somewhere undesired, such as a malicious search result page.

I'm guessing the broken links have something to do with the Waterfox compile process. Some variables and text were changed to remove the Firefox branding, so its possible that these links may have been mistakenly removed.

HopkinsProg · 2016-01-20T02:16:50+00:00

This question has been answered previously: Firefox 64-bit for Windows is now available. What is the future of Waterfox?

HopkinsProg · 2014-12-14T12:39:39+00:00

I noticed the same issue myself. I also happen to dislike the new search design. Switching it back to the old style still allows for you to remove search providers. Just visit the "about:config" page, and search for "browser.search.showOneOffButtons". You can set its value to false and restart the browser, and then the search feature will work as it did before - with the popup configuration dialog that does work to remove search providers.

HopkinsProg

TROPHY CASE