Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dual-port AirAlarms can not be saved as a device for the air alarm sync reasons #1369

Open
mqole opened this issue Jan 15, 2025 · 2 comments
Labels
Bug Somethings broken!

Comments

@mqole
Copy link

mqole commented Jan 15, 2025

so you can use a signaler on it but not an air alarm
image

the list mode on the multtool and network configureator isnt working
image
image

(submitted by qwat.)

@mqole mqole added the Bug Somethings broken! label Jan 15, 2025
@DinnerCalzone
Copy link

DinnerCalzone commented Jan 16, 2025

The short answer to this is that dual-port air vents are fucked up and evil devices and you generally shouldn't be using them for the same purposes as an air vent or air scrubber. The long answer is that you are meant to link dual port air vents directly with an air alarm and configure whether they blow air in our suck air out based on the air alarm's alarm status. You use this in conjunction with an air sensor linked to the air alarm to configure what the normal, warning, and danger thresholds are.

As for distinguishing which port is for blowing and which one is sucking, I have no clue

ko6lUFU

gXho8tj

@DinnerCalzone
Copy link

Actually I found a video from an old PR on dual-port air vents that illustrates a sane use-case for them, but you still basically either have to do trial-and-error or just memorize which port is for pressurizing and which port is for depressurizing.

airlock.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Somethings broken!
Projects
None yet
Development

No branches or pull requests

2 participants