running v0.13 now on my home lan with 3 AP's. client list now good. collecting radio frequencies and power data - but i'm not yet sure what to do with it.
great work - thank you.
i'm still in the preocess of learning how to deploy and make this tool useful.
i may have missed it - but how does one shut down the opensoho server? i've only successed to kill the process.
Do you use home assistant? On the list™ is exporting that data as energy meter and presence detection via MQTT.
Sending it a nice kill signal is the normal way to shut it down. kill -9 would be hard kill.
Small confusion: here the "power data" is not PoE power data. This is indeed planned (aka on the list 
, with export to home assistant (I only need to figure out an elegant way of implementing it 
).
The current release focuses on the radio settings and the radio transmission (tx) power.
What has been improved is that OpenSOHO now knows which frequencies are actually supported (not an educated guess based on the currently configured frequency).
And which power outputs, output power adjustments were not yet supported at all. So that has been added, an all values now have a better error checking thanks to these values:
To shut down OpenSOHO indeed, just kill it, preferably not with -9 since that leaves the database in an inconsistent state.
still playing with opensoho and have successfully configured AP's centrally. client list is working better now.
more implementation questions:
1- can i change IP addr of device/AP centrally ? (i think not)
2 - the openwisp-config package seems to require curl, which seems to require libmbedtls21. i have beeen deploying my openwrt network using openssl. since 25.12.4 at least, i have not been able to avoid the mbedtls subsystem with curl.. any pointer on thisd would be welcomes. thank you!
Not yet indeed. Although thinking about it, it sounds like a good idea to add, since openwisp-config will check connectivity after each change, so the config will fail to apply if the device would become inaccessible.
Hmm, I haven't played with that, so unfortunately I cannot help there, maybe someone else has experience with that.
up and running.
the radio frequencies overview is neat, but seems to only collect from radio 0 on AP's.
i've got 3 AP's' radio 0 is used on one, and radios 1-2 are used on all three. this is the the collected frequency report:
let me know what you might need to help with this great project
thank you!
Great!
Let's have a look at the problem though, since for me it works fine 
Could you have a look what the output is of this:
ssh thedevice /etc/hotplug.d/openwisp/opensoho -d | jq .radios | grep name
It should return the radios, if it only returns 1 radio, we know we have to have another look at the data collection script
"name": "radio0",
"name": "Generic MAC80211"
"name": "radio1",
"name": "Generic MAC80211"
Also there is caching (since I don't want to send this static data every 30 seconds), so that could also be a factor if not all radios are up immediately, although, while writing this, the cache should be invalidated in case the values change 
I have a ASUS BT8 supporting Wifi7 and 3 radios. Is it possible to add support for 6 GHz bands?
Hi @epkulse ,
I'm aware of this, I haven't invested in a 6GHz AP yet since they are quite expensive, and I personally don't have the need for 6GHz.
Donations are welcome (no matter the amount), and highly appreciated. https://buymeacoffee.com/rubenbe
When I have the HW at home it should be fairly easy to add. Since most of the code is not too frequency dependent, it is just very untested (for the reasons above). It could probably be part of the next release.
thanks for your understanding!
Also hints for "cheap" EU-available 6GHz APs are very welcome 
here you go:
root@ap10:~# ssh root@192.168.1.251 /etc/hotplug.d/openwisp/opensoho -d |grep name
{"type":"OpenSoho","radios":[{"name":"radio0","phy":"phy0","disabled":"0","info":{
"name": "Qualcomm Atheros IPQ8074"
root@ap10:~#
note: .jq not found on my opensoho device ap10)
You should not run it from your AP, but from your PC. In case you don't have jq, you can also paste the whole output of the command: ssh root@192.168.1.251 /etc/hotplug.d/openwisp/opensoho -d . PS: jq should be available via apt/dnf/...
this returns nothing.
there is no /openwisp/opensosho in /etc/hotplug.d:
root@ap251:~# ls -l /etc/hotplug.d
drwxr-xr-x 2 root root 3 Jun 29 12:59 dhcp
drwxr-xr-x 2 root root 40 Jun 29 12:59 firmware
drwxr-xr-x 2 root root 108 Jun 29 12:59 ieee80211
drwxr-xr-x 2 root root 79 Jun 29 12:59 iface
drwxr-xr-x 2 root root 30 Jun 29 12:59 leds
drwxr-xr-x 2 root root 3 Jun 29 12:59 neigh
drwxr-xr-x 2 root root 32 Jun 29 12:59 net
drwxr-xr-x 2 root root 36 Jun 29 12:59 ntp
drwxr-xr-x 2 root root 3 Jun 29 12:59 tftp
drwxr-xr-x 2 root root 32 Jun 29 12:59 usbmisc
That's interesting, I've seen something similar after an openWRT upgrade. (I just added a fix to have the opensoho files preserved over an update, this should be fixed in the next opensoho release).
BUT that being said, the openwisp folder should be there containing the openwisp-monitoring file.
Can you verify that you have openwisp-monitoring installed.
You can redeploy the openwisp files by doing a small modification. e.g modifying the device hostname. That should trigger a new deploy.
Maybe also have a look at how your radios are named, since opensoho expects them to be called radioN.
cat /etc/config/wireless | grep wifi-device
config wifi-device 'radio0'
config wifi-device 'radio1'
Some extra interesting info:
cat /etc/config/wireless | grep path
option path 'platform/ahb/18100000.wmac'
option path 'pci0000:00/0000:00:00.0'
and this command:
lrwxrwxrwx 1 root root 0 Jun 5 19:47 /sys/class/ieee80211/phy0 -> ../../devices/platform/ahb/18100000.wmac/ieee80211/phy0
lrwxrwxrwx 1 root root 0 Jun 5 19:47 /sys/class/ieee80211/phy1 -> ../../devices/pci0000:00/0000:00:00.0/ieee80211/phy1
You can also find the /etc/hotplug.d/openwisp/opensoho script on github:
https://raw.githubusercontent.com/rubenbe/opensoho/refs/heads/main/scripts/dump-radios.sh
I've released some bugfixes:
' are now properly escaped to avoid breaking UCI files.429 code to trigger a delayed retry by the openwisp-monitoring in that case.I bought the ASUS BT8, which is supported by Openwrt. It is not too expensive, I paid ca 180 Euro.
https://www.asus.com/se/networking-iot-servers/whole-home-mesh-systems/asus-zenwifi/asus-zenwifi-bt8/
Thanks @epkulse .
I had a look at them, but in Belgium they're all at least 250 euro which crosses a psychological boundary.
If you buy multiple, you get them quite cheap starting at 330 euro. But I only need one at this moment. And I already have a massive stash of APs
But I found the "Acer Predator Connect W6 Wi-Fi 6E" which is Wifi 6, but with 6 GHz for less than 100 euro (so very reasonable) . Expect 6GHz support soon (probably 0.15.0). You might need to do a bit of experimenting since Wifi 7 also has the 320MHz bandwidth which I can't test. (but I expect it to work). I'll continue to monitor the pricing of the Asus BT8 tough, maybe I can catch a nice promo.
W1700K from the US should be around 100 Euros with shipping (only supported on Snapshot and still under heavy development as a target, but WiFi 7).
thanks @p.p !
I'll keep a look at that one too, both pricing and OpenWRT stability point of view. (Although the price is already crazy sharp)
And it is 10Gb plus it has a zigbee/matter radio, fancy.
In the end it becomes 123 euro with VAT included when starting the checkout on Amazon, but still very reasonable.
It might be slightly cheaper on eBay (probably the same seller), but you have to monitor the keyword for that.