Default Channels on Things [message #1728828] |
Thu, 07 April 2016 17:07 |
Karel Goderis Messages: 198 Registered: March 2014 |
Senior Member |
|
|
The PaperUI is capable of showing the exact status of a Thing, e.g. ONLINE,..., but the PaperUI is primarily for configuration purposes, not for really operating an ESH/OH environment that is configured through Sitemaps.
It would be beneficial to expose the state of a Thing as a Channel of that Thing, so that the state of the Thing can be displayed in other UI's or be exposed to the userspace (e.g. Rules). For example, have an indication that a hub or bridge for a certain technology is up and running, so that in case of a problem, that problem can be flagged to the user, and diagnosed consequently
We could imagine defining a set of Channels, with fixed names, that are available and enabled by default on any Thing, and that can be linked to Items and so forth
Any thoughts on this?
|
|
|
|
|
Re: Default Channels on Things [message #1729013 is a reply to message #1728996] |
Sat, 09 April 2016 12:55 |
Karel Goderis Messages: 198 Registered: March 2014 |
Senior Member |
|
|
@kai Just to prevent any (future) confusion, is there any work ongoing at your side in terms of bringing the automation stuff to the userland/rule-engine? FYI, I have a branch in the working (depends on the new scheduler infrastructure, hence the reason why I have not created the PR) that effectively migrates the Rule & Script infrastructure to use the Automation bundles. That way, only one type of underlying automation framework is used. I have not progressed as I need the scheduler, but I sense that maybe it is now a bit behind the most current Automation updates. You might want to have a look at https://github.com/kgoderis/smarthome/commits/scheduler-migration/bundles on how I did it, and provide feedback in terms of advancing it, holding it and so forth. Or integrate it in what is going on at your side. There are also a few PR of Johann that are pending in the same area, and which this stuff could be integrated with. Note that some of the commits are not good as the Scheduler infrastructure has changed in the meantime, the rest should, I hope, still be relevant
|
|
|
|
Powered by
FUDForum. Page generated in 0.03694 seconds