I also want to highlight one problem of the arduino IDE, and that is that it is very local to your machine. It makes hard to share your projects with others or even to migrate to a different machine of yours. This may not be a problem for casual editions, but as soon as you have build 5 or 10 things this starts to be a concern. People should be able to store their projects whenever they want and not be tied to specific paths/configs on a particular machine.

@TRS-80 I looked at Grafana and InfluxDB a few years ago and found them supremely limited. It may be that I am a MS SQL Server user but the act if trying to do an update/delete of a value in InfluxDB is painful. Running everything through a JSON call to modify data annoys me. So, all that aside I prefer sending data for long term storage to an instance of SQL Server 2012 - even with 4 sensor nodes + weather queries and some other data that send info every 30 seconds, 5 minutes, 10 minutes, and 30 minutes for a few years. I am not even above 100 MB of storage used. The data types are Date, INT, CHAR(xxxx), and in one crazy case VARCHAR(1000). I use Domoticz's built in sqlLite and hassio's DB to handle the data view from my controllers (yes, I have 2). The split of data occurs in Node-Red where it gets the data from my MQTT broker and sends to controllers (different subscription topics due to C/F fubaring in hassio) and send to SQL Server for long term storage. Efficient storage types is the key so a timestamp as an INT/BIGINT would be nice. As long as all your values are INT as well that is even better. Timeseries DBs do have their use, I have just not found one I like. If there is a timeseries DB that can be accessed via ANSI SQL that would be awesome. Other thought - you could use Elasticsearch to send in values as "documents" and then run analysis on them. For dataviz, I use the built in ones in my two controllers and I have written my own to handle long term data analysis. I prefer Highcharts for doing the viz as that is what I use at work. It is clean, efficient, and fully customizable.

Wow, I would have never thought that many either! Well done, guys. :clap: I was satisfied when hek said we were above water, and should remain so foreseeable future. :) But thank you for the additional disclosure @tbowmo, I am sure anyone searching for such information will appreciate your forthrightness.

@TRS-80 I have similar thoughts for a controller for my heater (hot water radiators with an oil boiler and 4 zones). For 1 and 2, I realized I could wire my node into the zone controller. It has a common, so I can derive the node power from the controller. Since it works over radio, it doesn't have to be where the old thermostat was. I have temperature sensors in all the rooms. The node controls 4 solid state relays that are wired in parallel with the existing zone thermostats. That helps with 5. The idea was to set the conventional thermostats at a low value. Then if my node failed, at least the old thermostats would kick the heater on before the pipes started to freeze. Also as a fail safe, if the node has the heat on and doesn't hear from the controller periodically, it will shut off. Still working on that part. As for controlling it, there is a domoticz plug in here: https://www.domoticz.com/wiki/Plugins/Smart_Virtual_Thermostat.html It only works for heat, but the underlying code is pretty straight forward, and it lets you average sensors. There might be something there you can adopt. I ran it with a MySensors modified space heater all last winter and it worked well. Unfortunately, something kept killing the radio on my node, maybe a spike from zone controller relays. I haven't sorted it out yet, so the heater thermostat remains a work in progress.

@TRS-80 said in wait() with interrupt: @Yveaux & @mfalkvidd, I can't help but make it complicated, I'm descended from Germans! :D :D :D Aber das Traue ich dir.

@waspie said in Is MySensors Binding needed in addition to MQTT Binding (in OpenHAB 2.5.5)? (aka request() node state via MQTT): I had initial problems with the 2.4 binding and went MQTT only. Pretty much my exact experience as well. I've been really happy with the plain vanilla Ethernet / MQTT gateway (without MySensofs binding) so far this time around. But I'm easing into it slowly and lightly, bit by bit this time. But so far, so good! :) I probably have dug into the MQTT and MySensors protocols, as well as pure textual configuration of OpenHAB well enough to probably figure out the issue I originally posted about. But then I realized I probably don't need to get state from the controller... This node will be a 3 relay node to control my HVAC (fan, compressor, heat) and so it really doesn't need state on startup. They can just start up always off, and then when temperature, humidity or other settings / rules demand it, controller will just tell the relays to turn on. I think I was at the end of like a 14 hour bender of reading and working on stuff when I made that post. Some times, you should just go to bed, instead. :D :D :D One thing I guess I am still curious on is: what functionality exactly does the OpenHAB binding provide, other than auto-discovery and (probably much) easier node management and creation? Because I struggled a bit at first, but now that I am over that hump, I am actually really glad all my config is in plain text files instead of some hidden automagical database deep inside the bowels of Java and OpenHAB. :D

@TRS-80 There's an argument for putting two different value capacitors near the nRF24L01 (or whichever radio you're using). A 0.1uF bypass cap to help filter out noise, and a higher value cap as insurance against possible battery ESR and/or inductance from possible long battery leads/traces. For example: https://www.openhardware.io/view/480/Compact-nRF24L01-Pro-Mini-Bottom-Shield#tabs-design

However, reading carefully the descriptions state that some of the "5m strips may be soldered together" LOL, Normally not a problem, but the adhesive on the backside of the soldered parts can be weaken. also, they show pictures of 3M backing, but do not explicitly state that the backing is 3M. Well they are shipped with the 3M backing... but usually they can just support their own weight and not a gram more. I suggest to obtain double sided adhesive for parts that are more stressed.

@UglyKidJoe I have been using OpenHAB and MQTT for a number of years now. The reason for using MQTT and not just a serial connection from the MySensors GW is partly the flexibility as many have stated previously here. Easy to test, using e.g. the mqtt.fx tool. If you want to know what is going on you simply connect to the MQTT stream and "snoop" on the messages. Another reason is that I am running three geographical sites on one OH installation. OH is running on a NUC at my home. There is also an MQTT GW here. Two other My Sensors MQTT-GW are running remotely in two summer houses. The three GW connect over internet to a cloud-based MQTT broker and OH connects to the same broker. In that way I do not have to open any ports into my home network for access should I have had a local MQTT-broker at home.