Development

@Redferne Thanks. I'll check it out.

@bjacobse Yes, wdt business can be quite confusing :) Optiboot has a sophisticated wdt approach: wdt is only enabled if the MCU is reset externally (this is the case when you upload a new sketch from the IDE), in all other reset cases (i.e. watchdog-, brownout- and power-on reset), the wdt is disabled and optiboot directly hands over to the sketch. See here for the conditions: https://github.com/Optiboot/optiboot/blob/master/optiboot/bootloaders/optiboot/optiboot.c#L484-L485 And here it gets disabled: https://github.com/Optiboot/optiboot/blob/master/optiboot/bootloaders/optiboot/optiboot.c#L847 This also means that with optiboot, wdt is always disabled when the sketch starts (if WDON fuse is unset). And to give a heads up for the MYSBootloader 1.3 release: wdt will be on by default (at the moment 4s), and the user has to either disable or reset it in the sketch. This is a safety mechanism and the only way to remotely recover from a bad/faulty FW.

Please let me know when u have somthing... I will publish also if I'll make it work.

Two days ago i got two through the mailbox and two at the postal office.

@pixelmagic here you can find a description of the project @sincze is referring to : https://forum.mysensors.org/topic/4461/smartmeter-sensors

@korttoma said: Try running the "ClearEepromConfig" example sketch from MySensors examples and then try your sketch again. Might be that there is an old "NODE_ID" being used that is conflicting with another node. If you want to use static NODE_ID you should put the following before the MySensors.h include in your sketch: #define MY_NODE_ID 14 You are also stil missing the #define MY_RADIO_NRF24 Before the MySensors include that @hek pointed out. ^^ this - I've had this happen before (just last night actually) but i recalled from when it happened in the past, found out it was using a dupe ID, ran eeprom sketch.. good to go now.

Some weeks ago i recieved 2 promotion PCBs when I shopped at Itead... not knowing anything about them i googled and it was a project like that (not for mysensors though...)

I've now tried various algorithms. In all of these I set the oversampling of both temperature and pressure to 1 (no oversampling). Forced mode, with fixed 5mS delay between reads, Forced mode, with fixed 4mS delay between reads, Forced mode, with fixed 3mS delay between reads, Forced mode, with fixed 1mS delay between reads, Normal mode, set t_sb = 0.5 mS, waiting until status bit 3 = 0, read data, repeat Normal mode, set t_sb = 0.5 mS, waiting until status bit 3 = 0, read data, wait until status bit 3 = 1, repeat With each algorithm, I'd do 2000 reads. As I went through the above scenarios, the minimum and maximum readings (for both values) got farther and farter apart - ie: the range of values got larger. That was until #5, where it was slightly better then #1. The range with #6 was the least of all - in other words, algorithm 6 gave the most consistent readings (I should say the sensor is laying still throughout these tests). In #5, it took 6 seconds to make 2000 readings - or an ODR of about 333 hz. In #6, it took 12 seconds to make 2000 readings - or an ODR of 166 hz. Just what the datasheet said would be the maximum ODR. I have to assume with #5, about half the readings were done before the registers were updated. In other words, it was a waste of cpu time to make the reading.

@TheoL Hi. I think that a higher level of abstraction from the controller, and giving the node more personality suits better for me. Also I like reducing the unnecessary radio traffic. Let me explain something more my node. The node I'm working on it's basically a multiple actuator that abstracts from the code things like the number of relays or their behaviour. At the moment, you are forced to populate a collection for it to discover and work with a variable number of elements, but as soon as I can I'll find a way to inject that info and avoid altering the code. Perhaps something like espeasy does, rflink activates it's rf modules, or even through a variable from the controller (worst of cases) Now it does all those things but the timer shutdown. I'm a good C# programmer, but I admit that it'll be difficult for me to adapt to C++. I still do all the things as I was doing in C# I don't know anything about the scope or the behaviour of instantiated objects. I would like to tie a timer object to one element's property in the collection and let it run, but I don't know how, or if it will stay "alive" after the procedure ends :smirk:

@hek looks good...thanks for that ill investigate over the next week getting it running

@shabba thanks, main site matters I leave to @hek to decide upon.

understood. i just happened to already have these as 'extras', so i figured i'd build a node and give it a whirl. I'll definitely do some more research on @ceech his postings. thx for the insight

@martinus Anoying isn't it? I allways give a description for each child I present. E.g. gw.present( TEMP1_CHILD_ID, S_TEMP, "DHT1 sensor", true ); // present to controller gw.present( TEMP2_CHILD_ID, S_TEMP, "DHT2 sensor", true ); // present to controller By doing this I can see the description in Domoticz, so that I know what to add.

@kk02067 it will work fine without presentation

So I'm new to all this, however anytime I get funky things going on when I have multiple sensors on a node I found that introducing a delay in between the readings helped smooth things out. Hopefully someone will correct me if I'm wrong, but I have had some luck with delays. Also I built one to control my hot tub and I found noise from the pump messed things up, de-coupling capacitors became my friend after that.

@jj1990 Currently I don't think it's possible, there are too many dependencies on arduino. But the aim is that we separate those dependencies from the core. So we have a more portable codebase.

@mfalkvidd said: It depends on how much work you are prepared to do and how much flexibility you want in the code. If you only use one temperature sensor and don't have any plans to add more, change gw.send(msg.setSensor(i).set(temperature,1)); gw.send(msg.set(temperature,1)); Only using the ph sensor and 1 temperatuur sensor no need for more temp sensors.

@stofakiller I think that is supported but I don't know how to do it. Hopefully someone else can chip in.