@AWI Is this code for version 1.5?
Im trying to compile it for the dev (v2) but i get a lot of errors.
Mostly alot of code that "was not declared in this scope".

EDIT: Just found your link to the "Conversion guide", will have look at it!

@mfalkvidd I use those touch modules on every node that needs a button, i did have a node with haptic feedback. I just used an iphone vibrator and sent a short pulse to it when one of the touchbuttons was pressed.

Im just about to finish this one, i use a black (transparrent) acrylic plate with touchmodules and LCD behind the acrylic.

@blebbens said:

I take a look at domoticz, never heard of it.

I found mysensors page of controllers and those screenshots. Those screenshots do not tell me how easy it is to use the software. They also do not tell me if I have to be able to program it by myself. Seeing OpenHAB screenshots, I thought they give me a nice GUI, but there I have to create the whole interface by myself from the beginning without some sort of settings etc.

Hope, domoticz, vera or PiMatic are different. Does anybody use a controller without programming skills?

When you add your gateway as "hardware" in domoticz and connect your nodes they will be discovered by domoticz.
In your device list all the childs of every node will be listed and with one click you can add them to the system.

Here you can see my latest mysensors node that was added yesterday, if you click the green arrow you can add the child to your system.

Here is one of my scenes that activate some of my mysensors moodlights, "Fargelys", and the two "RGB Stue" devices is mysensors nodes. You can set the level (if its dimmers) and on/off delays).
You can also press the "Add device" if you want a button, scenecontroller, motion detector etc to activate the scene.

You can use blockly to do some logic, in the example under a device that was named "16" (used to be my livingroom lights) is turned off when i start a movie in kodi.

This looks realy nice, but isnt the thermal fuse supposed to be glued to the hi-link?

@AWI
Amasing! I have been using your v1 sketch on 5 different nodes.
I was just about to make another one when i saw that you had released another version.

I have made a similar hack to your v1 with a dimmer/selector switch in domoticz as pattern selector. But your code looks way better

I cant belive i missed this topic. Count me in next time, a perfect time to drop the kids off at their grandparents house in falkenberg on the way down and take home some cheap bacon, beer and sigaretts on the way home (norway) Its a win, win, win situation.

A bit dissapointed that the bbq was not rigged with mysensors hehe

@AWI The code is from the MySensors examples and i use it to control 3 mosfets that controls a ledstrip.

I need the heartbeat because i use the RPi gateway with the NRF24 chip directly connected to the RPi, and the gateway software for the raspberry dont store the network map so if i reboot the RPi the nodes loose connection to the gateway.

Isnt the only difference the cpu and the amount of RAM?

The one with more RAM is slightly thicker (but also a bit cheaper), so it all comes down to size vs some extra ram.

@TheoL said:

I would strip the complete sketch and leave only the button part in it. That way it's much easier to detect if there's any mistake. It's really hard to help you with a sketch if this size.

You could try to give the debouncer a higher interval, e.g.:
debouncer2.interval(25);

Thanks for the troubleshooting tip!

@mfalkvidd After commenting out almost all of the LCD/temp functions i was left with the last wait that caused the problems, it seems to be working now but havent got the time to run it more than a few minutes.

Does anyone have info on how to wire the GP2Y1010AU0F?

My cable is almost the same as on the picture https://www.mysensors.org/build/dust

The red, black and yellow is in the same place, but from there it goes white, green, blue.

EDIT: Found that Red is vcc, black is signal and yellow is ground.
Do this sensor need calibration?
And what is considered a high value for dust?

And is it only those three wires that needs to be connected to the arduino? Not the led?

@AWI has a nice piece of code that is exactly what you are looking for, try searching for mood light here on the forum.

Today i received 2 pcs Ultrasonic Mist Makers, i already have mysensors nodes in some of my plants with ws2811 RGB strips.

Now i want that fog effect! Has anyone tried these mistmakers?
I tried to find some wiring guides but i have not found one yet, i think its 12V.

Do i need any other parts for these to make mist? Or is it just to hook them up to a powersupply and controll it with a zwave wallplug or arduino with an transistor?

http://www.ebay.com/itm/Ultrasonic-Mist-Maker-D20mm-Atomizing-Transducer-Ceramic-Humidifier-Accessories/381768814890

Good evening!

As the number of nodes keeps incresing my need for 5v powersupply increses.

Right now i am building a node with a ws2811 led strip, but my powersupply gives me 5.3v.
It seems that my leds dont like the extra 0.3v, how can i adjust the output of my powersupply (generic wall-plug-powersupply)?

I have lots of resistors, transistors(mosfet), logic level shifters (5-3.3v) etc laying around, is it possible to make something or should i just buy a new powersupply?

@AWI
Amasing! I have been using your v1 sketch on 5 different nodes.
I was just about to make another one when i saw that you had released another version.

I have made a similar hack to your v1 with a dimmer/selector switch in domoticz as pattern selector. But your code looks way better

Suddenly my MySensors network has crashed

My setup:
MySensors v2.0
Raspberry PI 2 (OS: OSMC/debian jessie, controller: Domoticz)
10 Nodes
Serial gateway (arduino nano)

A few days ago my MySensors networkk stopped responding, i dont realy know where to start troubleshooting and if its possible to see any Gateway logs on my RPi?

I can see some errors on the RPi:

[    5.529590] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[    5.529857] systemd[1]: Found ordering cycle on basic.target/start
[    5.529880] systemd[1]: Found dependency on sysinit.target/start
[    5.529901] systemd[1]: Found dependency on apparmor.service/start
[    5.529920] systemd[1]: Found dependency on remote-fs.target/start
[    5.529937] systemd[1]: Found dependency on remote-fs-pre.target/start
[    5.529953] systemd[1]: Found dependency on connman.service/start
[    5.529970] systemd[1]: Found dependency on dbus.service/start
[    5.529987] systemd[1]: Found dependency on basic.target/start
[    5.530006] systemd[1]: Breaking ordering cycle by deleting job apparmor.service/start
[    5.530027] systemd[1]: Job apparmor.service/start deleted to break ordering cycle starting with basic.target/start
[    5.530323] systemd[1]: Found ordering cycle on basic.target/start
[    5.530345] systemd[1]: Found dependency on sysinit.target/start
[    5.530364] systemd[1]: Found dependency on kbd.service/start
[    5.530382] systemd[1]: Found dependency on remote-fs.target/start
[    5.530399] systemd[1]: Found dependency on remote-fs-pre.target/start
[    5.530416] systemd[1]: Found dependency on connman.service/start
[    5.530432] systemd[1]: Found dependency on dbus.service/start
[    5.530449] systemd[1]: Found dependency on basic.target/start
[    5.530466] systemd[1]: Breaking ordering cycle by deleting job kbd.service/start
[    5.530485] systemd[1]: Job kbd.service/start deleted to break ordering cycle starting with basic.target/start
[    5.530599] systemd[1]: Found ordering cycle on basic.target/start
[    5.530618] systemd[1]: Found dependency on sysinit.target/start
[    5.530636] systemd[1]: Found dependency on rpcbind.service/start
[    5.530655] systemd[1]: Found dependency on network-online.target/start
[    5.530672] systemd[1]: Found dependency on network.target/start
[    5.530688] systemd[1]: Found dependency on connman.service/start
[    5.530705] systemd[1]: Found dependency on dbus.service/start
[    5.530721] systemd[1]: Found dependency on basic.target/start
[    5.530738] systemd[1]: Breaking ordering cycle by deleting job rpcbind.service/start
[    5.530758] systemd[1]: Job rpcbind.service/start deleted to break ordering cycle starting with basic.target/start
[    5.679174] fuse init (API version 7.23)
[    5.701175] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    5.728290] i2c /dev entries driver
[    5.733286] bcm2708_i2c 3f804000.i2c: BSC1 Controller at 0x3f804000 (irq 83) (baudrate 100000)
[    5.738096] systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
[    5.740561] systemd[1]: Failed to start Load Kernel Modules.
[    5.740793] systemd[1]: Unit systemd-modules-load.service entered failed state.
[    6.070440] systemd-udevd[198]: starting version 215
[    6.298370] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    6.330031] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    6.499883] usbcore: registered new interface driver usbserial
[    6.499996] usbcore: registered new interface driver usbserial_generic
[    6.500115] usbserial: USB Serial support registered for generic
[    6.502689] usbcore: registered new interface driver ch341
[    6.502800] usbserial: USB Serial support registered for ch341-uart
[    6.502946] ch341 1-1.3:1.0: ch341-uart converter detected
[    6.506979] usb 1-1.3: ch341-uart converter now attached to ttyUSB0
[    6.507114] ch341 1-1.4:1.0: ch341-uart converter detected
[    6.511244] usb 1-1.4: ch341-uart converter now attached to ttyUSB1
[    6.779200] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[    7.871057] systemd-journald[193]: Received request to flush runtime journal from PID 1
[    8.649890] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    8.650159] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   10.109285] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   10.110614] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[   10.140762] 8021q: 802.1Q VLAN Support v1.8
[   10.259892] random: nonblocking pool is initialized
[   13.031131] smsc95xx 1-1.1:1.0 eth0: link down
[   14.519466] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[   15.618347] Console: switching to colour dummy device 80x30
[97628.494454] Console: switching to colour frame buffer device 240x67
[97630.022871] Console: switching to colour dummy device 80x30
[592849.839421] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[592849.839542] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[592849.839621] ch341-uart ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32
[592850.032947] usb 1-1.3: USB disconnect, device number 5
[592850.034342] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[592850.034534] ch341 1-1.3:1.0: device disconnected
[592853.089143] usb 1-1.3: new full-speed USB device number 7 using dwc_otg
[592853.192492] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523
[592853.192531] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[592853.192551] usb 1-1.3: Product: USB2.0-Serial
[592853.194402] ch341 1-1.3:1.0: ch341-uart converter detected
[592853.199751] usb 1-1.3: ch341-uart converter now attached to ttyUSB0
[592857.035394] ch341-uart ttyUSB1: usb_serial_generic_read_bulk_callback - urb stopped: -32
[592857.035569] ch341-uart ttyUSB1: usb_serial_generic_read_bulk_callback - urb stopped: -32
[592857.201899] usb 1-1.4: USB disconnect, device number 6
[592857.203137] ch341-uart ttyUSB1: ch341-uart converter now disconnected from ttyUSB1
[592857.203218] ch341 1-1.4:1.0: device disconnected
[592857.439203] usb 1-1.4: new full-speed USB device number 8 using dwc_otg
[592857.542421] usb 1-1.4: New USB device found, idVendor=1a86, idProduct=7523
[592857.542448] usb 1-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[592857.542462] usb 1-1.4: Product: USB2.0-Serial
[592857.543776] ch341 1-1.4:1.0: ch341-uart converter detected
[592857.547777] usb 1-1.4: ch341-uart converter now attached to ttyUSB1
[592861.554465] usb 1-1.4: USB disconnect, device number 8
[592861.555543] ch341-uart ttyUSB1: ch341-uart converter now disconnected from ttyUSB1
[592861.555680] ch341 1-1.4:1.0: device disconnected
[592864.089163] usb 1-1.4: new full-speed USB device number 9 using dwc_otg
[592864.192309] usb 1-1.4: New USB device found, idVendor=1a86, idProduct=7523
[592864.192338] usb 1-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[592864.192350] usb 1-1.4: Product: USB2.0-Serial
[592864.193674] ch341 1-1.4:1.0: ch341-uart converter detected
[592864.198088] usb 1-1.4: ch341-uart converter now attached to ttyUSB1

This looks realy nice, but isnt the thermal fuse supposed to be glued to the hi-link?

@Lars65
Take a look here https://forum.mysensors.org/topic/1607/safe-in-wall-ac-to-dc-transformers

WHat kind of child do i need to use the selector switch in domoticz?

Im also trying to make a node that can activate different effects on a ws2811 led strip.

@tante-ju Some sort of cache problem? I had a similar issue with the beta, i used the clear eeprom sketch on the node and set a different node id manually and fixed it.

EDIT: Had the same problem now with the v2 release, clear eeprom on the node solved it