Selecting 'Re-Discover Bulbs' produces errors

[jkosharek]

I am looking for smart switches to jump ship on Inseton and find a keypad link replacement, so I am testing some LiFX switches and Lights for our new home. I am running IoP and PG3, I installed LiFX controller and the node was created on IoP, selecting 'Re-Discover Bulbs' produces these messages in the logs:

2022-07-27 23:47:14,685 Thread-96 udi_interface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2022-07-27 23:47:16,473 Thread-96 udi_interface INFO lifx-poly:_discovery_process: 0 bulbs found. Checking status and adding to ISY if necessary. 2022-07-27 23:47:16,475 Thread-96 udi_interface INFO lifx-poly:_discovery_process: LiFX Discovery thread is complete.

The devices are ping'able from the POLISY and I can run this command and lists the bulbs/switches.

curl "https://api.lifx.com/v1/lights/all" \
     -H "Authorization: Bearer YOUR_APP_TOKEN"
On the LiFX controller node in IoP, if I press All On or All Off, it controls the LIFX Z light strip, but not the switch.

Does the Node need an API Key created to auto-discover the bulbs and control them?

[Bumbershoot]

3 hours ago, jkosharek said:

I am looking for smart switches to jump ship on Inseton and find a keypad link replacement, so I am testing some LiFX switches and Lights for our new home. I am running IoP and PG3, I installed LiFX controller and the node was created on IoP, selecting 'Re-Discover Bulbs' produces these messages in the logs:

2022-07-27 23:47:14,685 Thread-96 udi_interface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2022-07-27 23:47:16,473 Thread-96 udi_interface INFO lifx-poly:_discovery_process: 0 bulbs found. Checking status and adding to ISY if necessary. 2022-07-27 23:47:16,475 Thread-96 udi_interface INFO lifx-poly:_discovery_process: LiFX Discovery thread is complete.

The devices are ping'able from the POLISY and I can run this command and lists the bulbs/switches.

curl "https://api.lifx.com/v1/lights/all" \
     -H "Authorization: Bearer YOUR_APP_TOKEN"
On the LiFX controller node in IoP, if I press All On or All Off, it controls the LIFX Z light strip, but not the switch.

Does the Node need an API Key created to auto-discover the bulbs and control them?

You shouldn’t need an API key, which is one of the great things about a local API.  I’d make a static reservation for these lights in your routing table, and search for “devlist.yaml” in this forum.  Sorry I can’t help you more, but I’m traveling out of the country for a while.