WiFi Connected block security output

[corganp...@gmail.com]

The WiFi Connected block outputs a number for the "Connected network security" output variable. Does anybody know how to translate this number to the security type on the network?

[Henrik "The Developer" Lindqvist]

You can see the bit flags (values) in the Wi-Fi network scan block, i.e. 1=WPA, 2=WPA2, 4=WEP

[corganp...@gmail.com]

Thank you Henrik. So it looks like the security type should be an integer from 0-7, right? The value I'm getting is 1114115. What am I missing here?

[Henrik "The Developer" Lindqvist]

It's a bit flags, and there's other unofficial bits. To mask just the "protocol" do:

(security & 7) = 4

https://en.wikipedia.org/wiki/Bit_field

[corganp...@gmail.com]

Ok thank you for walking me through this. So in my case:
(security & 7) = 3
This means that WPA and WPA2 are enabled (WPA = 1, WPA2 = 2, WEP = 4) on the network, right?

[Henrik "The Developer" Lindqvist]

No, 7 (1+2+4) is to mask out the unofficial bits, 4 was for WEP:

(security & 7) = 4

for WPA:

(security & 7) = 1

for WPA2:

(security & 7) = 2

You could also do, to check for WEP:

security & 4

for WPA:

security & 1

for WPA2:

security & 2

[corganp...@gmail.com]

Ok, so what does it mean when (security & 7) = 3? This is the result I'm getting. I checked my WiFi settings and under Security it says 'WPA/WPA 2 PSK'.

[Henrik "The Developer" Lindqvist]

3 = 1+2 = WPA+WPA2

[corganp...@gmail.com]

Ok got it. Thank you for all your help, Henrik!

[Automate for Android]

This should be included in the docs. 

[Automate for Android]

A simple function I came up with, that gives you an array of securities:

filter(sift([null, "WPA", "WPA2", null, "WEP"], [security & 1, security & 2, security & 4]))

[Henrik "The Developer" Lindqvist]

Indeed. I'll add it.

[8li...@gmail.com]

IS DOCS = https://llamalab.com/automate/doc/block/wifi_network_scan.html

ב-יום רביעי, 20 בספטמבר 2023 בשעה 12:44:28 UTC+3, Henrik "The Developer" Lindqvist כתב/ה:

[Henrik "The Developer" Lindqvist]

Hmm, i don't think it's necessary there since the user can deduce them from the input argument field, as in every other block.

I usually only add explicit documentation for input argument and output variable values where there's no other way to know their values.