My inspiration for this project came from this topic:
My needs were different than what was shown in that topic, and after getting inspiration and guidance from @iEnam , Claude and I embarked on a journey to explore this Vibe-Coding thing. This was my first VC attempt. Lots of trial and error and testing, etc. You know the drill.
EDIT: I have removed the rest of this post, as it is mostly wrong!
Description from my new best friend, Claude:
SenseCAP Indicator Motion Display connects up to 9 Hubitat motion sensors to a SenseCAP Indicator touchscreen running openHASP firmware. Each sensor gets its own colored tile on the screen — red when motion is detected, fading to black then snapping to green when clear. The backlight turns on with motion and turns off automatically when all sensors are clear, with configurable timeouts. Supports 2×2 (4 sensor) and 3×3 (9 sensor) layouts.
Are you using MQTT bridge with OpenHASP?
Edited: didn’t read the other part, looks like it is.
I’m interested in checking out that custom ultrasmart.pl firmware linked when it’s available, but not sure how flexible it will be in terms of UI, because I’d like the main page to have the time taking up the top portion, then the bottom two squares for two devices I want to monitor the most.
Using MQTT seemed like the easiest approach but looked at Maker API as well.
I’m interested in what you have, I have 2 D1 and a D1Pro. Ultrasmart.pl said their custom firmware won’t support the D1Pro (yet at least), so some functionality is lost flashing with that.
Do you plan on putting your implementation up on GitHub/GitLab?
I’ll probably try out ultrasmart.pl’s custom firmware, but something opensource and flexible to modification could really push the use cases of these cool devices.
I have quite a few 2 inch screen Sonoff and ThirdReality Temp/Humidity sensors I’d like to replace with these.
Do be aware that it appears that the temperature and humidity sensing capability of this device is accomplished by plugging in a small external circuit board, so the wife approval response (“war”) factor may need to be taken into account.
Yep, the D1Pro comes with a Grove AHT20 sensor, I have some cheaper
Grove T/H sensors from some other projects, but I haven’t tried them on the D1 yet.
My wife is pretty liberal with my tinkering as long as I don’t create an eyesore.
The D1 takes up about double the space as the Sonoff and ThirdReality sensors with screens, but for spots like my office desk and nightstand I shouldn’t get much fuss, other spots my be a bit tricky.
I just told Claude - published to github. we done good, claude
He responded with
We really did! It's a solid piece of work — started as a simple 4-tile motion display and grew into a full-featured integration with dynamic grid layouts, smooth fade transitions, smart backlight control, MQTT resilience, and clean separation between the app, driver, and display layout.
Congrats on the publish — hopefully the Hubitat community finds it useful!
New version and license. Added ability to choose the logging level (info or info & debug or turn off.)
If there is motion and it has triggered long enough to cause the backlight to turn off, then while there is still active motion, the backlight will briefly come on showing the still current motion.
If there is motion and it has triggered long enough to cause the backlight to turn off, then when the motion stops, the backlight will briefly come on showing all motion is stopped.
These delays are configurable within the driver, as is the logging level.
I'm just starting out on this adventure. I can PM them to you if you want.