@gregl I have used this procedure a few times:
Define for example a V_VAR1 message for the query (or use any other suitable message type depending on purpose),
Make a MQTT binding for this message i Openhab (for example bind it to a switch, a number or whatever fits the purpose)
Make a rule in Openhab that reacts on this incoming message ("When Item xxxxx received update then ......)
Fix whatever logic is needed in this rule so you can send the queried info back to the sensor. If no existing binding is suitable you can of course define a V_VAR2 message (or use other type which fits) for the return message.
In the "Incomingmessage" function use whatever logic is needed to decode the returned message.
Reason for choosing a custom type of message (like a V_VAR2) for sending the info back is of course that it is easy to sort it out from the stream entering the incoming messages function. If you have no other incoming messages or the logic for the queried info already is in place then you do not have to think about this.
Hope the explanation is understandable, if not please revert.
Hi @blackchart,
Unfortunately, all devices are sold out. Further production is possible only when ordering more than 10 devices (in this case, I also can modify the device to suit your needs).
High sensitivity: down to -148 dBm.
From the datasheet. There probably needs to be some margin, but my experience with Sigfox shows that -130 is quite reliable. After that, packets start go missing. I would guess LoRa is similar.
I modified MyConfig.h file and RFM69 driver to allow you build gateway (ethernet or MQTT) with W5100 ethernet and RFM69 radio modules using SoftSPI bus. You can find it at: https://github.com/gieemek/RFM69_softSPI-for-MySensors-2.1.1
@sebdetours said in MDMSPanel "Nextion":
Did you take a standart case that you cut out?
Hi @sebdetours, yes. This is G1910 (Gainta) box. See drawing attached to projet files.
