Tried base samples on 3 devices:
- Raspberry 3b+ works fine
- Odroid - no
- Intel Nuc - no
Where is the difference?
Hi,
Can you give us more details on what does not work or what errors you see for Odroid and Intel Nuc? Thank you.
ID: 4
DEVICE TYPE: intel-nuc
STATUS: idle
IS ONLINE: true
IP ADDRESS: 192.168.0.107
APPLICATION NAME: Intel
UUID: 0abc06fd3fc963c16d094b1474b3fea3
COMMIT: b9e9170a52a1830ceba0785cdec17c3b
SUPERVISOR VERSION: 10.0.3
OS VERSION: balenaOS 2.39.0+rev3
DASHBOARD URL: https://dashboard.visoagent.xyz/devices/0abc06fd3fc963c16d094b1474b3fea3/summary
ID: 1
DEVICE TYPE: raspberrypi3
STATUS: offline
IS ONLINE: false
IP ADDRESS: 192.168.0.102 192.168.42.1
APPLICATION NAME: rasp_v3
UUID: e23d98a214a1c1056187efb86b64146b
COMMIT: 7f519b460f0984301b8c62144a836227
SUPERVISOR VERSION: 9.15.7
OS VERSION: balenaOS 2.38.0+rev1
DASHBOARD URL: https://dashboard.visoagent.xyz/devices/e23d98a214a1c1056187efb86b64146b/summaryI can confirm that 192.168.42.1 - wifi spot on rasp device.
I’m not guru in balena os. if you could provide some commands to figure out, I will say thanks many times 
it’s the same project for both applications.
@ afitzek
Can you get the logs for the Intel nuc? This should work with balena logs 0abc06fd3fc963c16d094b1474b3fea3.
[Logs] [8/30/2019, 1:25:33 PM] [main] * Running on http://0.0.0.0:80/ (Press CTRL+C to quit)
[Logs] [8/30/2019, 2:21:34 PM] Downloading image 'registry.visoagent.xyz/v2/07724906fb659e117bf00f4bf9348390@sha256:5c861ff7784f47c5b60eef421b7dfe962ab828d3bee0783c5993eaaeb2b3a104'
[Logs] [8/30/2019, 2:24:28 PM] Downloaded image 'registry.*.xyz/v2/07724906fb659e117bf00f4bf9348390@sha256:5c861ff7784f47c5b60eef421b7dfe962ab828d3bee0783c5993eaaeb2b3a104'
[Logs] [8/30/2019, 2:24:29 PM] Killing service 'main sha256:33cc75c2bd56143b25db98b35942ab544074dcf400ac3a2588baa755cf733e65'
[Logs] [8/30/2019, 2:24:41 PM] Service exited 'main sha256:33cc75c2bd56143b25db98b35942ab544074dcf400ac3a2588baa755cf733e65'
[Logs] [8/30/2019, 2:24:41 PM] Killed service 'main sha256:33cc75c2bd56143b25db98b35942ab544074dcf400ac3a2588baa755cf733e65'
[Logs] [8/30/2019, 2:24:42 PM] Deleting image 'registry.visoagent.xyz/v2/ae3b0fe12f390b7f132b33fe9a5326c1@sha256:2542d622376178fe5da5103b41406d8b2ff58583b4d000260cd055ee09f1f530'
[Logs] [8/30/2019, 2:24:43 PM] Deleted image 'registry.visoagent.xyz/v2/ae3b0fe12f390b7f132b33fe9a5326c1@sha256:2542d622376178fe5da5103b41406d8b2ff58583b4d000260cd055ee09f1f530'
[Logs] [8/30/2019, 2:24:48 PM] Installing service 'main sha256:d6d567e6e825ce3c11721447815ccc4ea4e9990ae300af343fecff7514256f66'
[Logs] [8/30/2019, 2:24:59 PM] Installed service 'main sha256:d6d567e6e825ce3c11721447815ccc4ea4e9990ae300af343fecff7514256f66'
[Logs] [8/30/2019, 2:24:59 PM] Starting service 'main sha256:d6d567e6e825ce3c11721447815ccc4ea4e9990ae300af343fecff7514256f66'
[Logs] [8/30/2019, 2:25:04 PM] Started service 'main sha256:d6d567e6e825ce3c11721447815ccc4ea4e9990ae300af343fecff7514256f66'
[Logs] [8/30/2019, 2:25:03 PM] [main] Starting WiFi Connect
[Logs] [8/30/2019, 2:25:03 PM] [main] Error: Cannot find a WiFi device
[Logs] [8/30/2019, 2:36:14 PM] Downloading image 'registry.visoagent.xyz/v2/86f9d3bff48112d013e8e57e1e631bc9@sha256:e0446a489bdce0e5397d78ef9cd52c30849b4e9d7d1b1711a9c1d875519cf86a'
[Logs] [8/30/2019, 2:47:17 PM] Downloaded image 'registry.visoagent.xyz/v2/86f9d3bff48112d013e8e57e1e631bc9@sha256:e0446a489bdce0e5397d78ef9cd52c30849b4e9d7d1b1711a9c1d875519cf86a'
[Logs] [8/30/2019, 2:47:18 PM] Killing service 'main sha256:d6d567e6e825ce3c11721447815ccc4ea4e9990ae300af343fecff7514256f66'
[Logs] [8/30/2019, 2:47:30 PM] Service exited 'main sha256:d6d567e6e825ce3c11721447815ccc4ea4e9990ae300af343fecff7514256f66'
[Logs] [8/30/2019, 2:47:30 PM] Killed service 'main sha256:d6d567e6e825ce3c11721447815ccc4ea4e9990ae300af343fecff7514256f66'
[Logs] [8/30/2019, 2:47:31 PM] Deleting image 'registry.*.xyz/v2/07724906fb659e117bf00f4bf9348390@sha256:5c861ff7784f47c5b60eef421b7dfe962ab828d3bee0783c5993eaaeb2b3a104'
[Logs] [8/30/2019, 2:47:32 PM] Deleted image 'registry.*.xyz/v2/07724906fb659e117bf00f4bf9348390@sha256:5c861ff7784f47c5b60eef421b7dfe962ab828d3bee0783c5993eaaeb2b3a104'
[Logs] [8/30/2019, 2:47:35 PM] Installing service 'main sha256:a2083fdf6e12b4c859e8af857ed9de025e41f9ec002758406ee574a80425a8fd'
[Logs] [8/30/2019, 2:47:41 PM] Installed service 'main sha256:a2083fdf6e12b4c859e8af857ed9de025e41f9ec002758406ee574a80425a8fd'
[Logs] [8/30/2019, 2:47:41 PM] Starting service 'main sha256:a2083fdf6e12b4c859e8af857ed9de025e41f9ec002758406ee574a80425a8fd'
[Logs] [8/30/2019, 2:47:46 PM] Started service 'main sha256:a2083fdf6e12b4c859e8af857ed9de025e41f9ec002758406ee574a80425a8fd'
[Logs] [8/30/2019, 2:47:50 PM] [main] * Running on http://0.0.0.0:80/ (Press CTRL+C to quit)
== HIDDEN FROG
ID: 6
DEVICE TYPE: odroid-xu4
STATUS: idle
IS ONLINE: true
IP ADDRESS: 192.168.178.36
APPLICATION NAME: Odroid
UUID: e05fcf09757626874c89eb67d73b9f7e
COMMIT: 474dfea42d3858fa43e9c20e98693155
SUPERVISOR VERSION: 9.15.7
OS VERSION: balenaOS 2.38.3+rev2
DASHBOARD URL: https://dashboard.*.xyz/devices/e05fcf09757626874c89eb67d73b9f7e/summary
let’s investigate on Oroind device
why?
Did you push the plain wifi-connect application, or did you embed the project into an application of yours?
Tried a ton of examples. But to be on same page using this one:
mexekanez-2:wifi-connect mexekanez$ balena deploy Odroid --logs --source . --build
[debug] original argv0="/usr/local/lib/balena-cli/bin/node" argv=[/usr/local/lib/balena-cli/bin/node,/usr/local/lib/balena-cli/bin/run,deploy,Odroid,--logs,--source,.,--build] length=8
[Debug] Parsing input...
[Debug] Loading project...
[Debug] Resolving project...
[Debug] Failed to resolve project:
[Debug] AggregateError of:
[Debug] Error: ENOENT: no such file or directory, open '/Users/mexekanez/work/wifi-connect/docker-compose.yml'
[Debug] Error: ENOENT: no such file or directory, open '/Users/mexekanez/work/wifi-connect/docker-compose.yaml'
[Info] Creating default composition with source: /Users/mexekanez/work/wifi-connect
[Debug] Creating project...
[Info] Building for armv7hf/odroid-xu4
[Build] Building services...
[Build] main Preparing...
[Debug] Found build tasks:
[Debug] main: build [.]
[Debug] Resolving services with [odroid-xu4|armv7hf]
[Debug] Found project types:
[Debug] main: Dockerfile.template
[Debug] Prepared tasks; building...
[Build] main Step 1/6 : FROM balenalib/odroid-xu4-debian
[Build] main ---> 8b9cfa328873
[Build] main Step 2/6 : RUN install_packages dnsmasq wireless-tools
[Build] main ---> Using cache
[Build] main ---> 21bb5df9b593
[Build] main Step 3/6 : WORKDIR /usr/src/app
[Build] main ---> Using cache
[Build] main ---> c91038721545
[Build] main Step 4/6 : RUN curl https://api.github.com/repos/balena-io/wifi-connect/releases/latest -s | grep -hoP 'browser_download_url": "\K.*armv7hf\.tar\.gz' | xargs -n1 curl -Ls | tar -xvz -C /usr/src/app/
[Build] main ---> Using cache
[Build] main ---> e41e3acf84b3
[Build] main Step 5/6 : COPY scripts/start.sh .
[Build] main ---> Using cache
[Build] main ---> f5ede603a5f4
[Build] main Step 6/6 : CMD ["bash", "start.sh"]
[Build] main ---> Using cache
[Build] main ---> d6d567e6e825
[Build] main Successfully built d6d567e6e825
[Build] main Successfully tagged wifi-connect_main:latest
[Build] main Waiting...
[Build] Built 1 service in 0:12
[Info] Creating release...
[Debug] Tagging images...
[Debug] Authorizing push...
[Debug] Requesting access to previously pushed image repo (v2/86f9d3bff48112d013e8e57e1e631bc9)
[Info] Pushing images to registry...
[Debug] Saving image registry.visoagent.xyz/v2/b215570aa56079faf235d0e3f31c552e
[Debug] Untagging images...
[Info] Saving release...
[Success] Deploy succeeded!I see that you use an odroid-xu4 which does not have a built in wifi adapter. What WiFi adapter do you use there?
BIG thanks!!!
oh… really… I didn’t knew since it’s remote device… flashed with balenaos… let me check intel device…
It seems like it loads fine. It might be that the driver or the chip does not support AP mode, which would mean wifi-connect cannot use it to create a hotspot. What WiFi-adpater are you using and for which device (Odroid or Intel Nuc)?
To check if the driver and chip can do ap mode, you could add a NM connection like this:
[connection]
id=Hotspot
uuid=60e385b1-6b4f-49be-9fcf-7548b3f4949b
type=wifi
autoconnect=true
permissions=
[wifi]
mac-address-blacklist=
mode=ap
ssid=test
[wifi-security]
group=ccmp;
key-mgmt=wpa-psk
pairwise=ccmp;
proto=rsn;
psk=test1234
[ipv4]
dns-search=
method=shared
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=ignore
This should span a hotspot manually and would mean that the device and driver is capable of switching to AP mode.
could you please provide a patch? where I can find this config?
I’m own you a beer 
Hi @mexekanez,
Take a look at our docs on how to set up a hotspot: Network Setup on balenaOS - Balena Documentation. Specifically, towards the top of the page note the following in the introduction (Network Setup on balenaOS - Balena Documentation):
All of the network configuration for balenaOS can be done though files in the boot partition of your device. If you have a freshly downloaded balenaOS .img, you can mount it and inspect the resin-boot or resin-flash (for devices that boot from eMMC) partition. In the boot partition you will find a directory called system-connections.
Please let us know the results of your test!