Topics created by dakipro

If anyone is trying the same, I did it as @mfalkvidd recommended, with several child IDs Then I basically reset the message if data comes on on first childId, and only append it if data comes on any other sensor, something like if (message.sensor == messageCHILD1){ strcpy(newMessage, " "); // we put some spaces in front strcat(newMessage, message.getString()); }else{ if(curMessage!=""){ // append existing message to newMessage strcpy(newMessage, curMessage); } //append rest strcat(newMessage, message.getString()); } Note: the code also works with just two sensors, first for reset, and second that only appends data, but I decided to go with four child IDs, in case there is something I am not seeing at the moment. Thanks everyone for ideas

@parachutesj that sound a reasonable approach

One of the things I do at work is to manage the disposal of old computers and electronics. As part of that I often find different multi pin dupont headers like these, usually with a bit of cable already on them. I sometimes salvage these from the e-waste and add them to my parts bin. Just one of the things that I like about my job.

At these prices, I ordered a couple of them, just because all the cool kids have them I was thinking, that (on top of all already ambitious functionality) it would be nice to have a Firmware over the air functionality wouldn't it, as I am certainly going to need to debug and fix the code... So in the end I might split the functionality in two/three pro minis, or if I manage to make Mega do FOTA (didn't find much info about someone doing it already). But then there is maybe issue with proximity of the radios in the box which is an old round lamp, radius 10ish cm. I guess I will have to wait for the boards to see how will it all fit together...

Referencing the enhancement request on https://github.com/mysensors/NodeManager/issues/233 Thanks!

Then I have an "alarm" flow in node-red (via openhab) which blinks all lights in the house, sends notification to mobile phones with high priority etc. Which brings me a lot of joy when all works fine (and annoys my wife, as usual)...

Success! @sundberg84 and @Nca78 you will be proud of me when I tell you that I was doing everything "correct" all the time, it is just that arudino IDE had some stupid bug or something. I had to delete everything mentioning Arduino from the pc, and reinstall the IDE, and now all works as expected! It was a stupid thing hunting me for year(s) now that I think about it. I always assumed that ftdi cannot be used with other then the original bootloader, because of stupid error noone ever heard about At the end, I used this repo https://github.com/joe-speedboat/Arduino-LowPower and added new definitions in the boards.txt, then copied relevant bootloaders (and files in "variants" folder). And repeated all the steps above, and everything works great now. I have a 1mhz arduino blinking correctly, and going down to 1.8v, and sending correct temperatures and all Life is worth living again!

Thanks, I will most likely do it like you are suggesting. About reset, you mean setting it to "off" state after click or? The code above sends only one action per press, so it is either as "click", or a "double click" or a "hold released" (you can even send a "hold started" and "I'm holding...I'm holding...I'm holding...I'm holding..." events, but I do not need them for now). All the logic about counting etc is nicely handled by the OneButtonLibrary, it works much much better then the other solutions I found on the net (I even started writing my own logic, but being somewhat "experienced" developer I figured that someone has allready tested it better then me, and I was right ) I use domoticz as controller and it has option for the "contact" type of switch, which gets triggererd each time I press the button/send the ON state. It works nice so far, so I wasn't going much into details about hows and whys

Powering sketch off and on again began the "booting-upgrading procedure". Which unfortunately got messed up somehow (I suspect some other node on the network was interrupting constantly). Node suddenly not visible to the mysensors network, restarting or rebooting, it didn't start. probably i messed up the loader or something, don't know how I did it. I however managed to access the board and reflash mysbootloader and then was able to upload sketch with the wait() at the end. This update process was stuck in the loop, but then I turned off some of the universal sensor nodes, the update finished successfully. Not sure how, but I keep messing things up somehow, good news is that eventually I learn a bit more each time Thanks for the help

@m26872 I agree with you about the wired connection, unfortunately in the apartment I rent now we have one switch in the middle of the apartment that controls five light bulbs in two different rooms (don't ask why), so running the cables trough whole apartment is just not practical. Which is the main reason I am motivated to MySensorify it all, it takes too much walking around for the light switch and too much hitting the door and the cat in the night. @fets Exactly, I found that method/setter in API and got inspired to go around/parallell of the controller. The sketch logic would be then: -- Switches On Click: sends message to Lights Control Node with its SwitchNodeID and SwitchAction (NodeID is sent automatically if I read API right?) -- Ligts Control Node On Message Received: Do some if else based on the SwitchNodeId and SwitchAction and send "Toggle" message to desired light or group of lights. (Right now I am a bit concerned whether to send the toggle message or on/off, as controller can get lights out of sync by running some automatic script. Not sure how to handle this yet, probably by always running some lights in the group-only (living room lights, bedroom etc)) -- Light nodes On Message Received (both from "Lights control node" and domoticz): do what it says in the message and report your status back to domoticz. I just started with MySensors and arduino programming (I do some programming in php). I will have some time now during the hollidays to play around, but do you guys see any challenges in this code and design logic? Something that could be difficult/impossible due to some design or code limitations? I guess switches and the Lights control node need to be presented to the gateway and the controller, which can then just ignore them. Also, which message should I send from switches and Lights control node, S_LIGHTS or some custom variable? Does anyone have some example of node-to-node communication and sending the messages between? I think I saw something on the forum about weather station but I cannot find it now

Thanks, I tried running it on old laptop, but it was difficult for non-russian speaker to figure things out. And I remember that the app was constantly using around 30% of CPU which kept the fan running all the time (because php was running in infinitive loop). I switched to domoticz on raspberry, but have now settled on openhab and am very happy with it. None of them used more then 1-2% cpu on same laptop, and both are very stable (also easy to find documentation for english-speaking user).

Yeah, makes sense... I guess then that z-wave it is for controlling 220v. I have read that 433mhz usually doesn't have two way communication, which is inconvenient for reliable setups (state of main lights etc). And z-wave is not quite cheap setup. I am planning to use MajorDoMo controller, they support Z-Stick and raZbery as gateway. What would be the cheapest and minimum z-wave setup for turning on/off (and maybe dimming) the lights? So far I've found f.eks. z-stick https://www.m.nu/zwaveme-stick-p-1778.html for 35ish euro and popular Fibaro WALL PLUG FGWPF-102 for 60ish eur. Would that be minimum that I need to hook up to a pc running a controller that supports z-wave? Than it would be about 60euro for every new light/switch (vs 6 eur for one risky diy). Being a cheap guy I must ask, is there any cheaper certified alternative?