Can't activate scenes

[bland328]

Using node-red-contrib-lifx-api 1.2.0 under Node-RED v0.20.5, when I trigger an lifx-activate-scene node configured with my API Token, a Duration and a Selector in the form of:

scene_id:c5156204-3921-40a6-9e37-432d9ae15ah0

I do successfully get back a payload resembling this, correctly referring to the two globes in the scene:

{"payload":{"results":[{"id":"d073d5898dc3","status":"ok","label":"Light 1"},{"id":"d073d523cef3","status":"ok","label":"Light 2"}]}}

The scene, however, isn't activated.

The scene is activated, however, if I provide the same Selector and API token in the LIFX 'Try it Out' form at the bottom of:

https://api.developer.lifx.com/docs/activate-scene

I greatly appreciate the work put into this project, and I'm happy to provide more information if it might help!

[alisdairjsmyth]

Note there is an issue with the dependent package which impacts this capability.

[bland328]

Ah! I'll watch for an update to lifx-http-api. Thanks for the quick response.

(Oops...realizing I probably shouldn't have closed, since there's not yet a fix ;) )

[johnfenwick]

In the file life-http-api/dist/lifx.js, line 386 needs to be changed from:
url: 'lights/' + selector + '/cycle',
to:
url: 'scenes/' + selector + '/activate',
Sorry, I don't know how to do pull/push requests!

Edit: whoops. Looks like you've already made that request @alisdairjsmyth Thanks!

[alisdairjsmyth]

No problem @johnfenwick - as you have noted a pull request has been submitted on klarstil/lifx-http-api with this fix

[bland328]

I'm (finally) taking another look at this, but having no luck.

Based on what I see at klarstil/lifx-http-api#6 and klarstil/lifx-http-api@d9299fc, it appears this should now be working, but I'm still having no luck, and my results still match my original post from a couple years ago.

I'm now on Node-RED 1.3.5 and node-red-contrib-lifx-api 1.2.1, and everything I've tried aside from lifx-activate-scene node works great.

However, when I trigger lifx-activate-scene, nothing happens, and the node output looks like this:

_msgid: "bb4c49b1.b1b5a8"
payload: undefined
topic: ""

Since that node is fully configured, my expectation is that even an empty message sent to the node should trigger it—do I have that right?

Edit: I see there's there's been another report of this at #14.

[CypherMK]

Did you get this to work? Or still the same issue? I'm running into the same problem.