I’ve been fighting with the configuration of my LIFX bulbs since I changed from using my trusty AirPort Express “puck” access point to the RBwAP2nD that I purchased a month or so ago. The bulbs I had are the original Kickstarter release models which I bought because I’m a terrible toy-hound.
Turns out I’d hit two problems, one being that certain bulbs running their 2.1 firmware just don’t like changing the SSID they’re associated with, and the second being that client-to-client forwarding wasn’t enabled correctly on the new AP. I could test the former by starting up the old AP and they’d connect straight up, the latter seemed intermittent. I could Communicate between a RaspberryPi and my laptop, but couldn’t ping the bulbs.
LIFX replaced both the faulty bulbs - I couldn’t get them to connect to the new SSID and they were clearly having a known issue - in only three days! Great service, I’ll definitely say. I got them connecting successfully to the new AP fine, could see them on the registration screen and everything. They just wouldn’t respond to ping or register properly. This requires communication between the mobile phone and the bulb, it seems. After a few random hail-mary settings changes (and reversions) I found the right setting.
The difference tonight seems to be that I set client-to-client forwarding explicitly on the “configuration” tab and not just the datapath - even though the datapath configuration should override/set it. This caused a bit of a drop on the wireless for a minute or so, then it all came up and was working fine. Yet another Mikrotik oddity I guess.
Here’s my config (with a few redacted details):
/caps-man manager set enabled=yes /caps-man interface add arp=enabled disabled=no l2mtu=0 mac-address=00:00:00:00:00:00 master-interface=none mtu=1500 name=cap1 radio-mac=00:00:00:00:00:00 /caps-man datapath add bridge=bridge-cap client-to-client-forwarding=yes name=housenet-internal /caps-man security add authentication-types=wpa2-psk comment=main encryption=aes-ccm group-encryption=aes-ccm name=housenet-internal passphrase=[redacted] /caps-man provisioning add action=create-dynamic-enabled master-configuration=housenet-internal name-format=prefix name-prefix=AP /caps-man configuration add country=australia datapath=housenet-internal datapath.bridge=bridge-cap datapath.client-to-client-forwarding=yes mode=ap name=housenet-internal security=housenet-internal ssid=[redacted]
The main lines are the configuration and datapath ones - but also note the specific encryption settings, since the LIFX bulbs don’t like lower security levels. Another issue to check for is the channel - they’ll only work on 1-11.
On to the next problem!