update - my wife’s iPhone worked ! The lights changed from solid red to cyan and it connected and went through the whole process ok. Really odd.
I’ll write up the ‘three’ different devices that didn’t work and their os levels, as there has to be some kind of BLE compatibility issue in the WF software.
And I see the hub transmitting with tcpdump, so I’m off to the reading UDP races !!!
sudo tcpdump -i en0 'udp and port 50222' -vvv
Password:
tcpdump: listening on en0, link-type EN10MB (Ethernet), capture size 262144 bytes
17:08:30.464663 IP (tos 0x0, ttl 255, id 1060, offset 0, flags [DF], proto UDP (17), length 136)
192.168.1.151.50222 > broadcasthost.50222: [no cksum] UDP, length 108
17:08:30.669501 IP (tos 0x0, ttl 255, id 1062, offset 0, flags [DF], proto UDP (17), length 182)
192.168.1.151.50222 > broadcasthost.50222: [no cksum] UDP, length 154
17:08:30.669874 IP (tos 0x0, ttl 255, id 1064, offset 0, flags [DF], proto UDP (17), length 129)
192.168.1.151.50222 > broadcasthost.50222: [no cksum] UDP, length 101
17:08:30.976585 IP (tos 0x0, ttl 255, id 1066, offset 0, flags [DF], proto UDP (17), length 139)
192.168.1.151.50222 > broadcasthost.50222: [no cksum] UDP, length 111
17:08:31.386210 IP (tos 0x0, ttl 255, id 1068, offset 0, flags [DF], proto UDP (17), length 136)
192.168.1.151.50222 > broadcasthost.50222: [no cksum] UDP, length 108
17:08:32.307861 IP (tos 0x0, ttl 255, id 1070, offset 0, flags [DF], proto UDP (17), length 136)
192.168.1.151.50222 > broadcasthost.50222: [no cksum] UDP, length 108