I have a couple of radio controlled sensors and actors which are simply accessible via a different gateway on my Linux machine. I now would like to use LinKNX as a gateway between these systems:
1)
One of the radio controlled switches is triggered, so I want to write to a specific group address on the bus. This looks quite easy, as I would just need to use the groupswrite outside of LinKNX,…BUT….I also want to have a physical address inside the EIB for this switch, so that I know the status of it.
2)
Switching radio controlled actors via LinKNX: I want to define virtual actors which it's own physical address and I would like LinKNX to serve the virtual part for it. If a switch signal is received for this device, I would like to call a script which will then actually send the radio-controlled command to switch the actor.
Any ideas how to implement this?
Additionally I would like to include timer configurations to include these radio controlled switches. Like the one for the lamps outside of my house which are not connected to the EIB.
Thanks for your help…
Netsrac
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I guess using linknx is not a 100% fitting solution - but I was hoping, that Jean-Francois is picking this ideas up. (But since his reply-speed has reduced in the last year, I guess he is recently very busy with other tasks. Same for me… that's why I haven't followed up on this on my own…)
I think similar like you, that this "virtual device" functionality is somehow "overlapping" with LINKNX, because some technical interfaces are already implemented in linknx, I could imagine some "modul" in linknx OR some spinoff from Linknx…
What is similar:
1) bus access (via eibd), but this has to be extended with a "read" option
2) XML-parser
What needs to be done new:
3) The XML would need to be extended to allow "device" definitions with some attributes…and to support the "reading" of persistent values.
4) some programming language needs to be included to write the "logic". The Programming language interface needs to support timers and callbacks (timeouts). maybe this can be done with the (existing LUA) interface.
I don't believe that it will be possible to have an own "device adress" on the bus, since this is limited by the bcusdk. (and probably by the bus coupling device or router in the backend.)
@Jeff, are you somehow interested to follow up on this?
(maybe if we find more potential users of this?)
Thanks, Best Regards, Jens
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maybe all you need is "listening" for a group address to be called and send a reply to the BUS. Shouldn't this be possible with the current version of LinKNX?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1) One of the radio controlled switches is triggered, so I want to write to a specific group address on the bus. This looks quite easy, as I would just need to use the groupswrite outside of LinKNX,…BUT….I also want to have a physical address inside the EIB for this switch, so that I know the status of it. 2) Switching radio controlled actors via LinKNX: I want to define virtual actors which it's own physical address and I would like LinKNX to serve the virtual part for it. If a switch signal is received for this device, I would like to call a script which will then actually send the radio-controlled command to switch the actor.
So you have radio push buttons (I don't like the word switch because it's sometimes confusing because it's also used to speak about actuators) and radio actuators.
And the software can receive the commands sent by push button. Right?
What do you receive from push button? just a message saying that the button was pushed, or do you receive alternatively "on" and "off" messages.
Is the actuator also able to send its state, or does it just receive commands?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have a couple of radio controlled sensors and actors which are simply accessible via a different gateway on my Linux machine. I now would like to use LinKNX as a gateway between these systems:
1)
One of the radio controlled switches is triggered, so I want to write to a specific group address on the bus. This looks quite easy, as I would just need to use the groupswrite outside of LinKNX,…BUT….I also want to have a physical address inside the EIB for this switch, so that I know the status of it.
2)
Switching radio controlled actors via LinKNX: I want to define virtual actors which it's own physical address and I would like LinKNX to serve the virtual part for it. If a switch signal is received for this device, I would like to call a script which will then actually send the radio-controlled command to switch the actor.
Any ideas how to implement this?
Additionally I would like to include timer configurations to include these radio controlled switches. Like the one for the lamps outside of my house which are not connected to the EIB.
Thanks for your help…
Netsrac
Hi Netsrac, seams we are 2 of a kind:
https://sourceforge.net/projects/linknx/forums/forum/743669/topic/3730537
What do you use to control your radio devices? FHEM?
I guess using linknx is not a 100% fitting solution - but I was hoping, that Jean-Francois is picking this ideas up. (But since his reply-speed has reduced in the last year, I guess he is recently very busy with other tasks. Same for me… that's why I haven't followed up on this on my own…)
I think similar like you, that this "virtual device" functionality is somehow "overlapping" with LINKNX, because some technical interfaces are already implemented in linknx, I could imagine some "modul" in linknx OR some spinoff from Linknx…
What is similar:
1) bus access (via eibd), but this has to be extended with a "read" option
2) XML-parser
What needs to be done new:
3) The XML would need to be extended to allow "device" definitions with some attributes…and to support the "reading" of persistent values.
4) some programming language needs to be included to write the "logic". The Programming language interface needs to support timers and callbacks (timeouts). maybe this can be done with the (existing LUA) interface.
I don't believe that it will be possible to have an own "device adress" on the bus, since this is limited by the bcusdk. (and probably by the bus coupling device or router in the backend.)
@Jeff, are you somehow interested to follow up on this?
(maybe if we find more potential users of this?)
Thanks, Best Regards, Jens
Maybe all you need is "listening" for a group address to be called and send a reply to the BUS. Shouldn't this be possible with the current version of LinKNX?
So you have radio push buttons (I don't like the word switch because it's sometimes confusing because it's also used to speak about actuators) and radio actuators.
And the software can receive the commands sent by push button. Right?
What do you receive from push button? just a message saying that the button was pushed, or do you receive alternatively "on" and "off" messages.
Is the actuator also able to send its state, or does it just receive commands?