ST_Anything was created originally to be able to utilize my home’s prewiring for an alarm system. I use it to monitor 4 door contact sensors and a motion sensor, as well as control and monitor my two garage doors, and measure temperature/humidity. It’s been running for years. It’s really not “overkill” as that is the exact application we built it for. To use ST_Anything for your specific application, it only needs 5 lines of code in the example sketch, one for each sensor to be monitored.
Also, the DTH code now uses the Composite (Parent/Child) model, so no SmartApp required for multiplexing.
Cool, that’s great to know. When I looked at ST_Anything, I just thought it seemed like there were a lot more features than I needed for my modest project. Come to think of it, maybe I did end up using it, I was going back and forth so many times… Can’t find my Arduino code now, so I’ll never know…
I found your GitHub repos – lots of cool things, there, it seems.
When you say ‘SmartApp uses the Composite…’ you are referring to the new ST infrastructure, is that right? The multiplexer is my only deployed SmartApp, so if I don’t need to multiplex anymore, that’s a relief.
Unfortunately, no. ST_Anything still uses Classic DTHs for all communications between the Arduino and the ST Hub. Also, it is designed to primarily work with the Classic ST Mobile App.
The Composite Device Handler model was created by ST many years ago. It allows for the elimination of the Multiplexer SmartApp, as it implements a Parent/Child design. As updates are received from the Arduino, the Parent Device creates Child Devices as necessary. So, it greatly simplifies the overall design, and eliminates the need for users to have to create/maintain the old multiplexer SmartApp design that I originally used with ST_Anything.
