Available Devices not working

jezzaaaa · 2019-05-12 13:31:36 UTC

Just tried it again, still not working for me in AU.

ady624 · 2019-05-14 19:45:43 UTC

I have made a change to break up the lists of devices onto two pages. Turns out building the list of capabilities takes too long in the Asia-Pacific region. This is due to a feature flag that we currently enabled. We are looking into ways to make things faster, until then, use the devices by type primarily - there is a big chance you still won’t be able to access the devices by capabilities but since that’s now in a different sub page, you should be able to at least use the by-type selectors.

Also, sorry it took me so long to fix this. And thanks to one ST employee who also uses webCoRE who found the “fix”.

jezzaaaa · 2019-05-14 23:26:27 UTC

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”.

ady624 · 2019-05-15 01:35:09 UTC

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 · 2019-05-15 11:11:19 UTC

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!

ady624 · 2019-05-15 18:23:31 UTC

What exactly does not work, could you please explain step by step?

Thank you

jezzaaaa · 2019-05-16 00:27:22 UTC

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 · 2019-05-16 10:54:07 UTC

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

R1CHY_RICH · 2019-05-16 23:15:32 UTC

Thank you, I can confirm after updating via git it’s all working for me again.

Ganman · 2019-05-18 03:02:15 UTC

Still not working for me…

Ganman · 2019-05-22 07:08:53 UTC

@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 · 2019-05-22 16:09:09 UTC

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 · 2019-05-22 16:29:52 UTC

@Ganman can you please update to v0.3.10c and try again? Thank you

eibyer · 2019-05-22 16:35:41 UTC

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 · 2019-05-22 16:50:05 UTC

FYI, @Ganman issue is with installing webcore on AP02 and not about this thread’s topic of available devices.

ady624 · 2019-05-22 19:22:57 UTC

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 · 2019-05-23 10:45:46 UTC

@ady624 thank you so much! Working fine now and sorry if I confused the thread with my description of the issue.

mr_fy · 2019-07-02 01:13:21 UTC

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 · 2019-07-02 02:20:49 UTC

@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 · 2019-07-02 04:04:23 UTC

Thanks for leading me here. Me too in Singapore having this same issue as well. Updated to the latest version too.