Hello,
I have devices flashed with Tasmota.
For simple devices, no problem.
For power strips, I have a problem with some scenes.
When my scene asks to activate the device, it offers me the power strip and not each socket of this power strip independently.
When I choose the power strip, it turns on or off the first socket of the power strip.
Is it me who can’t do what I want or is there a small bug here?
Thanks for your feedback
Benoit
Hello @Bencoene 
I assume you are using the « turn on sockets » action from the scenes. This action is not designed for power strips but for single sockets.
I recommend using the « control a device » action, where you can select the correct socket
Hello,
Thank you for your feedback, I will test it 
Hello,
With this method, it works very well
I hadn’t seen the « control a device »
Could you tell me when to use one over the other in your opinion so that I can better understand the principle, as I don’t understand why there are two well these two options please?
Thank you
The « turn on outlets » action is a bit of a very practical « shortcut » to easily turn on many outlets in one action, but only works with individual outlets (we might add a message)
The « control a device » action works at the « feature » level of a device, and allows fine control of a single feature of any type (In Gladys, the data model is as follows: you have a « device » that has several « device_features ». Example: « Living room lamp » has 3 features: binary on/off + color + brightness)
Thanks a lot for your feedback by the way, if you have other feedback / questions, things you miss compared to Domoticz, don’t hesitate
Thanks for your feedback,
Well, here are my first impressions of Gladys after 2 days of use.
I just tested Gladys thanks to your YouTube videos and especially the NodeRed video, so I confirm that your videos are useful for recruiting new users like me 
My equipment:
RFXCOM / Switch / Relay / 433MHz plug
Sonoff equipment (RF, TH, POW, 4CH, DUAL) and other plugs / multi-socket flashed with Tasmota
Magic Home LED strip not flashed
Sony Bravia TV (recovery of status to turn on other equipment)
Freebox Revolution (not yet home automated)
Zigbee CC2531 key flashed for Zigbee2MQTT
4 Aquara Zigbee immersion detection boxes
I have an RFXCOM that doesn’t work natively on Gladys and I have several 433MHz devices that I really need (okay, want is better than need 
, home automation is never a need)
Several Sonoff or other plugs flashed with Tasmota and that works pretty well (except for the power strips with the disadvantage explained above)
4 Zigbee boxes in Zigbee2MQTT that work very well in Gladys.
There is also the test if the TV is on or off. I worked on this point. I didn’t find directly in Gladys how to query an API.
Last night I did it via nodered/mqtt and the management in gladys works very well now that you have answered another question to turn on the amp and the subwoofer.
I have a frameless frame controlled via a magic home module that was controlled by domoticz with no problem, for the moment, I haven’t found how to do it in gladys yet but I haven’t looked into it much yet.
I don’t have heating management yet. I’m thinking about it but I haven’t looked into what is compatible with my boiler yet (I want a bus contact and not a dry contact. If you have any leads on this, I’m interested )
Finally, I have a Bluetooth LED strip that I couldn’t control with domoticz. Once everything is functional, I will look into how to do it with gladys if it’s feasible.
If you want me to test some of my equipment, I can do it to help the project move forward.
Good evening
Great
You can call an API in the scenes by making an HTTP request, and retrieve the API response in the messages / or a box continue only if Otherwise, it is also possible to do this in Node-RED and then send the information to Gladys via MQTT.
From what I see, your feedback is more about compatibility, rather than the features of Gladys itself (except for the multi-outlets). All the better, this means that at least the basic building blocks and the general philosophy of Gladys suit you!
On this point, it’s more on a case-by-case basis for each integration development. Do not hesitate to follow the developments on the forum, and to offer to do tests
I have a Freebox Delta, and I’ve been trying for some time to control it and/or retrieve its state via scenes but I’m stuck on authentication…
I don’t receive the expected responses but incomprehensible strings of characters made up of �
whereas it’s supposed to return something like this :
{
"success": true,
"result": {
"app_token": "dyNYgfK0Ya6FWGqq83sBHa7TwzWo+pg4fDFUJHShcjVYzTfaRrZzm93p7OTAfH/0",
"track_id": 42
}
}
unable to retrieve the app_token and the track_id, essential for the rest 
source: Login — FreeboxOS Gateway api 9ba63963 documentation