In 2.8.15 using a twinkly string 250 (gen 2), it appears that the app is sending more details with '/xled/v1/led/mode':
POST:
{ "mode": "color", "unique_id":"", "name": "", "id": 0, "detect_mode": 0, "color_config": { "red": 255, "green":41, "blue": 9, "white": 0 } }
which returns:
{ "mode": "color", "code": 1000 }
In essence, it seems like POST mode can now set the color (when switching to/in color mode) and movie/effect in one go, rather than separate calls. Interestingly, 'white' is included in the color_config, despite the string being RGB only.
GET similarly returns:
{ "mode": "movie", "detect_mode":0, "shop_mode": 0, "id": 10, "unique id": "[UUID]", "name": "Fireworks", "code": 1000 }
In 2.8.15 using a twinkly string 250 (gen 2), it appears that the app is sending more details with '/xled/v1/led/mode':
POST:
{ "mode": "color", "unique_id":"", "name": "", "id": 0, "detect_mode": 0, "color_config": { "red": 255, "green":41, "blue": 9, "white": 0 } }which returns:
{ "mode": "color", "code": 1000 }In essence, it seems like POST mode can now set the color (when switching to/in color mode) and movie/effect in one go, rather than separate calls. Interestingly, 'white' is included in the color_config, despite the string being RGB only.
GET similarly returns:
{ "mode": "movie", "detect_mode":0, "shop_mode": 0, "id": 10, "unique id": "[UUID]", "name": "Fireworks", "code": 1000 }