For the Aeotec devices you can try the Aeotec channel drivers. The drivers offer more settings than some of the stock drivers.
Now that SmartThings has released its own IDE replacement here (SmartThings Advanced Web App), my API Browser+ app is largely redundant with that. However some of you may continue to find it useful for some things not yet supported by the SmartThings app.
So just for awareness, I wonât be shutting this down until I see usage drop to minimal levels, which I expect to see in the coming weeks. Iâll post here when that happens so no one is taken by surprise.
Thanks to everyone for your interest, feedback, and support!
10 Likes
One of the major benefit of your API Browser+ app is that I donât need to log into SmartThings every time I want to check device/rule info. A PTA is all that is needed and it sticks with the web page so itâs very convince to access the device/rule information.
If you ever decide to shut down the web page, please provide the web page code so we can access the web page it locally
3 Likes
Another benefit is that the API Browser+ includes Routines as well as Scenes!
5 Likes
And Rules also! I publish and handle my rules directly, and exclusively, here.
Hope I can continue with thatâŚ
1 Like
Until managing and viewing details on Routines and Rules is included in the SmartThings Advanced Web App, your API Browser+ will remain my go-to IDE replacement. Please donât abandon us too soon. 
7 Likes
Thank you for this app/service. You not only provided a bridge after the IDE was abandoned but surely gave the SmartThings folks a good prototype that they can model in their app. I agree with other comments that your coverage of Rules/Automations is critical and please donât shut down until the Smartthings Advanced Web App is complete.
5 Likes
@rambo350z @art_333 @Johnnybegoode @bthrock @harobinson
No worries guys! As long as there are folks that still want to use it, Iâll keep it available.
15 Likes
I notice an anomaly, but perhaps this is not the right place to mention it:
At home we only have two geolocated users, me with Pixel 7 Pro, my wife with Oneplus.
-
On Browser+ I see only one Pixel and one Oneplus correctly.
device for type: MOBILE -
From IDE same situation
-
in https://my.smartthings.com/advanced i see one Oneplus but two different Pixel 7 Pro.
I tried to cancel the first one, and from the app the automations related to geolocation got disconnected because they no longer had that phone available. If I reselected my Pixel 7 Pro from the app, the second device was created again. What could this anomaly be due to?
When you are using presence sensing on your phone there will be a mobile presence device created for each Location that you enabled it for. Those are the ones you are used to seeing. However these devices actually have a parent device that isnât in a Location, and this device represents your phone/tablet itself. I call it a âmobile as a thingâ device because of the presentation it uses.
You can only see a âmobile as a thingâ device if you are the owner of it, and it only appears in device listings that specifically ask to be able to see âUser Devicesâ, which the Advanced Web App does. So that is why you only see your phone and not your wifeâs, and why you only see it on the Advanced Web App.
If you delete a device in SmartThings its children will also be deleted. Just as your hubs are the parents of all your Zigbee, Z-Wave and LAN devices, your âmobile as a thingâ phone device is the parent of the mobile presence devices. So that is why they disappeared.
As I have an app that I use for cross-referencing API objects I encountered these âmobile as a thingâ devices a small number of years ago. However it was only when I saw them appearing in the Advanced Web App that I uncovered how they could be displayed in listings. So the confusion is understandable.
5 Likes
Thanks, exemplary explanation
I may have found a good reason to keep API Browser+ around, I canât get device information on my mobile. Tried a couple of different browsers and while devices and hubs get listed, clicking on them doesnât show the device or hub details panel.
1 Like
Feature request: âList unused driversâ (perhaps under hubs/installed drivers)
3 Likes
You can tell if a driver is used or not by going to Location->Hubs->âYour Hubâ->Installed Drivers->âYour Driverâ>List Devices. If no devices are listed, the driver is not in use.
@h0ckeysk8er provides an alternative, but I will still consider this function. I can appreciate the usefulness of getting a quick listing of âorphanâ drivers.
3 Likes
Good to know. But it is time consuming and it would be nice to have an automated method. In my case, I found I had some 30 drivers, with 3 orphans in the bunch.
1 Like
Is this also why I see on the main page of Advanced Web App it says âYou have 45 devices registered in 2 locations and 1 device without a locationâ. The device without location being the âmobile as a thing deviceâ?
I also deleted that device (before I had read this post) and lost my phone in both my locations, but luckily I noticed in the ST app settings that I just had to turn back on the âget your location from this phoneâ for both locations and the 3 instances of my phone reappeared. I also had to put back the phone into the routines I have that use the presence sensor to turn on & off the virtual device I have that represents my phone in each location.
Yes, thatâs right. So far, those are the only devices Iâve found outside of Locations but there gould well be others.
New Feature Alert!
Version 230806 is now live, which adds a new feature to the Locations â Hubs â Installed Drivers menu item: there is a new button at the top of the installed driver list to highlight any installed drivers that have no devices assigned - in other words, unused drivers. Any such drivers will be displayed with red text in the driver list.
Please note this feature is meaningful only for Edge drivers (zwave, zigbee, LAN, Matter). If you still have any DTH drivers installed (if thatâs even possible anymore!) with no devices, they will not be highlighted.
Please report any issues you have.
Thank you to @georgeh for requesting this useful feature.
14 Likes
Thanks. A good add.
1 Like