I must have misunderstood or more likely miss remembered. I wish I could find the thread, it was actually a pretty good one.
I’ll start being a nuisance then.
It’s kind of minor, but I’ve dealt with several users who, for example, keep trying to toggle the Switches from the Network binding and are confused when nothing happens.
There are three approaches to solve this problem documented in Design Pattern: Manual Trigger Detection.
Either I’m misunderstanding or there already is. events.log only has Item and Thing state changes.
I think this would need to be implemented on the Zwave binding and exposed as a Channel.
I believe there is already an issue open for this on the Android app repo. It has been much requested but you are correct, it isn’t really part of the core framework.
See Show Remaining Time of a Timer - #2 by rlkoshak for a way to do this in Rules.
It’s the details that I’m looking for. When ever I try to do anything more than logging from an PaperUI defined Rules I get ClassNotFoundExceptions. I’m mainly looking to know when there is enough there that it becomes a viable replacement for Rules DSL so we can start the documentation efforts.
Thank’s for the video link! Are there any others from the recent meet up in Germany? I must have missed the announcement if they were previously announced.
Perhaps it is worth pursuing making PaperUI a bit more mobile friendly and or making a PaperUI App. Personally I already find PaperUI to be quite mobile friendly but perhaps I’m missing some pain point. @ptmuldoon, what is it about the web browser interface that causes problems for you? On Android at least, you can even “Add to Home Screen” your PaperUI and it will have it’s own icon and pop-up like an app when you tap it.
I completely agree though, managing user permissions, and all the other tasks mentioned are administration tasks and do not belong in the openHAB Phone apps themselves.
We are already starting down that path a little bit. Archived Projects | The Eclipse Foundation
Note, one of the reasons that ESH was split out from OH was to give 3rd party vendors a basis to enable this sort of thing.