today I have finished the 3d printable case of the d-diot hub.
The hub basically is a Raspberry Pi 3 with the d-diot board (see this topic) that offers the following functionalities:
IR Gateway (blaster and receiver) to control every device that has a dummy infrared remote.
433 Mhz Gateway with the RFLink firmware running on the on-board ATMega2560 microcontroller
Dual MySensors Gateway: NRF24 (2.4 Ghz) and RFM69 (868 Mhz).
Latch circuit to power-on and safely power-off your Pi with a simple button press.
SSD1306 I2C Oled display controllable in Home Assistant
Radio activity LEDs for IR and Mysensors gateways
Nice and powerful web interface thanks to Home Assistant
Easy setup and configuration with the d-diot image
If someone is interested, here the detailed build instructions.
I agree, the amount of time required to learn how to do the things is quite high and after a lot of research you will find that other people have had the same issue... so in the end you have just reinvented the wheel!
In any case I think that MySensors is a very good project and probably underrated respect to how good and useful it is for a maker that wants to build its own domotic sensor and actuators.
For the reasons above (and others), some times ago I have started the d-diot project:
The hub (Raspberry Pi + d-diot board) implements, among the other things, two MySensors gateway (RFM69 868 Mhz + NRF24L01). All the software configuration steps are well documented in the dedicated section of the wiki.
In general the software part is easy because all is preconfigured in the d-diot image. Just burn the iso image to an SD card and you will have Home Assistant and MySensors working and ready to go.
3d printable sensors and actuators and the relative PCBs and firmware are part of the project. All parts (hardware, firmware, 3d printable case) are open source
In the wiki you will find the detailed build instructions (with pictures) for each device, so @mhkid and @Psilin maybe here you can find some useful information or a at least a good starting point for your nodes. In particular the Mini-BT-Pcb-328P is a general purpose and flexible board that could be useful for a lot of small (battery or USB powered) RFM69 or NRF24L01 nodes.
Now I'm in contact with PCBway, a PCB manufacturer that offers also soldering service, so If there are enough people interested, I think that it is possible to start thinking about the possibility to start a small production of some boards, maybe already assembled. In my opinion this will be helpful for other people.
Let me know... maybe we can start something
@alex28 yes exactly, it may look exagerated but this is how that is. But development boards (like OP design) can maybe fit in the "subassemblies" group, so mostly for development purposes only. That's a while I looked at this, way before debating..
more links here:
@jocke4u I run 2 RF gateways and it's not a problem. When you 'migrate' a node to a new gateway make sure to run the mysensors clear eeprom sketch first to get rid of the old routing table or you might have issues.
Thanks for taking a look Mikeal,.
Here's my update:
I added a 47uF cap to the 3.3V input to the RA-01 Lora radios on both Node and Gateway, now the SF 12 long payload messages pass!
I tested various SF and BW and coding rates, I decided on the following for the "long-range mode". Typical use will be point-point mode, or gateway to 2 or 3 nodes max, no repeaters. Horizontal polarised yagi antennas.
MY_RFM95_FREQUENCY 433237500ul (its 1MHz away from my co-located standard mode gateway frequency and other local ISM users).
RFM95_MODEM_CONFIGRUATION RFM95_BW62_5CR45SF4096 (Typical time-on-air is around 4000ms.
MY_RFM95_ATC_MODE_DISABLED (to reduce traffic).
Passive mode = off.
MY_REPEATER_FEATURE = off.
CAD = Default settings.
Encrypton = Off
Signing = Off
Sleep = Off.
Further test planned:
866 MHz setup.
TXCO setup narrow band modes to 7.6KHz
Chain network topology with repeaters.
Higher RF power (Ham radio license).
@NeverDie I can give my thoughts here, and we can move it later to another thread if necessary.
The bigger selling points, at least for me:
Every project is a self contained directory, even the boards configuration, bootloaders, libraries, code and build procedure
I have a project template for mysensors (mainly a platform.ini) that I copy for each node that I create.
I can manage everything with my known tools (vim, make, git, etc)
I like to play with arduino and electronics, but have other interests (Family, friends and 3 small kids...) so I usually have little time to spent in my hobbies. Platformio allows me to just have all the configuration in code and know 6 months ahead that I can do a "make clean && make upload" for a particular node without issues, even if I lost my PC, as everything is in my gitlab account.
Also the FW of my 3dprinter must be complied and uploaded with platformio (marlin 2.0) so I can have only one tool for both hobbies.
@NeverDie Actually no. Because this is an EPA list denoting the effectiveness of listed products, it's much too complicated to find out concentrations of the active ingredient, and I would guess that the kill times have a Factor of Safety built in.
Saw nothing on what surfaces are referred as the Virus is known to survive on different surfaces for different durations, again I suspect a high FoS.
Sorted on "Follow the directions..." and looked for Human Coronavirus, ethanol and isopropol both pop up at 30 seconds contact (normal terminology for disinfection) time.
Hypochlorite is a few minutes but varies according to brand name, so not really helpful if you don't know concentrations.
My point remains that alcohol is readily available, and as an additional precaution post washing surfaces probably more than sufficient in a domestic environment.
If 70% is adequate for handwash on skin where it evaporates in a few seconds, no reason why on a cold non-porous surface it would be no less effective