I had to restart this night which was the first restart since months. Tonight the clocks were changed (Daylight Savings Time). I suspect that this was the reason. Apart from that it is absolutely stable.
Yes depending on the controller (Arduino) you choose will determine the number of sensors or actions a node may support. I will take into consideration if the node can be hidden, or it needs to be small and/or presentable where it is going to be located. This may effect your choices for the controller.
I will also look at the tasks I'm trying to accomplish for a given objective. Some tasks like knowing if a door or window is open or closed and a motion sensor may not play well with each other in a node.
Determine if it is going to be using batteries or get power from my house curcit (for example via a wall wart). When determining the power source I will look at the tasks I have defined. One of the tasks could determine if you are able to resonable use batteries to power it. For example a task like knowing if a door or window is open or closed most likely will not be run on batteries.
If using a battery you should put your controller and radio to sleep as long and often as you can. If you have to use a small controller then the number of interrupts available will be limited and most likely be one. Some tasks will use an interrupt to override the sleep timer, for example a motion sensor. If more then one task (like a motion sensor) needs an interrupt and you are using a small controller you will need to split it up to more then one node or redefine your objective.
These are just some thoughts I have been running with for now. Any other persectives are greatly appreciated. There are several of you that have a lot more experience with this adventure then I do.
I use an ftdi cable https://www.sparkfun.com/products/9873 Be sure to use one that can be switched to 5v. I have one that supports both 3.3V an 5.5V.
Once you've hooked up the ftdi to the arduino and your make book, you're good to go
gw.begin(incomingMsg, MY_NODEID, true)
turn this node into a working repeater ?
Yes, this enables the repeater feature.
OK,thank you. This will save me an additional node..
What does you sketch look like? Do you listen for incoming messages and answer the request when it arrives?
The node does not keep any state by itself of the last sent message etc. So you have to save these values yourself and send them upon request.
@raulandresmoch Intresting reading on accuracy & lifetime! of temp sensors.
The SHT71 does seem to be generally superior to the DHT22. It is better made, at least as accurate, more precise and responds more quickly to change. It does of course also cost ten times as much.
Reliability may justify the higher cost, but I have to be cautious because I have not had the Sensirion device as long as the others.
Two of my six DH22 / AM2303 devices have failed. Life expectancy is around one to two years.
After 18 months of continuous operation only one of my six DH22 / AM2303 devices (device E) is able to match the performance of my one SHT71. Of course it is possible that I got the one good SHT71, but I do not consider that likely.
The DHT22 cer
list itemtainly is better than DHT11 and easily justifies its``` extra cost.
Did you ever get this going if so can you share the code? My project is similar have a few temp sensors around and send them to an lcd screen node. Lcd can be a repeater to the gateway for logging on domoticz, also if so what extra code did you add on the temp sensor side?
@hek Thank for the update, it looks very interesting.
I have been working on a ESP/MQTT sketch using the ESPWIFI Gateway and the subpub library. I will try the sketch in the development branch. I'm sure you have workout everything I am having problems with
I would really like to get OTA working here as it's freezing outside and I have to go there to update the software in the greenhouse control system.
So please, can we have a 'how to' step-by-step guide to OTA? Please?