Does this require an update on the devices running the Samsung app? I can’t see a change in my WebCoRE (no split into two pages, still says something went wrong). It shows “Cast Iron v0.3.10a.20190223”.
Available Devices not working
ady624
#24
You need an update in the IDE for the app. Make sure you also publish. I simply moved the other types into a different page - that may still fail but at least you have a way to use the actuators and sensors which should be all devices, if their DTH is written correctly.
The version is v0.3.10b.20190514
Ganman
#25
Still having the same issue unfortunately and using the version you mentioned v0.3.10b.20190514
I have removed the 4 groovy in the IDE and re-installed from the repo but same result.
Note this whole process did work for me the very first time I tried to install and I only removed to start over because I could not get back into where a new device needs to be added in the Classic app.
Loved what webcore was doing before and would love to get it back!
jezzaaaa
#27
Thanks. I updated in the IDE and it’s allowing me to select by type.
Strangely,
the version showing in my app is still v0.3.10a.20190223. But it’s certainly behaving as you’ve described - separate sub-page for “select devices by capability”, which times out but is not necessary.
Thanks for all your work on this stuff. WebCoRE is seriously what makes SmartThings shine, and is what wows friends and family enough to consider joining the smart home revolution.
Ganman
#28
All goes well installing from the IDE and updating from the repo.
The issue seems to be inside the Classic app where I firstly see the below which looks correct.
Onto installing Webcore and I see the below after entering password etc.
I get the spinning wheel for a while then the error up the top.
I had previously installed fine and only removed webcore because I would get the spinning wheel when trying to add a new sensor.
Maybe I uninstalled incorrectly and there is something left from the uninstall preventing a new install as I had no issues first time around??
Snapshot from my IDE below
Thanks
Andy
Ganman
#31
@ady624 wondering if you have any update? I’m really at a loss and about to reset my hub and start all over but worries I’ll be in the same position.
ady624
#32
Sorry, just realized the initial setup is done in a different app and I have to update that to split the faulting page out of it. Will update today, sorry for the issues.
ady624
#33
@Ganman can you please update to v0.3.10c and try again? Thank you
webCORE Dashboard Completely Broken. Please Help [UndeclaredThrowableException]
eibyer
#34
Ady, since changing the device values to NaN didn’t really help much in the device loading, can we get that back? ocd is begging 
jkp
#35
FYI, @Ganman issue is with installing webcore on AP02 and not about this thread’s topic of available devices.
ady624
#36
Yeah, it was brought to my attention about the setup issue from within ST. So I fixed that too. I initially fixed just the page (which normally resides in the storage app). The setup uses the webCoRE parent app, so I fixed that too today.
Ganman
#37
@ady624 thank you so much! Working fine now and sorry if I confused the thread with my description of the issue.
mr_fy
#38
Hi,
I updated my webCoRE in IDE the other day to 0.3.10e and started to have problems.
Some devices that used to be visible are no longer visible and some new ones I have are not visible,
Looks like it might have been this change to break devices up onto two pages for timeout issues in APJ and I’m in Australia. But I never saw any timeout issues previously.
On the first page under Sensors or Actuators I don’t see the device.
The only other option is ‘Devices by Category’ which doesn’t work, just get ‘Something’s Wrong’ in Android and Network Error in IOS.
I’ve tried to roll back to previous version 0.3.10a with a manual install but get ‘Sorry, there was an unexpected error’ when installing the smartapp in SmartThings Classic App.
Edit: Actually with versions a & b I cant install into SmartThings, just get ‘Sorry, there was an unexpected error’.
Versions c,d & e, only able to add devices by sensor or actuator. Selecting ‘by capability’ fails with ‘Something’s Wrong’.
So am missing a few devices.
Any help?
Cheers,
mr_fy
#39
@jkp
Is there any more info on this not working on AP02?
I guess we need to speak to SmartThings then but what do we need to ask them?
Cheers,
Max_Lin
#40
Thanks for leading me here. Me too in Singapore having this same issue as well. Updated to the latest version too.
mr_fy
#42
@ady624
Hi, since the upgrade I am missing some devices and not able to add some new ones.
I cant pinpoint the exact time this occurred because hadn’t logged in for a few weeks but saw the upgrade available in IDE and installed it.
We see now that the devices page is split into two as you advised for your update. We can put devices into Actuators and Sensors and this all works fine. But I also have many devices under other sections which are no longer available.
When we press the third option for ‘Devices by Category’, it fails with ‘Something’s Wrong’ (In Android. In IOS get nothing just fails back to previous page).
So we cant get to the second page to add in the additional devices in the other sections.
I understand that this may be a problem with the AP02 server for Asia Pacific. I reached out to SmartThings to open a support case but got back that this is a 3rd party product that they dont support and see webCoRE instead.
I tried to roll back to 0.3.10a and b but they wont install into the SmartThings Classic App. in c,d,e we cant get to the second page of devices,
Pistons still work fine for the devices that are available through Actuators and Sensors.
For one of my devices which was a TP-Link HS100 wall power plug, I just updated the DTH and added in ‘capability: actuator’, and can now select it. But doesn’t help for the other devices.
Cheers,