Topics created by FotoFieber

@tbowmo @scalz @mfalkvidd Your patience is amazing...

Some more services disappearing, "Bonjour" alarm clock didn't even finish sending the kickstarter orders, and those who have received the product will soon get a brick (nice enclosure for a MySensors project, though ) https://www.gearbrain.com/bonjour-smart-alarm-clock-killed-2626720300.html Lima is also closing with only 2 weeks notice, their device was offering a "personnel cloud" service, if data is encrypted it's a short delay to save it https://www.zdnet.com/article/lima-closes-its-doors-personal-cloud-devices-will-cease-to-function/

What board do I pick in the Arduino IDE when I go to compile my code. It doesn't work if I pick DUE? Thanks.

Hi, The code that is here:"https://github.com/tbowmo/node-red-contrib-mysensors" as a problem with latest mysensors with arduino 1.6.13 and NodeRed v0.15.02. These line: pl = msg.nodeId + ";" + msg.childSensorId + ";" + msg.messageType + ";" + msg.ack + ";" + msg.subType + ";" + msg.payload; Should be: pl = msg.nodeId + ";" + msg.childSensorId + ";" + msg.messageType + ";" + msg.ack + ";" + msg.subType + ";" + msg.payload + "\n"; This way the message gets to the node, the first one doesn't get there. Thanks, Rui.

@hek said: Encryptions is relatively untested. And you did enable encryption on both gateway and node? Yes, I did enable that. My setup: a ) ESP8266 gateway b ) Sensebender Micro c ) Mega2560 Problem can be reproduced wiith both b and c. It is working with fixed PARENT_NODE_ID.

Yes depending on the controller (Arduino) you choose will determine the number of sensors or actions a node may support. I will take into consideration if the node can be hidden, or it needs to be small and/or presentable where it is going to be located. This may effect your choices for the controller. I will also look at the tasks I'm trying to accomplish for a given objective. Some tasks like knowing if a door or window is open or closed and a motion sensor may not play well with each other in a node. Determine if it is going to be using batteries or get power from my house curcit (for example via a wall wart). When determining the power source I will look at the tasks I have defined. One of the tasks could determine if you are able to resonable use batteries to power it. For example a task like knowing if a door or window is open or closed most likely will not be run on batteries. If using a battery you should put your controller and radio to sleep as long and often as you can. If you have to use a small controller then the number of interrupts available will be limited and most likely be one. Some tasks will use an interrupt to override the sleep timer, for example a motion sensor. If more then one task (like a motion sensor) needs an interrupt and you are using a small controller you will need to split it up to more then one node or redefine your objective. These are just some thoughts I have been running with for now. Any other persectives are greatly appreciated. There are several of you that have a lot more experience with this adventure then I do.

Hmm. that should't be included at all for MQTT gateways. Thanks for spotting. Or maybe I misunderstand what you're trying to do.. Please open a chat.

The nice thing about the MQTT Client Gateway form 1.4 was, that it was the controller too. If I need a controller, I will use node-red with the serial gateway. MQTT is then handled by node-red.

@mfalkvidd Thanks - you are on fire today (that was quick reply)!

Yes, this is a minimalistic NRF Arduion PCB: http://forum.mysensors.org/topic/595/pcb-boards-for-mysensors/11

@FotoFieber Cannot use MyMessage msg(CHILD_ID, V_VAR1); as this is not supported by Domoticz.

Checkout git stash and git merge...