@idanronen said in Wireless remote door lock - HW choices:

Hacking - Like i said, it will be operated from home assistant, and I'm not worried about that being hacked. The device can be hacked directly by someone sending random messages with a compatible NRF24 or other device somewhere nearby. I'm not really sure how to handle that one, as this sort of communication is broadcast and a verified message would have to change content every time to be secure, sort of like a rolling code.

So . .. . above, I said that ProMini with batteries was the simplest, but you may want to move to a 32 bit controller for this one.
MySensors provides a security framework to address the hacking aspect above. Using signing on a complicated node, I started running out of memory on the ProMini. I have moved to the NRF5 series, mostly to get more memory. There is a lot of additional features and power also, but it is a harder learning curve to get the tool chain working.

It can be done in the MySensors framework, but I am not sure I would call it simple. See this thread:

https://forum.mysensors.org/topic/1085/node-to-node-communication

I used node-node communication once to reduce latency on a button press, but as @mfalkvidd states, this is not the norm for MySensors. After more fiddling, I determined I did not actually need the node-to-node to make my application work.

MySensors smartsleep would be a good way to implement your receive/sleep code. It handles any waiting messages when the node wakes up and before it goes to sleep. Look it up in the API page.

Some thoughts on your other questions. Others may have better answers than me:

Your simplest node would be a 3v3 pro-mini running on 2AA batteries. Check out the low power node discussions on the MySensors web site. This would be the most straight forward if your motor supports it. A 5V pro mini with an NRF24 is also a straight forward option if you have more than 5v available (but consumes more power). The trade off on power source and complexity is a real one, and depends a lot on what you are trying to do. There are lots of discussions in the forums about how to handle mixed 3v3 and 5v components and lithium vs alkaline batteries -- a very common problem.

RFM69 will normally give you better range than NRF24, also at very low power. But they cost a little bit more and are not 5V tolerant. The NRF24 is easier to make work with a 5V pro-mini or nano since only the power needs to be dropped to 3.3v. Again, lots of discussion can be found in the forums. You need a gateway with a compatible radio, so there is a bit of commitment in your radio choice.

@neverdie said in Which are the preferred LoRa modules now?:

SX1262

Are these RFM95 compatible (software wise), or do they need a different library?

@zboblamont
Yeah .... I see the problem. I have several sensors that measure levels that I report as voltage, because I just want to send a float number, and S_Voltage handles that. A nice feature would be to be able to override the units display, but I haven't figured out how to do that.

You could set up an influxdb server and have domoticz send updates to it. I do that for some things that I want to track for more than a year. Then you can use grafana to set up graphs you like. Domoticz has a setting you can use to pick readings to send to influxdb.

@scalz said in ENC28J60 Ethernet gateway:

A while back, we checked w5100 module + arduino 328p. Eth module and radio were working on same hw spi bus but in docs it uses softspi, I don't remember why, perhaps for having a dedicated spibus for ethernet..

It may have been fixed by now, but originally the W5100 did not release the SPI bus properly. So, it needed a separate SPI bus from the radio.
I think this was fixed in the W5200 and W5500.

@jasxvii
Yes. Makes sense. I the code in the original article was from an earlier version of MySensors.

Hi. The MySensors site has a whole section on controllers with a matrix that compares the features:

https://www.mysensors.org/controller

Any of them should be able to control that outlet once set up.

You will also need a gateway to connect to the controller if you don't have one already. See this section: https://www.mysensors.org/build/select_gateway

Check the variable type you are sending with the humidity. The log parser indicates you are sending a V_TEMP for the humidity reading instead of a V_HUM

You can find the log parser here: https://www.mysensors.org/build/parser
Much easier than trying to read the log output directly.