What did you build today (Pictures) ?

[berkseo]

Another project of mine, the second revision is finished today and put to the test. This is an encoder with accelerometer, powered by nRF52811 chip (datasheet).

[NeverDie]

@berkseo Cool!

[berkseo]

@neverdie Thanks for rating. Especially pleased, so as nRF52 for me began with Your those on this forum.

[monte]

@berkseo nice piece! Do you mean accelerometer for an encoder, or a physical one? And if the latter, what for is it supposed to be used?

[berkseo]

@monte said in What did you build today (Pictures) ?:

nice piece! Do you mean accelerometer for an encoder, or a physical one? And if the latter, what for is it supposed to be used?

I think the use cases quite a lot, I want to implement double tap. For example, there is a dimmable lamp with switching to cold and warm light. Here with the help of a double tap you can control the switch from cold to warm and back. In any case, I think this is a good extension of the functionality.

[NeverDie]

@berkseo I'm glad it was helpful. And now you're inspiring me back! That's a virtuous circle if ever there was one.

[Fleurros]

This post is deleted!

[berkseo]

Another one of my brand new device is ready, today I finished the case for this device. This is a motion sensor on the S16-L221D-2. Also added a temperature and humidity sensor, it can be sht20-21, si7020-21, hd 1080, perhaps something else, now there are many sensors in such cases. Powered by a "nuclear" battery 2/AA (14250) 3.6 V. Powered by a chip nRF52811. I added support for this chip to the sandeepmistry boards.

Soon this sensor will be available at openhardware.io

[tbowmo]

Not hardware though, but I'm working on my dashboard solution for a wallmounted tablet.

I kind of already have this working in angular, but lately I have switched to react (joined a new project at work where they use react for frontend development), so wanted to see how "easy" it would be to create a something similar to my angular dashboard, but in react instead.

Made a small screencast of the dashboard, and are now playing around with "fully kiosk browser" on an old android tablet. Next step is to create a wooden frame, so it doesn't look like a tablet that is mounted on the wall (for WAF'ines).

home automation tablet view – 02:07
— Thomas Bowman Mørch

All data, except weather forecast and channel lists, is from my mqtt broker, where I use mqtt over websockets.I have a bunch of python scripts, and a node-red instance, to wrap things up for the display, and also do a lot of magical stuff, like turning on TV and amplifiers automatically when casting youtube, and then turn the TV etc. off again, when I haven't streamed anything for a couple of minutes. (So the kids doesn't forget to turn off the TV when they're finished watching cartoons)

[sundberg84]

Today i fired up my controller after 6 months houserenovation. Upgraded to new 2.3 version and instantly some old nodes started reporting again . Yes, there were some without battery but several temp and binary nodes survived 6 months without supervision.

[zboblamont]

@sundberg84 Out of curiosity, did you have battery powered Nodes trying to contact a dead controller or did you shut them all down?

When the Controller here died in June/July, the hit on Node voltage was quite spectacular compared to normal decay, in this instance the gas meter which was only supplying hot water and cooking...

[FotoFieber]

@tbowmo said in What did you build today (Pictures) ?:

Not hardware though, but I'm working on my dashboard solution for a wallmounted tablet.

Sigh, this is on my todo list for a long time. I have a working solution with imperihome (gateway to imperihome implemented in node-red) but never get to mount the tablet.

I kind of already have this working in angular, but lately I have switched to react

Second sigh.... popularity of angular seems to decrease. Do I have to learn another framework?

(joined a new project at work where they use react for frontend development), so wanted to see how "easy" it would be to create a something similar to my angular dashboard, but in react instead.

...

All data, except weather forecast and channel lists, is from my mqtt broker, where I use mqtt over websockets.

Third sigh I like your chosen architecture except for the decision using websockets. (It is neither nice from a security standpoint nor is it proxy friendly, but who cares in a closed home enviroment.)

I have a bunch of python scripts, and a node-red instance, to wrap things up for the display, and also do a lot of magical stuff, like turning on TV and amplifiers automatically when casting youtube, and then turn the TV etc. off again, when I haven't streamed anything for a couple of minutes. (So the kids doesn't forget to turn off the TV when they're finished watching cartoons)

I really like your project. Maybe you can publish some react code? (Then I can try t understand another ui framework...)

[Omemanti]

After 4 months of finishing the new house, i finally started to build in my sensors

Do need to build a new repeater, since a part of the sensors are out of reach.

[mfalkvidd]

A 3D printed hanger for dupont cables, mounted on the inside of the wardrobe that is my electronics lab.

Found it on thingiverse, https://www.thingiverse.com/thing:3567126

[tbowmo]

@FotoFieber

I was forced over to react, as the new project I was assigned to is using it (one of the downsides / luxuries of being in a large corporation). But yes, "Another framework". I can't decide if react is better than angular though. It's not as strict as angular on how to design things, but then the "strictiness" could be one of the strengths of angular.. I have experienced it a couple of times, where there are a lot of different ways to accomplish the same thing in react, so it's a bit harder to find the "Best way (tm)", whereas for angular it's a bit more strict path to implementations.

for the websockets, there might be security issues with it but if you want to have an open connection where you push data to the client, you don't have that many options available. I have thought about ditching mqtt for the frontend, and implement my own (websocket) protocol. Mainly to limit access to my mqtt broker, but there is only so many hours a day, and work, wife, kids etc. all want a part of them..

The project is already on github, don't expect anything fancy though..

[nagelc]

@mfalkvidd Neat! It's so obvious once you see it. This is something I need. I have a box full of dupont cables, but it always seems I can't find the right length gender combination.

I also have a wide variety of USB cables hanging on hooks. Something like this with wider slots would be a better solution.

Gonna have to get that 3d printer on day.

[nagelc]

@Omemanti Looks really professional. Are these a commercial style of switch? Wonder if I could get something like that in the US.

[Omemanti]

@nagelc Its al from jung. Series AS500. Its hard for me to search for sellers in the US.. Google forces me to search in the Netherlands.

My understanding that the standard inwall boxes in North America are pretty different than in Europe /Netherlands . The types I use always look like this

But I'll share my kicad files on openhardware.io, only thing you have to do is change the backplate.

This sensor : link

Also made a repeater, but this one is fairly unsafe( I got zapped installing it ). I just got the PCB's for a safer version I hope I can post pictures when everything works.

[Nca78]

A relatively basic board, based on a cheap CDEByte module, some leftover iTead power supplies (with not so-well aligned footprint) and a PCA9555 to drive the SSRs directly. I have suspended ceiling with many light spots so I want to be able to control them either one by one (in small rooms with less than 8 spots) or by groups/area in bigger rooms. This will be hidden in the ceiling in an electric box so I have no size constraint and it was easy to respect the creepage/clearance distance and include slots.

Resistors are the pullups for the I2C bus that I stupidely forgot (and yes I fixed that ugly solder point for the middle SSR)

Result in Things Gateway:

[NeverDie]

@Nca78 Looked at another way, once installed and sealed up it will also be a sort of time capsule.

[Nca78]

@NeverDie said in What did you build today (Pictures) ?:

@Nca78 Looked at another way, once installed and sealed up it will also be a sort of time capsule.

I said hidden and not sealed. Unless you have worked really hard on the FOTA for nrf52 ?

[zboblamont]

Not so much a build as a case study in deploying Mysensors with Domoticz to solve a puzzle simply with heating.
Having retrofitted insulation 2 years ago to my relatively modern house (2013), seeing gas consumption plummet to 55% of previously was a joy. The unknown thermostatic valves and heads were replaced with Heimeier Eclipse and Halo devices a year ago and an undersized Lounge radiator replaced (all paid for out of the first year's savings). The original intent of electronic zone control was abandoned when prices rocketed since the original goal was it being self-funded by first year savings, so a Honeywell multi$ was nowhere on the cards in any instance.
As Honeywell and other modern valve manufacturers have manufactured for thermostatic control, the Eclipse is essentially a dual flow control valve, one part replicating the return or lockshield valve (which is left fully open), the other the thermostatic control. On paper the Eclipse offered the secondary advantage of being pressure agnostic per kW panel, you set the flow and it stays that way.

Delighted though I was to break 50% savings over the original thereafter with rooms remaining within a 1.1c band, there were some rooms colder than were set which made me realise there was some imbalance which I didn't realise then was the transit time from boiler to radiator (or miscalibrated valves).

First step was smart in but stupid out, monitoring the boiler by attaching DS18B20s to the connection nuts. Outgoing measured temperature being 10c below the boiler setpoint should have given a clue, but a week of running round like a lunatic with a laser thermometer and a notebook proved I was none the wiser other than the radiator was hotter than the boiler sensor.
Hence deployed this, a temporary hookup of two DS18B20s on perfboard connected with Cat 5e and phone cable and held with hot glue, two G clamps and some cardboard to ensure they stayed put, and a roving Node...

Not elegant but dysfunctional (hot glue struggled under heat and pressure including having to be levered off the radiator) but it enabled the problem to be identified, transit time... Being able to monitor both the top and bottom panel temperature in relation to the main rads helped nudge the time to get incoming temp close to that taken to hit the main rads +/- 1 minute within a cycle time of 18 minutes...
Not elegant, and Domoticz is useless being built around 5 minute intervals, but it still enables readings to be taken with a notebook and pen in one hand with a glass of Rioja in the other Creeping up on it.. The improvements are felt before they are observed.
My point is, a temporary Node can serve a lot of useful purposes leading up to or supplementing the permanent structure.
The screenshot is two different targets being tweaked...

[NeverDie]

@zboblamont Ah, you got bit by my main reason for not liking Domoticz: Domoticz would be so much more useful without that 5 minute minimum between recorded datapoints. It's a wonder they've never fixed that.

[NeverDie]

@Nca78 Just FYI, I looked into attempting a FOTA on the nRF52 but at the time I didn't feel as though I had enough easy-to-follow information to do it within the limited spare time available. I think adafruit may have some kind of FOTA for the nRF52 with their circuitPython project, but that language's runtime is awfully slow compared to C or FORTH.

[zboblamont]

@NeverDie I don't mind it so much as an overview, it's getting sense of the overview which is the problem as the detail is absent from the graphing.
Simple enough for my purposes though, sitting in a kitchen with a glass of Rioja recording details is remarkably simpler than spilling a perfectly good wine dashing back and forth balancing a notebook, pen, laser thermometer and a clock..
We work with the tools we have, which on balance are a lot more advanced than when I was your age when flints, candles and acetylene were all the rage...

[monte]

@NeverDie I came to this idea after I read again about your trying to add FOTA to nrf52. What do you think about it?

[NeverDie]

@monte I think it may run into the same barrier I encountered with both uPython and FORTH and uLISP. I got them all to do FOTA with nRF52, which is easier because they are interpreted, but in none of the cases could I easily leverage the wonderfully extensive arduino sensor libraries because those are written in C. Apparently there do exist ways to do it with linkers and such, but I wouldn't classify it as easily done. More like "easier said than done." uLISP would have been the easiest to adapt C-libraries, but it's a slow inefficient implementation of LISP, so that was a downside. Although practically anything can be made to work given enough time and effort, there's something to be said for staying within the Arduino framework so as to minimize time and effort.

That said, maybe your idea is different. Sometimes it's hard to really know until you explore it a bit.

[monte]

@NeverDie I mean, what exactly use scenario for FOTA update of a remote working node? What can you possibly want to change remotely without changing any hardware? I guess it can be some logic, or parameters that may require adjustment that can be made remotely, and that's how I think JSON can be used to specify those. I well may be overlooking the big part of a problem, so I ask to better understand it.

[scalz]

@monte said in What did you build today (Pictures) ?:

@NeverDie I mean, what exactly use scenario for FOTA update of a remote working node? What can you possibly want to change remotely without changing any hardware?

for example arduino core used for the firmware (sdk..), libraries updates (MySensors, sensors), etc

[monte]

@scalz but why do you need this on an already working node? Mysensors has backward compatibility so far. Do you expect any improvements from updated sensor libraries for a working node? In this case, you of course would need proper FOTA.

[scalz]

@monte said in What did you build today (Pictures) ?:

@scalz but why do you need this on an already working node? Mysensors has backward compatibility so far. Do you expect any improvements from updated sensor libraries for a working node? In this case, you of course would need proper FOTA.

I don't think that a major fw release (MySensors in this case) always guarantees full backward compatibility.
Perhaps not for a sensor lib (but who knows), still, if not for any core updates, do you expect any improvements from updated MySensors lib for a working node/network? If no, then you don't need fota
app settings != app/fw update

[edit]
Examples when you may need to flash your fw (wirelessly or with a programming tool):

• it was not possible to have backward compatibility between old and new rfm69 drivers (new driver brought lot of improvements for green rf like adaptive TX power, power consumption etc).
  So it required updating network (gw and all nodes). This can happen eventually for a major release (v2->v3 or v3->v4..), a major release could allow "controlled" breaking change if no other way.
• bugs fixes in MySensors files (core, transport, security..)
• new features updates if needed (in MySensors, or your own sketch), easy to imagine, so many things to improve
• etc

[monte]

@scalz as time goes I'm becoming more "Ain't broke, don't fix it" guy. Let's say, you've installed relay node somewhere outdoors, that has been working for a couple years. What exactly would you want to improve by reflashing it with updated library? Or maybe not a relay, but any other node, you have in mind, that could benefit from this action.
Once again, I don't want to argue, just clearing things out for myself.
Thanks

[scalz]

@monte I get it. I think this is off topic here, maybe open a new thread if you need to ask people why/when they need to update their systems, reflash their devices etc
( I have edited my previous reply with a few more examples in case it would be more clear)

[monte]

@scalz I agree that this conversation is off topic, and I indeed started a separate thread before I posted replies here. Fell free to express your thoughts here, if you want: https://forum.mysensors.org/topic/10895/modular-sketch-to-be-configured-with-json-idea/

[xmonika]

Have finished RIB king gate opener/controller based on NRF52840 & MySensors.
image url)

[NeverDie]

@xmonika Nice work! I really like how you very artfully leveraged pre-made boards into such a compact assemblage. Is the backplane something that you self etched or CNC'd?

[xmonika]

@NeverDie a big thank you as I was inspired by many of your post and this was my first Nrf5 project. The backplate is designed in KiCAD and then outsourced for etching to one local semi-hobby service. Modules are then connected via precision header pins (concept inspired by Ardumower)

[Omemanti]

Today I finally assembled some of my new PCB's

2 New front PCB's (a repeater and a LED-Dimmer)
1 New Back PCB that can be used as just an AC/DC power supply or as part of the AC current side of the LED-Dimmer

The last inwall repeater I made was just one PCB, and during installation, I got zapped , so I tried to make a 3D design to counter that.
The part that is the furthest in the wall is the AC side, and the microcontrollers, etc (DC-side) are at the front. Both are connected using 4 pins and are fastened by 4, 3m standoffs

I think this is much safer when, for instance, the front cover is taken off. (i use the same design as: LINK)

Pictures show the FL5150 dimmer at the front and its compatible backside.
When the testing is done, I also want to connect a touch sensor to it, so the dimmer can be controlled remotely as well by touch.

[NeverDie]

@Omemanti said in What did you build today (Pictures) ?:

I also want to connect a touch sensor to it

You may not need an extra sensor. I haven't yet tried it myself, but supposedly the nRF52 has capacitive touch sensing built in.

[iancu]

@sundberg84 Nice, I had hanging issues with Domoticz in the past, until I decided to switch to Home Assistant. Best decision ever.

[maghac]

Built a heat pump monitor based on mysensors on an Nano board and a few LM393 light sensors.

It's simply reading the status LEDs and tells me if they're on or off, and it means I can correlate e.g the compressor or circulation pumps with the electricity usage read from the power meter.

Also, which actually was the main driver behind the project, it allows me to send an alarm to my phone in case the alarm LED goes on. This is usually caused by incorrect pressure somewhere in the system and can be fixed by simply restarting the system. When the alarm triggers, it shuts down everything which is a bit annoying since it can take a few hours before I notice it (usually not until I go in the shower and there is no hot water). I now have to figure out how to deal with the fact that the alarm LED is blinking, which causes a stream of "alarm ON, alarm OFF, alarm ON, ... ." etc messages in Telegram There should be a way to fix this in Home Assistant I hope.

An interesting thing was that I was not able to tune the sensors to give me an accurate on/off digital signal. I therefore have to read the analog signal, and in the sketch decide whether it's on or off depending on the value. The values are in the 0..1023 range and the threshold was somewhere around 1000, so I think it was too close to the end of the range for the adjustment potentiometer.

[Nca78]

@maghac said in What did you build today (Pictures) ?:

I now have to figure out how to deal with the fact that the alarm LED is blinking, which causes a stream of "alarm ON, alarm OFF, alarm ON, ... ." etc messages in Telegram There should be a way to fix this in Home Assistant I hope.

You should fix it by using a flag for alarm led on and the last time the alarm led went on :

• when led gets on, set the "alarm on" flag in your code, save the millis() of last alarm led on in a "last alarm led on" variable
• in the loop, check status of the alarm led: if off and "alarm on" flag is on, compare millis() with "last alarm led on" time. If the difference is higher than the duration of a blink interval then your alarm is really off.

[maghac]

@Nca78 You're probably correct. I first wanted to keep the sensor "dumb" and put all logic in the controller, but it makes sense that the sensor actually returns the true alarm state - which is ON if the LED is blinking.

[nagelc]

It's s WS2812B LED strip driver using STM32 blue pill and RFM69HCW.
I have made a few revisions previously, but this one fits an off-the-shelf enclosure and uses the pcb and enclosure lid for strain relief on the LED strip connector wires.
I like the concept of using the enclosure slots to hold the pcb. Maybe a slightly smaller enclosure next time.

[Nca78]

Today, a 5uA always on display with a PCF8553 LCD driver and a GDC1038 LCD from GoodDisplay. Power consumption varies with voltage but mostly with what segments are on/off, but at 3.3V with segments on to display data on all parts of display (2*4 digit numbers and 3 letters) it's always below 6uA.

Not sure why the Youtube video won't integrate as it should, but here it is for a more animated version:
Arduino ultra low power LCD (5uA) – 00:21
— NicolasVietnam

[pihome]

very first working Ethernet gateway

[Nca78]

Today I finished to fix failed soldering (too old solder paste made a mess ) on the "motherboard" of my air quality sensor.
It's based on ESP32, uses a charging IC with power path so it can run on batteries for around a day or stay plugged without destroying the battery, step down from USB/battery to get VCC, storage on I2C EEPROM, flash and/or µSD card (depending on use case), one SK6812 mini RGB led as indicator, a small 240*240 IPS LCD (backlight driven directly by ESP32 pin in high drive capability mode), a 3 way switch for basic user interface + footprint for PAJ7620 gesture recognition module, accelerometer and I2C IO expander to manage the 3 way switch and interrupts from sensor modules.
Sensor modules will be added on top, connected using an FPC connector. At the moment I made only one sensor PCB able to manage usual PM, CO2 and formaldehyde sensors. Only one sensor per sensor board where an attiny841 manages the UART sensor and convert it to I2C, it also manages the 5V step up to power the sensor.
On the main board I also added an NRF24 footprint so with the same PCB I will be able to make a gateway with integrated battery backup.

I'm pretty happy with the relatively well aligned components (no, I don't have OCD ) , too bad I had to unsolder, clean and re-solder each component as it now looks botched up. But at least everything (except a missing connection on µSD card, hence the blue wire) is working,

LCD test showing jpgs from SD card

[berkseo]

My new mini multi device on nRF52810, nRF52811, nRF52832 chips. Designed specifically for a very small case from Aliexpress. It works!!!

bme280, sht20/21, si7020/si7021, hdc1080, max40009, lis2dw12, lis2dh12, lmt01, reed switch, led + rgb led, user button and 6 analog pins, 6 digital pins with NFC.

VIDEO:
Mini multi-sensor in a small case. New Happy node mode test. nRF52 – 03:29
— Andrew EfektaSB

[sundberg84]

Today I designed a case for EasyPCB with 2xAA holder on the back.

and a case that slides just over.

It works with 3x5 version so for this you accually have to use the more advanced option and reflash the fuses on your pro mini to make it 3x5. The normal EasyPCB with booster is 5x5, but Im thinking of just stretching this for another version.

[mfalkvidd]

@sundberg84 just a suggestion; wouldn't it be good to move the batteries to the right (instead of the left) so they block the nrf antenna less?

[sundberg84]

@mfalkvidd - a great suggestion! It wont not block it completely but as you say, a little less.

[NeverDie]

Here's another idea too: if you were to add a blank copper cladded FR4 between the batteries and the PCB above it, with a cut-out below where the antenna is, then maybe you'd have a much improved ground plane, making your radio awesome? You could have little drawer like grooves on the side of your case to slide the copper cladded FR4 into position, and, of course, you would want a ground connection to it.

[sundberg84]

Not sure about that groundplane @NeverDie - you are most probably right but I dont really understand the theory behind it but sounds really cool!

[NeverDie]

@sundberg84 Here's all the theory you need in one picture:

Most of the modules use a monopole antenna, and as near as I can tell, most of them, if not all of them, have insufficient ground plane. It still works, of course, but it's impaired over what it would be with a better ground plane. I think maybe that's why whenever someone switches to a dipole antenna they generally notice a huge improvement. So, there's always that, but your design is nice because it's so compact, and a dipole would spoil that.

[sundberg84]

@NeverDie - so a ground plane like in here? Like that mod Pete did in his video but you inmplement it into the 3d case?

[NeverDie]

Yeah, the flat piece that the red line points to. I'm not sure what those black spray painted things are, so I'm ignoring those.

[NeverDie]

Made a dead-bug op-amp circuit to help measure open-circuit voltages created by nano-amp currents generated by a solar cell illuminated by just 1 lux of very dim light:

This picture is actually just the LDO part of the op-amp circuit, where I was able to solder the prescribed surface mount capacitors directly between its pins. The larger circuit is described on this thread: https://forum.mysensors.org/topic/10812/the-harvester-ultimate-power-supply-for-the-raybeacon-dk/122
Why dead-bug you ask? Since the circuit depends on the correct measurement of the effects of mere nanoamps, I didn't want any leakage currents that might happen on a protoboard, which can be significant when it's just a small number of nanoamps and their effects that's under scrutiny.

[sundberg84]

Updated my GW with the code @mfalkvidd provided to monitor OK and NACK

[nagelc]

I got tired of twisting DuPont cabels to get from different programmers to different boards.
This is an adapter that lets me connect the programmers I commonly use (Jlink-mini, BMP, STLink clone) with the boards I commonly program with straight through wires. I left a couple unpopulated for future in and out.

[tbowmo]

Finally I am starting to do a little electronics again.. First thing is a prototype assembly of RASLE (Rpi Arcade Sound and Light Extension). It's a custom made arduino "coprocessor" for a raspberry pi, built into retropie arcade cabinets. It's a joint project with a couple of friends that are building arcade cabinets (I built mine a couple of years ago, I think that there is pictures earlier in this thread).

Features:

• stereo 3W class-d amplifier
• atmega328p
  • 3 pwm channels for LED strips
  • a port for WS2812 type led strips
  • pwm channel for fan
  • output for a relay to control mains input for the box (let the rpi shutdown cleanly, before disconnecting power)
  • 5 button inputs (shared between rpi and atmega)

[franz-unix]

Hi, finished two nodes based on the same multi-purpose battery powered pcb (all the documentation here)

One is a door / window sensor based on a Reed switch.

If someone is interested, the dedicated wiki page contains the detailed build instructions.

The other is a soil moisture sensor.

For this one, the wiki page is here.

Happy Easter, even if at home!

[NeverDie]

Anyone know or have experience with how well the underlying capacitive soil moisture sensors hold up over the long term? Clearly they're better than the cheap conductive electrode kind, which for most people don't last very long at all, but I recollect reading that water ultimately invades the PCB enough on even the capacitive designs that it goes kaput. Maybe they've been improved since then or maybe there are now known tricks for how to fortify them against that happening?

[franz-unix]

@NeverDie Good question. My is too young (2 days) to say something.

Here a possible solution. See at about 9:50

[BearWithBeard]

@NeverDie The guy with the swiss accent once said that you can coat the capacitive soil moisture sensors with a water resistant varnish or put it inside a waterproof shell.

https://www.youtube.com/watch?v=udmJyncDvw0
starting at ~7 mins.

@franz-unix Ha, Great minds think alike.

[franz-unix]

@BearWithBeard I love the video of the swiss guy!

[Yveaux]

@BearWithBeard ah, now I know who 'the guy with the Swiss accent' is

[sundberg84]

Today I have a very strange problem. I have created a new outdoor sensor which is powered by a 240v-5v HLK module. Its working VERY intermittent and should send data every 5 minutes (no exceptions).

Whats even more strange is that, when my outside node (called multi) is working, I have a battery powered node (sleep 15 min - send - sleep) that seems to go down, and the other way around (not always, but quite frequent - could be very unrelated but I have notised it a couple of times now).

Anyhow, Im very glad i build my logger node - works great once more. I use this so often and really recommend all with a bigger network to have some sort of mobile debugger. Most of the times I use the bluetooth module (2xAA powered) but at this point I have my node on my workbench powered by a USB adapter (orange wires). I then parasite power from the node to run the debugger and is now logging everything to a sd-card.

[mfalkvidd]

In case anyone hasn't seen the logger before, it is available at https://www.openhardware.io/view/532/The-Logger-Machine-Short-and-long-term-serial-logging

[sundberg84]

Another picture from today:

Just started working with coincells - CR2032 to be exact. Anyone knows why the battery % varies with the given temperature? Are those coincells very temp. dependent or I have made a misstake somewhere... ???

[Nca78]

@sundberg84 said in What did you build today (Pictures) ?:

Anyone knows why the battery % varies with the given temperature

They don't like it when it's too cold. Check page 4 :
https://data.energizer.com/pdfs/lithiumcoin_appman.pdf

[Yveaux]

@sundberg84 looks like you can ditch the temperarure sensor and just use the battery voltage to measure the temperature

[cloolalang]

433 MHz ESP 32 MQTT Gateway with proper antenna

[sundberg84]

@Nca78 - Well, its been around 14-17dgr C today, so almost room temp. Strange
@Yveaux - hahaha, best answer! Saving uA!

[idanronen]

@NeverDie sorry if it's a bit off topic, but I see that 10 pin ARM box connector you use in several of your designs, and I was wondering if it offers anything extra in addition to the regular 6 pin programming pins. I'm asking specifically because I want to try some of your nrf52832 designs, but would like to avoid spending extra money on special connectors and cables. Thanks!

[NeverDie]

@idanronen No, nothing extra. It just conveniently and transparently interfaces to the ribbon adapter cable used by the Nordic nrf52 dev kits for programming external nRF52 MCU's. If you want to roll-your-own, you can do away with most of the pins. I myself migrated to a smaller connector in later designs.

[idanronen]

@NeverDie thanks for clarifying!
So for example in the mini breakout board (https://www.openhardware.io/view/471/Ebyte-nRF52832-Small-Breakout-Board) I could just align the 6 pads and use a standard 6 pin pogo programmer right?

[NeverDie]

@idanronen Yup. If you have more questions, you should probably ask them on a different thread than this one, as it's off topic here.

[monte]

Offtopic in terms of mysensors platform, but somehow tangent to a home automation. I've made a batch of concrete switches/push buttons which are in this case simple buttons with led backlight and all the logic is located centrally in distribution box, based on KNX ABB module. But I am planning on making smarter and more complex version which could use Mysensors as its transport.


and a photo of insides of one of the prototypes at first stages of development

[MatiasV]

@monte Nice work! I love the looks of the concrete switches, do you have some links or useful information on how you did it.
I have a project of a doorbell that could use such a switch.

Thanks!

[NeverDie]

@monte It's a real pleasure to see such professional looking design!

I'm curious though: the button in your teardown looks clear:

so how does it turn black and give the solar eclipse effect? I mean, I can see the 4 LED's that comprise the "sun," but how does the button (the "moon" in this analogy) go from clear to black?

[monte]

@NeverDie tanks for describing it as "professional":)
The clear button on the last photo was one of prototypes as I've mentioned, frankly process of refining the button part to make it work as it should was the longest part of the development. Now it is made in two stages: at first the transparent acrylic part is cut on laser machine, then it placed into a mold with curing mix of resin and concrete, which makes it's black top layer that blocks the light from below. 3mm acrylic base and 2mm resin top layer.
But I have to say that next batches will be made the other way, which is already in my mind:)

@MatiasV thanks! Well, I coluld describe the whole process of making, but it requires a lot of work like making propper mold, the process of trial and error while trying to achieve consistant pour and at last the complex process of making a button that would work without sticking.
Frankly I don't think it's worth time and effort if you plan tho do only one switch for yourself. But I can give you hints about concrete mixture and other stuff, if you're just interested in it's concrete part.

[NeverDie]

@monte Now that you've mastered the medium you can cast your own tile to texture a wall:

I met a local architect who did such a thing for her own home. She only had to create a handful of different molds, and then random placement gave the illusion of more than that. Maybe they could be secret panels for hiding all your home automation control equipment behind. High WAF that would be.

[tbowmo]

Just made a fun (and useful) sensor / device, using a arduino pro-micro (atmega32u4), and VL53L01 TOF distance sensor.

It's an auto lock device for my pc, I have mounted the VL53L01 to the bottom of my center monitor, and then have it measure the distance to my body, whenever it exceeds 1m (or is out of range), I increase a counter. When the counter reaches 20 (seconds) I send keypress GUI+L, to lock the screen (works equally well on ubuntu and windows).

When I return to the desk again, it is detected by the arduino (distance is now under 1m again). And it then sends CTRL+ALT+DEL to start login procedure.

The arduino sketch is available on https://gist.github.com/tbowmo/7e9934796d47566dc09e7b3bc5b2f208

next project should probably be to find a better enclosure, and build one for when I return to the office in a month or two, when the corona lockdown is lifted more

[Luiz Carlos]

@sundberg84

I finished my fully functional panel for domoticz, using Display Nextion ...

I don't know where to post, sorry !!! lol

[sundberg84]

Interupted by our first "Summer" lightning, but in replacing my old Rfm69 gateway (old one works, but uses a ftdi adapter for Serial communication and i have another need for the adapter). In the same time im taking up signing. The node has a atsha chip but I never used it properly which im going to try to fix.

[franz-unix]

Hi guys,

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.

[berkseo]

@NeverDie My experience shows that the Chinese sensors that are sold on Aliexpress have a low quality printed circuit Board. When used outdoors, they may deteriorate within 1-2 seasons. Inside the house, in a flower pot, the service life is much longer. As for such sensors developed independently, the quality of printed circuit boards that are ordered through the services of jlcpcb, pcbway... very high.

[Avamander]

@NeverDie I personally took a bottle of nail polish and coated every sensor I had. I had a hunch that moisture seeping might affect the capacitive sensors so I took precautions. They've lasted a year now with no sign of deteriorating.

[NeverDie]

Thanks! Earlier in 2020 I started a shoot-out of different weatherproofing coatings, and I can already see that Spray Max 680061 is by far performing the best out of all the hard coatings that I tried: https://www.spraymax.com/en/products/product/clear-coats-and-spot-blender/2k-clear-coat/ So, for that reason, I suspect it would also perform very well at moisture proofing capacitive PCB soil probes.

[NeverDie]

I built a picoamp current source and tested a picoammeter that I built from Gyro's design that was posted on the EEVblog forum. It turns out it can measure even single digit picoamps to an accuracy of less than a picoamp (i.e. less than one trillionth of an amp!)

https://www.eevblog.com/forum/beginners/static-control-requirements-for-picoamp-measurements-using-ucurrent-gold/msg3101836/#msg3101836

[boozz]

Today I finally found some time to put a few modules together.
A cheap solar cell (€1.35 a piece) with recharcheable battery which feeds via a step-up converter (€0.70 /pc) a pro-mini (5VDC). The DS18B20 is read every 5 minutes.
Now I’m Interested how long this sensor will do its job.

[berkseo]

Hi, everybody. Yesterday I made a case for my new device with an e-ink display 2.7. the Case turned out to be quite thin. The dimensions of the device in the case are 86.5 mm X 59.5 mm X 11.5 mm. The new device is a continuation of the project - https://www.openhardware.io/view/629/EFEKTA-TempandHum-sensorver-nRF52-E-Ink-display

[alowhum]

Man, things are starting to look very professional around here.

[monte]

Made a prototype board for writing a software for one of my projects. Goal was to have everything needed on a board no bigger then a 1.54" eink display, and to make it doable at home by my own.
I was gladly surprised that everything worked (after a sleepless night of fighting through-layer connections, and soldering/desoldering FPC connectors) The only I've messed up is order of connector pins, so the display is connected the wrong way...

It also has pads for SHT30 sensor so it may be somehow useful after development is done.

[berkseo]

@monte said in What did you build today (Pictures) ?:

FPC

Excellent handwork. I also dealt with such FPC conectors :), here are the correct FPC conectors - https://aliexpress.ru/item/32794813863.html

[monte]

@berkseo Thanks!
Link doesn't open. I have the right ones, I've just messed up PCB layout. Somehow pins on the board goes in the wrong direction, so the most left pin is #24 instead of #1

[berkseo]

@monte fixed the link, html.... not htm

[berkseo]

@monte By the way, this version of screens is discontinued, it is better to develop software for new versions

[monte]

@berkseo thanks for mentioning that. But as I understand the change in software would be just including another header file, if I'm using GxEPD library. There is a mention on github that there is GDEH0154D67 model as a replacement for GDEP015OC. Or do you mean that they are discontinuing 1.54" displays completely?

[berkseo]

@monte said in What did you build today (Pictures) ?:

Or do you mean that they are discontinuing 1.54" displays completely?

Yes, I mean that these displays are no longer produced. And it is better to focus on new ones.