How to import ST_Anything into webCoRE

#1

1) Give a description of the problem
I can’t figure out how to import an ST_Anything button into webCoRE.
Thanks to the detailed ReadMe in the ST_Anything github repository I have successfully loaded ST_Anything into ST IDE and modified and loaded a simple sketch with one button and one TimedRelay onto my 8266 ESP_01. I see the relay as a child device in the ST app and in the webCoRE Available Device list. When I create a Routine in ST I find the button as an option and am able to use it to turn on a lamp.

2) What is the expected behaviour?
See ST_Anything button in list of Available Devices under webCoRE SmartApps settings.

3) What is happening/not happening?
button devices aren’t visible

**4) Post a Green Snapshot of the piston![image|45x37]
n/a—No piston - can’t get device loaded.

5) Attach logs after turning logging level to Full
n/a Can’t get this far…

#2

Common question, but I have to ask…

Did you check in the other categories??
(below actuators and sensors, there are about 50 other categories further down)

I am referring to:
Phone > ST Classic App > Automation > SmartApps > webCoRE > Settings > Available devices > Available devices > Scroll

#3

Thank you WCmore. Sorry I’ve never had to look beyond the Actuators and Sensors. I found my two 8266 device names in the list by category and was able to add them. However, on one of my ESP-01s (named ACE) I configured both I/O ports as buttons (button1 & button2). In the device list I only have ACE, no way to select the individual buttons. Within ST Classic App the button number is selectable after I pick ACE as the actuator for a Routine. Any thoughts?

Thanks

#4

@dduisenb, try selecting the ACE. Then, create a piston with it. Create IF > CONDITION > PHYSICAL DEVICE (ACE) and then look under Nothing Selected. Your 2 switches may show up there.

#5

Found it. After creating the Routine in ST Classic I went back to webCoRE and now see a field for selecting button number after picking ACE. Have to go do some wiring to test, but all looks as I would expect now.

Thanks for the help.