💬 Sensebender Gateway
-
This is on my most wanted purchase list now. :smile:
FYI, I noticed the spelling of "Sensebender" is "Sensbender" for this gateway on openhardware.io, so you're breaking your brand name. :wink: Would it be possible to amend it? If you try to search for it with the original spelling you only find the two sensor Sensebenders.
-
This is on my most wanted purchase list now. :smile:
FYI, I noticed the spelling of "Sensebender" is "Sensbender" for this gateway on openhardware.io, so you're breaking your brand name. :wink: Would it be possible to amend it? If you try to search for it with the original spelling you only find the two sensor Sensebenders.
-
Is this device capable of being a gateway for both nRF24L01+ radio and the Hope RF RFM69HCW radio simultaneously ?
I have some nRF24 nodes and see a lot of new goodies equiped with the RFM69 radio. One gateway to serve both would be excellent ! -
Is this device capable of being a gateway for both nRF24L01+ radio and the Hope RF RFM69HCW radio simultaneously ?
I have some nRF24 nodes and see a lot of new goodies equiped with the RFM69 radio. One gateway to serve both would be excellent !The hardware supports both NRF and RFM69 at the same time, they share the same SPI bus, but has separate chip select lines etc.
Unfortunately the MySensors library doesn't support multiple transports, so this time it's the software that limits things.
-
The hardware supports both NRF and RFM69 at the same time, they share the same SPI bus, but has separate chip select lines etc.
Unfortunately the MySensors library doesn't support multiple transports, so this time it's the software that limits things.
@tbowmo
The fact, that MySensors doesn't support more then one radio, was the reason for me not to order the sensebender gateway.I am working on a gateway⁄controller based on an arduino due, which supports at least up to 3 serial gateways via hardware serial. It handles ID and time (synced with ntp) requests and does pub/sub to mqtt with readable topics.(inspired by the old mqtt client gateway)
-
@tbowmo
The fact, that MySensors doesn't support more then one radio, was the reason for me not to order the sensebender gateway.I am working on a gateway⁄controller based on an arduino due, which supports at least up to 3 serial gateways via hardware serial. It handles ID and time (synced with ntp) requests and does pub/sub to mqtt with readable topics.(inspired by the old mqtt client gateway)
-
@FotoFieber this is a software limitation. Hardware wise I do not see why Sensebender GW cannot handle two (nrf24l01+ and rfm69/rfm95) GWs at the same time
@alexsh1
The question is: will the software restriction be solved? If not, I do not care if it is a software or a hardware restriction. :) -
Well, you need to hack the core anyways, if you want to accomplish your goal.
You could also help out with the core development, so we can get support for multiple transport on one gateway ;)
@tbowmo
No, I don't have to hack the core. I use the serial API. From an architectural point of view, I don't see the need to change anything in MySensors. A serial controller can be built for under 20€ Including the radio. Why should I add complexity to support more than one radio support with one cpu in MySensors, if I can have the functipnality with the abstraction layer of the serial API? Please keep MySensors s simple as possible. -
@tbowmo
No, I don't have to hack the core. I use the serial API. From an architectural point of view, I don't see the need to change anything in MySensors. A serial controller can be built for under 20€ Including the radio. Why should I add complexity to support more than one radio support with one cpu in MySensors, if I can have the functipnality with the abstraction layer of the serial API? Please keep MySensors s simple as possible.@FotoFieber simple for who? Simplicity also involve maintenance and code complexity. What about testability and regression testing? Nobody gets paid for maintaining mysensors.
-
@tbowmo
No, I don't have to hack the core. I use the serial API. From an architectural point of view, I don't see the need to change anything in MySensors. A serial controller can be built for under 20€ Including the radio. Why should I add complexity to support more than one radio support with one cpu in MySensors, if I can have the functipnality with the abstraction layer of the serial API? Please keep MySensors s simple as possible. -
But you ditched the sensebender Gateway, as it doesn't support multiple radios at the same time? Now you are saying that you would keep it as one radio per gateway?
This doesn't make sense :)
@tbowmo
Maybe the design of the sensebender gateway doesn't make sense to my architectural viewpoint.... -
@alexsh1
The question is: will the software restriction be solved? If not, I do not care if it is a software or a hardware restriction. :)@FotoFieber This is a question for the MySensors dev team. Sensebender can handle both radios. Currently, there is a software restriction.
-
@tbowmo
No, I don't have to hack the core. I use the serial API. From an architectural point of view, I don't see the need to change anything in MySensors. A serial controller can be built for under 20€ Including the radio. Why should I add complexity to support more than one radio support with one cpu in MySensors, if I can have the functipnality with the abstraction layer of the serial API? Please keep MySensors s simple as possible.@FotoFieber No, you do have to hack the core if you want both radios to be handled properly, i.e. to handle message queues with corresponding radios. For example, sending a message is done via rfm69 only and not via nrf24l01+
-
The architecture we use would place this kind of situation to the controller to solve. One gw per network. So one gw for nrf and one for rfm.
HW is cheap, and library should be kept simple.Do you feel secure today? No? Start requiring some signatures and feel better tomorrow ;)
