@monte said in Modular sketch to be configured with JSON (idea): Imagine you have base firmwares for most sensor types, or it can be generated with NodeManager. I don't see specific technical limitations to have this working. On the NodeManager side would be: Include in the sketch all the sensors you want, which is already there Have a logic to configure sensors remotely, which is mostly there through SensorConfiguration (https://github.com/mysensors/NodeManager/blob/master/sensors/SensorConfiguration.h). If then the configuration is through individual messages or json, it makes little difference. There might be some configuration settings missing since not all are available OTA Implement a logic for configuring only specific sensors. Shouldn't be that difficult, probably best is to have a enable/disable switch for each sensor (https://github.com/mysensors/NodeManager/issues/500), having all the sensors disabled by default and then dynamically enabling them Bottomline not something to put in place in a few minutes but all the building blocks are there. I do not have at this time spare cycle to spend unfortunately but feel free to start looking at it if you like. user2684 created this issue in mysensors/NodeManager open Add option to enable/disable a sensor dynamically and remotely #500

Nice project manufacturers datasheets, RF appnotes etc all mention this, with results for different usecases (like gnd plane size etc). I mentioned it a few times on the forum: nothing under or near antenna (keep out zone) their matching circuit, and CE/FCC certif are based on their development boards+their antenna if external, often without enclosure. there are a very few pcb antennas which are resilient to untuning. ceramic or meandered pcb are usually more compact but less resilient (like when you approach your hand and device suddently has better or worst communication) once you change any of these parameters (board shape, gnd size, enclosure etc), it breaks FCC, and may need retuning, still you can get useable range. "ideally" tuning should be done once enclosed for example. manufacturers can't cover all cases. on my side, I try to follow these rules. and when interested in a design or a device, I check this. Mainly the routing+gnd, antenna choice, keepout zone, and orientation vs my usecase (long range needed or not for example)

Hi @Nca78, I've placed the order on the PCBWay in early January, so it's almost finished. The factory just recently restored assembly services for some kind of boards including this one. Hope to have it in hands within a week or two.

Please Is it possible to buy only PCB? Do you plan also to release your sketch?

hello @berkseo can you share sketch for this sensor ? i am very intrested about this thank you PS: great job !

Can you tell something about the range of this node? And do you see a chance to post the schematic?

Could you please update the description with what component goes where on the pcb?

@lexusburn 1.I do not plan to add anything to this project. he as there is. Just an evaluation module. 2. The sources for the order are attached to the project on openhardware. Assembled modules I do not sell now, too lazy to solder them. ...Logical continuation of this project: E-paper_2.13 nRF52840 bme280 Mysensors | Zigbee – 00:45— Andrew EfektaSB

@nca78 I don't use ATAES132A. I put it in just in case I wanted to invest some more time using it. I now just use SimpleEncryption, it's secure enough for my purpose atm. (since the area I live in uses KAKU a lot, an insecure 433MHz lightswitch, I don't think anyone would be bothered to hack my temperature sensors. I found 163 433Mhz devices when I left domoticz logging for a couple of days.)

@Nca78 said in NRF52 Recessed Vibration+Contact sensor for door/window: (and an unpopulated footprint for an accelerometer, too). I wonder whether that unpopulated footprint is where the antenna is?

This project is impressive, I really like it. Pity it is so silent about it. After all this work, are you not willing to finish it?

I think you can just set the I2C pins in MyBoardNRF5.h without remapping the pins in MyBoardNRF5.cpp. Look in MyBoardNRF5.h, under the Wire Interfaces section. Set SDL and SCA to 30 and 31 as appropriate for your board.