@legeantvert said:
On the same way, i dont understand how and where are stored the values inside the gateway if not used on each reception, are they stored somewhere to be able to answer them when serial request arrive?
You could bypass this on some kind of events obviously !
Actually my perl gateway is acting as the server Vera is for the arduino gateway. So from there I can trigger external URL, store data in a sqlite3 database... and so on !
@Boots33
Thanks a lot for the quick response.
I now have my Nano running as a serial gateway and it is connected via a USB cable directly to my controller (Raspberry Pi 4 running Home Assistant / Hass.io).
I added a local motion sensor to the Nano gateway HW and pasted the mysensors MotionSensor example code to the setup(), presentation() and loop() functions as well as to the definitions in the top of the GatewaySerial example code.
I disabled the radio definitions as I currently have no radio capability in my gateway (not sure if this was necessary).
In Home Assistant / Hass.io I updated the configuration.yaml with the following text (as described on the Home Assistant integration help):
mysensors:
gateways:
- device: '/dev/ttyUSB0'
And it works
In Home Assistant Developer Tools under States I can now see my motion sensor go on and off by the flick of my hand.
I had expected a bit more bumps on the road just to get this far, but wow - I am obviously walking in the foot prints of people who have worked hard to make it easy for the rest of us.
I am sure I will hit bumps on the way when the radios have to send results to the gateway (thick concrete walls with lots of steel), but for now I will enjoy this big success.
Thanks again Boots33
Hi,
for everyone who reads all of this, forget about the last few posts.
I don't know why it works even when the Interrups are masked out on the radio, but it works now.
The error I had occured because of the config of the OrangePi-Gateway.
I removed:
--extra-cxxflags="-DMY_RF24_DATARATE=\(RF24_250KBPS\) -DMY_RF24_BASE_RADIO_ID=\(0x00,0xFC,0xE1,0xA8,0xA8\) -DMY_DEBUG_VERBOSE_RF24"
and wrote:
--extra-cxxflags="-DMY_RF24_DATARATE=\(RF24_250KBPS\) -DMY_DEBUG_VERBOSE_RF24"
Now I think I have an working OrangePi-Gateway without signing but with interrupt enabled.
If there are new problems I will come back here.
The next step for me is to activate signing again and bring the node into homeassistant.
@tsunami My setup is max 50m radius and 433MHz standard power RFM69s so a small 1/4 wave whip works reliably even from a below ground pump chamber 10m away.
Your 915MHz at 200m SHOULD work on 1/4 wave if obstacle free line of sight, but you could try a 2.4GHz Wifi router at one location and use a mobile at the other to test if you can see the router. I can see at least 3 neighbouring routers identified on my mobile from over 40m away through masonry, 10 on the laptop, so it's a simple enough test.
If you can see the router on either, 915MHz should be rock solid with a simple whip and no need of directional antenna.
