General Discussion

@mfalkvidd Not just the NFC chips, but their billowy antennas also add to their size. I wouldn't be surprised if a certain fully functioning nRF51 module has a smaller footprint: [image: s-l225.webp]

@alowhum most of these questions are way too advanced for me to answer, but I know that wait() calls _process() which processes messages and kicks the watchdog (through doYield()). See https://github.com/mysensors/MySensors/blob/development/core/MySensorsCore.cpp#L565 while (hwMillis() - enteringMS < waitingMS) { _process(); } By default, nrf24-based nodes do not use interrupts for message handling. There is nothing done in parallell.

Thank you so much, just the input I needed. Works like a charm, I have included the output from the serial port, if any one else wonders what to expect. __ __ ____ | \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___ | |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __| | | | | |_| |___| | __/ | | \__ \ _ | | \__ \ |_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/ |___/ 2.3.1 16 MCO:BGN:INIT NODE,CP=RSNNA---,REL=255,VER=2.3.1 26 MCO:BGN:BFR before ShuntCtrl to clear EEPROM presss c now: 321 4156 TSM:INIT 4157 TSF:WUR:MS=1000 4159 TSM:INIT:TSP OK 4161 TSM:INIT:STATID=123 4163 TSF:SID:OK,ID=123 4165 TSM:FPAR 4184 TSF:MSG:SEND,123-123-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 5159 MCO:BGN:STP setup 5161 !TSF:SND:TNR 6164 !TSF:SND:TNR 6192 !TSM:FPAR:NO REPLY 6194 TSM:FPAR 6211 TSF:MSG:SEND,123-123-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 7165 MCO:BGN:INIT OK,TSP=0 8288 !MCO:SND:NODE NOT REG 8372 !MCO:SND:NODE NOT REG 8455 !MCO:SND:NODE NOT REG 8539 !MCO:SND:NODE NOT REG [ %0PH 18.8 Vejr 18.7 ] [ %16PC 18.6 ->25 18.4 ] 8636 !TSM:FPAR:NO REPLY 8638 TSM:FPAR 8656 TSF:MSG:SEND,123-123-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: [ %0PH 18.8 Vejr 18.7 ] [ %16PC 18.6 ->25 18.4 ] 11094 !TSM:FPAR:NO REPLY 11096 TSM:FPAR 11114 TSF:MSG:SEND,123-123-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: [ %0PH 18.8 Vejr 18.7 ] [ %16PC 18.6 ->25 18.4 ] 13550 !TSM:FPAR:FAIL 13552 TSM:FAIL:CNT=1 13554 TSM:FAIL:DIS 13556 TSF:TDI:TSL [ %0PH 18.8 Vejr 18.7 ] [ %16PC 18.6 ->25 18.4 ] [ %0PH 18.8 Vejr 18.7 ] [ %16PC 18.6 ->25 18.4 ] [ %0PH 18.8 Vejr 18.7 ] [ %16PC 18.6 ->25 18.4 ] [ %0PH 18.8 Vejr 18.7 ] [ %16PC 18.6 ->25 18.4 ] 23558 TSM:FAIL:RE-INIT 23560 TSM:INIT 23561 TSM:INIT:TSP OK 23563 TSM:INIT:STATID=123 23565 TSF:SID:OK,ID=123

@neverdie said in Sensor Up or Sensor Down: si7021 Didn't even think of that, but it makes sense.

@noclue said in Sensor advice: @hj_sk I want to control my idea. I have put my ideas out there before, only to be stolen. either do as Tbowmo suggests, or if you are afraid that we will all steal your idea, I can recommend to contact a electronic development company, that will sign a non-disclosure contract, a company could be this one (I'm not affiliated with the specific company) https://www.prevas.com/

@sebex this is purpose or the "ABC". They neeed to be exposed to outside air at regular interval (usually at least once a week) to recalibrate themselves and stay accurate for years.

Here is a review of this https://youtu.be/55tgEMTumGo Not sure why, it YouTube has started suggesting this kind of videos after I read this post

@neverdie said in Anyone here tried/using either Dragino LoRa gateway or some other LoRa TTN gateway?: Are you sure? I'm glad I asked, because from my reading I had thought that FOTA had been baked into the LoRaWAN specification for over a year now: https://lora-alliance.org/in-the-news/lora-alliancetm-enhances-lorawantm-protocol-new-specifications-support-firmware-updates I am sure, but I am unable to find a reference. Having it in the spec is not the same as having it implemented in the infrastructure. If you deploy your own TTN v3 stack (most of it is open source), you can probably get it to work. I've had on my todo to do this for a long time, but other things have priority. You can also but a commercial license for the commercial version: https://www.thethingsindustries.com/technology/pricing So far I have only seen one implementation of fota, and that's by arm, which has a hard requirement that your firmware needs to be built on arm mbed. https://github.com/ARMmbed/mbed-lorawan-update-client

@NeverDie I don't remember exctly, but voltage requirements for mcu only might be the same (approx). On modules, it can differ, depending on external spiflash&ram voltage requirements. I thought you were talking about the esp32-s2, announced a few months ago, which has usb and few more IOs for example but it's single core. the simple S version is maybe used as coprocessor, like on particle boards, if I'm not wrong

@bjacobse Thank you :)

Though Fluke 115 could be a good option if you have enough budget but Fluke 101 is also good basic pocket portable digital multimeter with reasonable price.

@sola Thanks for your prompt feedback.

@tmaster great work!

@brianmichalk Do tell us more. Sounds interesting.

You'll want a valve that's certified to meet NSF 61 standards, preferably stainless steel. Anything else, especially if it's non-certified brass, has a significant chance of lead and/or other hazardous contamination that you won't want leaching into your drinking water. I recently replaced the solenoid on my Miele dishwasher with one of the US Solid electrically actuated ball valves (stainless steel, NSF 61 certified), and it's working fine. Total overkill for this application, but US Solid claims the mean-time between failure is something like 100,000 actuations, so hopefully I'll never have to touch it again. In contrast,the Miele solenoids fail about every 4-5 years, and replacing them with the same part is a total pain the neck. Besides, the Miele part would have cost 5x as much! Go figure.

@mickey Yes you can drive the motor directly from the esp32-cam module, but with MySensors you can put in deep sleep and wake up the esp32 on demand (pir, timer, etc...) for eample with an automation managed by the controller. In fact the esp32-cam, at least with the esphome firmware, is always active and the module become hot after few minutes. With an additional controller more power friendly you can turn on the module only when necessary.

@mfalkvidd If you look close, I'm only sending as a response to a request from the "controller". But I'm still wrong for insist getting the received value from the property bValue. Seems logical to me that it would contain the boolean value instead of a byte size or whatever. If I had used the method ".getBool()" I would had the boolean value. Although, if the controller sets a boolean, the node still gets wrong values, so you still have to transmit an integer 0/1. I don't like it, because it forces processing all the values as integers in node-red, for example. As usual, I'll leave this, my stupidity, behind in the hopes it serves to anyone else. :sweat_smile:

Hi, you can try these power supplies: https://www.aliexpress.com/store/group/UPS-Charge-Function-switch-power-supply/1242857_501520362.html?spm=a2g0o.detail.100008.25.56f87402HSB2Og The are for 12V, but also support an external battery. I have two that work very well.