With the transition to the new architecture, the IDE is in the process of being discontinued. Some features are already gone. Any device using new architecture, such as those using edge drivers, will just show up as “placeholder“ and the information will be incomplete or even inaccurate. (For example, it will probably say that all devices showing “placeholder“ are in the cloud, where in fact all edge drivers run local.)
Don’t try to use the IDE to change anything that says placeholder: you might even break the integration altogether.
At first that page was pretty limited, but as of 29 June 2023 Samsung has now added a number of new “advanced” features to that page, making it much more like the old IDE. People who prefer to work with official features should check this first before looking into some of the community created information display options. Here’s the discussion thread on the new features:
So… how do you do the things that you used to do with the IDE now?
This topic is a place to post those questions and answers. A lot of people will have the same questions, and this should hopefully keep us from getting a bunch of duplicate threads. At the same time, people may have different tips and tricks and methods for getting the information now. So this is a good place to collect those together.
You can exclude the Z-Wave device using the App.
Click on your Hub tile, then in a menu (three dots) select Settings and then Z-Wave utilities → Z-Wave exclusion.
TBH I even didn’t know it was also possible in IDE
How can I create virtual devices to trigger Alexa routines without the IDE?
Answer: as long as you have a smartthings/Aeotec hub, you can use the following custom edge driver. (If you have any further questions about this edge driver, ask in that thread.)
We are still waiting to hear on an official method for those who don’t have a hub. So far the primary workaround is to create a virtual lock using TAustin’s webpage project, since locks can trigger an Alexa routine.
Heh, I also use XBee to find all the routes The question why it’s not catched by the zigbee-thing driver is on my long list of questions I have not yet asked on the forum. Probably it’s missed because it does not use ZigBee HA profile.
In the IDE, there is an entry for the hub’s Zigbee radio and one for the hub’s zwave radio that tells you if each is active. This is handy as a troubleshooting step when, say, all Zigbee devices go offline at once.
Is there a way to get this information once the IDE is gone?
a) You can temporarily assign the device to one of the utility drivers that displays it, then assign it back to the regular driver. Mariano’s zwave thing for zwave devices or Zigbee thing for Zigbee devices will both do this. You should be able to find both in his channel which is linked at the end of the first post in the following thread.
Just in time (I read it won’t be possible after today), yesterday I used the IDE to change my hub zigbee channel to 15. I needed to modify as my Eero router does not allow me to modify the wifi channel. In the ST app on an android tablet I noticed today that it has automatically modified my future Thread network channel to 15.