Hi
I think the split between linknx as the "application" and "knxweb" as the renderer and interface is a very good idea.
What do you think about extending linknx with something like "software devices"?
I haven't had the time to look into the code, so I cannot make suggestions how to implement it. I have the following (sample) use case:
I have two different types of blind control-actors at home. The more intelligent are centrally installed in the central power junction box. I can send them group-adresses (EIS6) for setting a value for closing the blinds to a certain degree as well an adress (EIS1) for a specific programmed "preset".
Internally they work with parameters, which are set with the ETS. In my case I just have to pre-define the time in the ETS, how long it takes to open / close the blinds. The actor then just works with the time internally...
There is also an EIS6, which can be read and gives me the current position.
But I have other, locally installed thumber blind-actors, which just have the commands for up-down/stop.
I want to have some "code" , where I can define (emulate) the processing of incoming messages and translate them into messages for the thumber hardware. This is probably hard to be done in xml, but probably more for a C-Framework. In my sample case I could programme a more intelligent "software blind actor", which can also use incomming EIS6 values and translate them into "up" / "down" commands for the thumber local actor, based on a predefined time-setting. ... this can be become quite complex...
(this is your "status feedback"-sample-advanced, since the software device should also be able to send the EIS6-position information as the intelegent actors do.)
Further software devices could be "datastore" (see below) and others.
All these device need to have an interface with knxweb to let knxweb render their status. For example, knxweb could show a graph for the <temperature> of the last <24 hours>, which are logged in such a "datastore"...
This is probably too much for just xml - but a class framework / placeholders would be a start for me.
Thanks in advance
Best Regards, Jens
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I think the split between linknx as the "application" and "knxweb" as the renderer and interface is a very good idea.
What do you think about extending linknx with something like "software devices"?
I haven't had the time to look into the code, so I cannot make suggestions how to implement it. I have the following (sample) use case:
I have two different types of blind control-actors at home. The more intelligent are centrally installed in the central power junction box. I can send them group-adresses (EIS6) for setting a value for closing the blinds to a certain degree as well an adress (EIS1) for a specific programmed "preset".
Internally they work with parameters, which are set with the ETS. In my case I just have to pre-define the time in the ETS, how long it takes to open / close the blinds. The actor then just works with the time internally...
There is also an EIS6, which can be read and gives me the current position.
But I have other, locally installed thumber blind-actors, which just have the commands for up-down/stop.
I want to have some "code" , where I can define (emulate) the processing of incoming messages and translate them into messages for the thumber hardware. This is probably hard to be done in xml, but probably more for a C-Framework. In my sample case I could programme a more intelligent "software blind actor", which can also use incomming EIS6 values and translate them into "up" / "down" commands for the thumber local actor, based on a predefined time-setting. ... this can be become quite complex...
(this is your "status feedback"-sample-advanced, since the software device should also be able to send the EIS6-position information as the intelegent actors do.)
Further software devices could be "datastore" (see below) and others.
All these device need to have an interface with knxweb to let knxweb render their status. For example, knxweb could show a graph for the <temperature> of the last <24 hours>, which are logged in such a "datastore"...
This is probably too much for just xml - but a class framework / placeholders would be a start for me.
Thanks in advance
Best Regards, Jens