@alowhum
Some more personal remarks (hard to do in english, to be honest):

Reading your postings wrt. to the DS18B20 things and your enhancement proposals, I can somehow understand about your frustration. (The DS18B20 and BME280 I also use, so this is a part I can follow to some extend, other than a lot of other hardware you mentioned). I also suffered from changes in the libs that made it not to easy to get things going (routines from "the outer world" becoming private and so on). And some of the comments on your code in the mentioned thread are rather hard to understand or interpret.
As I also did one pull request in the past, I also know how high one's frustration tolerance has to be just to get through the necessary organisational process (including copyright questions and so on).

But: this is necessary stuff to go through... And the devs here are really doing a great job in quality assurance - at least imo.. But to be honest: It also took me quite a lot of time to find out, how difficult it in fact is to choose the right compromise between a lot of aspects.

Just one example: Your last proposal wrt. to temperature was to use BME280 as a future standard. Did you ever use more than 2 temp sensors on one node? Most likely not, as this is more or less only possible using the 1wire protocoll (I have around 25 of them on 3 nodes using 7 Pins as data lines).
And BME280: Try to compile the last version of the lib for ATMega328: It's broken... And the lib consumes way more memory (ok, to be honest: most likely most is for doing forecast calculations).
So please keep two things in mind:

• The two of us just see a small part of the world and are just about to start understanding how things really fit together. So going just one step after the next is best way to do. Don't be to eager, good ideas will find their way in the MySensors or Arduino code base.
• There are a lot of forums around, but only a few have the spirit you find here: If you ask your questions, you will most likely get a friendly answer that could bring your project forward!

So a big thank you to all the devs and mods around here! Great job!

To start, first decide what controller software you want to use (https://www.mysensors.org/controller).
Then you can start to built a sensor network (https://www.mysensors.org/about/network).
Typically, all the sensors are based on small Microcontrollers (most of the time: ATMega328). For using ESP8266-based Hardware (NodeMCU), you'd better have a look at other projects like ESPEasy ot Tasmota. Most controller sw supporting MySensors will also have a kind of plugin for these type of (ESP8266-) firmwares.

youtube really seams to tear "everyone" to "fast and easy solutions". I personally really hate that IoT stuff talking to the www without asking and therefore try to avoid whatever can't be flashed with own firmware for "offline" use.
Atm. I'm fiddling around vith voice control via Rhasspy. Really impressive project, btw. (I'm not to deep into all the details on that, but controlling my lights, shutters or media stuff works really great, even without any online service provided by any of the big players; just a service with relatively small resouŕce footprint on a dual-core server built ages ago!).

In my original HW setup I also used D4 for Servo and D5 for 1wire, but any pin should be ok AFAIK.

Additional remark: powering the nRF24 through the 3.3-PIN on Nano may cause trouble; use at least a capacitor as recommended in "Build".

Hi SuperKris,

most likely, there is not a definite answer to your questions.

First a very good point for a lot of info around the nrf's: https://arduino-info.wikispaces.com/Nrf24L01-2.4GHz-HowTo

I personally got best results using the PA+LNA-Versions and additional base modules, power sourced through 5V with PA-Level set to max.

This is the standard-level which is used as long as there is no explicitely defined other level. This is the standard mechanism using the myconfig.h settings. Keep eyes open, as this is defined to LOW e.g. in the GW-Sketch...

MAX will also work with the non PA+LNA-Boards, but keep in mind using this setting also means higher power consumption, so soucing the NRF through Arduino's 3.3V-PIN might not work.

@stefferd (I'm most likely the RS485-user @gohan is reffering to).
Imo, the key question is how to deal with the TRV's. If this is more or less independent C-code already adopted for the microcontrollers you are working with, you most likely will not have to big efforts to migrate your entire project to mysensors.

So I'd recommend to start first in understanding how MySensors in general works and how it's integrated into your controller software. Use something rather simple like a temp or PIR sensor node (or a combined one). As communication layer I'd start with RFM69 (868MHz). Should be sufficient to get much better results than in 2.4GHz WiFi.
Then you could try to replace Node 6 as a first step of migration. Next Node 4 with additional repeater functionality, in case Node 5 is to far from your controller/gateway to make the communication directly. For this, you won't need any RS485, this just replaces the wifi connection and one single RS485 connection.

As your current wired solution also works to your needs, you may stop there or - decide then to also sowitch over to MySensors with this part.
Remark on RS485: I at this moment would neitherblame the RS485 chips nor the implementation in MySensors to be the origins of my troubles. It just took me very long to understand all the parts that can affect communication. So if you already have a working electrical layout of RS485 lines, most likely this will just work when switching just the used lib for communication. At least one user in the FHEM forum has recently installed a line with 4 nodes running reliably for several weeks, and there seem to be a lot guys out there with similar results. But no guarantee...

You seem to send the temp messages under a different ChildID than it is presented:
presentation takes "1", send uses "0". You have to allign that, e.g. by using

send(msg.setSensor(i+CHILD_ID_TEMP).set(temperature,1));

But as long as there's just one DS18B20 doing that dynamically doesn't really make sense. Using the defined message structure (MyMessage msgTemp...) could make things more transparent.

Also there's no sending command for voltage. So why do you expect the controller to receive also voltage?

Found this some days ago: https://github.com/mysensors/MySensors/pull/1142

Adding these changes to a 2.3.0-alfa base seem to make a big difference in reliability .

So if there's other users having similar problems: please make also some testing of this patch.

You will get further updates and some more info on my recent setup, so far: Thanks a lot for all the ideas and hints to improve things!

seeers created this issue in mysensors/MySensors

closed Avoid data array overflow #1142

@sebex At least some answers to your questions:

• As Nano and Uno use the same processor, there's no big difference between the two, besides the fact Nano's just USB powered...
• when talking about environmental data, you'd perhaps also like to have a look at BME680; it doesn't deliver CO2 directly, but the delivered restults ale partly calculated on this.
• Most newer (I2C-) sensors seem to work at 3.3V internally, so when powered directly at 3.3V, you might be able to avoid losses due to a voltage regulation
• DS18B20 Modules sometimes come with a resistor, so you'll have to desolder that in case you want to use more than one on the 1-wire bus; "naked" sensors might be more suitable, e.g. if you want them to be mounted closed to a metal tube to measure water temps => depends on your needs.
• ZigBee and MySensors are completely different worlds. (Apart from RS485) MySensors itself is capable of building a mesh network.
• In general, MySensors can be used with any meassuring equipment as soon as there exists an arduino library for the hardware - the rest ist just "packing" the measured values in a MySensors-compatible format for data exchange with te controller. Searching the web for CO2+arduino+sensor gives at least some results. Better ask for experience with a specific sensor and avoid starting "multiple" questions threads like you did here.

@ben999 If you do node-to-node communication, the message does not necessarily need a controller; it is routed through the lowest common repeater node (this might be the gateway). Eg. if you have two nodes 5 and 6 that are communicating over node 4 with the gw, the gw may not even see the message.
Coding then looks like this:

send(SisternodeMsg.setDestination(MY_SISTER_NODE_ID).setSensor(CHILD_ID_SISTER_TEMP).set(temperature, 1));

In case you use a controller, you would have to map the values through the controller's functionality (eg. put temperature value #2 from node 5 to value2100 on node 6 so this can be requested from node #6 using it's own ID and child ID 100 - V_VAR2.

In both cases you have to code appropriate receive()-functionality.

@Yveaux said in Wake-up by interrupt doesn't work:

You should not sleep a node that must be responsive to incoming messages.

As smartSleep is used, this might work, but requires the controller software to also support the feature. Additionally, using ACK-request (in case the RF connection isn't reliable) might be a good idea.

@TonicCorvid
Some additional remarks:

• if the node is not battery powered, I'd recommend to use a "non blocking loop" instead of "sleep" or "wait". See the "SLEEP_MODE" - false tree in pulse water meter sketch as a reference how to implement this. Note: this only is needed in case you want some kind of regular reporting (e.g. for a heartbeat message). So just looping and checking pir state (and switching light off after some periode of time) might be closer to what you want to achieve - and easier to program.
• in case it's battery powered and your controller supports the smartSleep feature, imo using that feature instead of wait() is recommended.
• nut sure, but using long wait() periodes in battery powered nodes might dramatically shorten battery life.

Basically, you seem to search for a "multi-contact-multi-relay" solution. This for sure is possible with MySensors, but still the question remains: Why MySensors at all? For that kind of task, no controller is needed, to me this seems to be "just a simple arduino sketch" running on a single MCU.

Independend if you want to go the MySensors route, imo you will have to go through a fast learning curve. Good starting point may be https://forum.mysensors.org/topic/4847/multi-button-relay-sketch/33 - but this is with monostable buttons and not bistable contacts. So first steps could be to understand, how this sketch works and can be extended to more buttons/relays (you may need port extenders or a different MCU to add more PINs), then to adopt it to bistable contacts, and last switch additional relays for the "indicator LEDs".

Additional remark: If you finally want to use additional controller software and "need" additional communication between multiple MCU's (for other tasks), have a look at RS485 transport layer (or PJON (in development?)).

Is there any specific reason for using 2.2 and not either 2.3 or even 2.4 (development tree)?
Afaik, there's been especially some changes around the RFM drivers, so giving newer versions a try might be a good idea .

@skywatch said in Solar/battery powering:

@zboblamont said in Solar/battery powering:

@rejoe2 Anti-freeze.

But then the hot water would not be suitable to shower/cleaning/pool etc and you then have to go to a heat exchange tank, somewhere to put it and insulate it and pipe to it. I am sure is can be done, but the fact that it is not 'standard' hints at it being costlly or impractical or both.

In fact, imo it's highly recommended to use a seperate circle for the "transport medium" (typically: antifreeze liquid)! Otherwise you will at some point in time get problems with corrosion or deposited dirt particles if media would be continuously renewed. Dependent on the needed amounts of (potable) warm water, it might even be a good idea to have three circles (medium for panel, heating water, potable water). But tanks, heat exchangers and so on (including steering electronics ) are (relatively inexpensive) standard components - at least here in Germany. So imo technical complexity isn't a thing to worry about too much. But as already mentionned: I really doubt, if you will have a financial benefit out of such an installation, if you have to built it from scratch nowerdays. Additionally: have a close look, how big the need for hot water really is - in most cases, e.g. 5m² panel size for a family of 4 persons should be enough for hot water supply in middle Europe (+300l tank volume). As soon as heating is involved, you'll need much higher tank volumes - with no benefit in summer, but not sufficient capacity on roof top or tank volume in winter times?

@rejoe2 Agreed! - But it's not OT as you could mysensors the hell out of such an installation!

Indeed, buiding one's own MySensors-based controller for such a hybrid heating ecosystem would be right on topic - but not in this thread here...
Fyi:

• One of my very first things to get done with MySensors had been around my (gas based) central heating system;
• we have some tubes installed that would allow medium transport from roof to cellar. But to be honest, atm. I'm not willing to invest in tanks etc.; it's just not cost efficient, even if I would do a lot of the installation work myself....

@skywatch It really might depend, how "northern" the respective area is, but at least here in Germany, the used liquids imo are well tested and don't cause much trouble also in (rare) frost or snow conditions.
(@all: Sorry for one more OT comment).

@skywatch said in Solar/battery powering:

But yes - I always wondered why they didn't water cool the panels and use that hot water for the house hot water system or swimming pool. I suppose that would increase production and installation costs and complexity significantly as well as add more points of failure.

In fact, theres some few companies offering "hybrid panels", see e.g. https://www.todoensolar.com/300w-ecovolt-hybrid-solar-panel or https://dualsun.com/en/product/hybrid-panel-spring/ (don't have experience with neither of them).
Imo complexity isn't that much higher than with "conventional" solar panels for heating systems (liquid based, as known for much longer than the use of electrical PV systems in private environments). It's just the PV aspect added, which itself isn't highly complex, too. In fact, one needs bigger water (or other liquid) tanks to store the "conventionally harvested" part or the solar energy. If you don't already have this part of the installation up and running, the question is, if this makes sense at all or if just using electrical energy to heat (much less) (heating) water is more cost efficient.
(But this isn't really MySensors related, as 300+W will in most cases not be necessary to drive one or some more nodes...)

youtube really seams to tear "everyone" to "fast and easy solutions". I personally really hate that IoT stuff talking to the www without asking and therefore try to avoid whatever can't be flashed with own firmware for "offline" use.
Atm. I'm fiddling around vith voice control via Rhasspy. Really impressive project, btw. (I'm not to deep into all the details on that, but controlling my lights, shutters or media stuff works really great, even without any online service provided by any of the big players; just a service with relatively small resouŕce footprint on a dual-core server built ages ago!).

@monte said in Where did everyone go?:

@NeverDie I am just paranoid about relying on a cloud for everything.

Imo it's not only the technicals problems wrt. to connection cut off and so on, but also relying on cloud services raises a lot of security issues, see e.g. https://www.youtube.com/watch?v=urnNfS6tWAY (unfortunately in german) wrt. to all that stuff working with sume "Tuya"-based "App". "Military grade security" for cloud bases solutions?!? Complete illusion, at least with these offers from far east also distributed by some discounters here in Germany...

@NeverDie said in Where did everyone go?:

Even today, most weather stations and temperature sensors [...]

There's some clever solutions in the world to get the data out of these locally, e.g. OpenMQTTGateway for a lot of BT stuff and some 433MHz gadgets. I personally use FHEM as central Home Automation system, also offering a vast variety of solutions for 433MHz and 868MHz proprietary stuff out there (see keywords CUL and SignalDUINO in the command reference without the need to use any cloud service (including somfy, water meter signals, ...). Might be tricky in detail, but there's quite some folks out there using FHEM for the single purpose to bridge some special RF stuff to the MQTT world, btw..

As my own activities wrt. to MySensors, the stuff I soldered several years ago just works (actually running on some older beta version). So no need to aks tricky questions atm..

@monte said in Where did everyone go?:

It feels like people come to mysensors, make relay node, temperature sensor

If one just wants to have a temperature (or humidity) sensor or a relay, buying ZigBee or BT or ESP826x-based stuff is cheap and easy, no need to fiddle around with voltage regulators, fake nRF24L+, capacitor sizes and so on. So most people just beeing interested in quick solutions will not even care about these simple sensors.

and then go forward for more complex solutions to never come back.

Imo, MySensors still is a very good solution if you have the need for more complex or "clever" solutions. Choice is not to big, if you are looking for solutions with wired or LoRa nodes, and scripting more complex "rules" for Tasmota or ESPEasy seems not to be very common to build somehow autonomous subsystems.
Btw.: node2node communication in MySensors is not well explained as well. So also in the MySensors ecosystem most users are used to rely on some sort of central system to do logics as soon as more than one node is involved.