General Discussion

Does adding ack to messages help trigger any failures if something can't deliver? ... well that didn't make much sense. So lets say i have 2 repeaters on my network. i have a sensor that wakes up to report info. it normally goes to repeater1 -> gateway but repeater1 is acting up. Could you tell it to wait for an ack? after X amount of time with no ack would it trigger to find a new parent?

Hi, wow, quick answer. I'm on the way right now, I'm testing it Friday. (It would be a real shame to take softspi by this controller. ;-) ) Thank you, hyx

@sigolhi Yes, communication between two nodes is possible without a controller and gateway. I do this. And I tie them to each other in the air, it is not necessary to prescribe in the sketches. See my videos in this topic. Carefully look :) Master - Slave Сommunication | Micro Network

You should do the same for requestTime();

@chisight Thanks for the idea, I'll keep it in mind but for this project some of the relays will be controlling lights etc, so minimum delay is desireable. Thanks.

@hard-shovel Thanks for the response. The volume control is motorised so no need to 'remember' where it is as it is possible to manually change it and there is no feedback that could be used to determine changes. The remote control requires you to hold the volume buttons (+&-) down until desired volume level is achieved so I suppose I could start repeating the IRSend code from the node if one valid volune command is received. The first time the node gets a valid volume command it just repeates the send over and over until it gets another identical command which stops the loop. I'll think more about it and also see if the controller has something that might be suitable. Edit - Why not just start the volume repeating the code to go in whatever direction you want at a suitable speed and add a volume 'Stop' button - that would be easier! - I think I'll try that at the weekend...... ;) Thanks again, I can finally start hiding all the remotes cluttering up the place! :)

Duh .. . yeah . ... like @skywatch said.

@Johhnywalter I don't have equipment to test this, sorry. I only wanted an indication of the level of dust in a bedroom. But for now I have shelved this as I have more ijmportant things to take care of.

Thanks for some interesting info! The reason is 1. To save memory for adding more sensors, signing etc and 2. To save battery energy on battery nodes. So there is likely more than one solution to this problem. Also, I have used 'for' loops as well and wonder how this affects memory and battery drain? Thanks

I made heating as simply as possible - with good house insulation ( 20cm foam PVC for walls and 40 cm for roof ). I am using el. floor heating ( cables ) on both floors + fireplace like backup for unpredicable situations and for fun. I know, that heating cost me 2 or 3 times more than with heatpump, but consuption is low and investition was really very low too. ( cca 600 euros all heating cables and I made all work myself ) Regulation in this time ( and last winter ) by cheap Wemos with relay board and ESPeasy firmware on it in each room. It can regulate room or floor temperature ( I am using floor temperature regulation ) . Mode of operation and temperature setting are made from Domoticz, but regulation is made by Wemos itself - not running Domoticz needed. Temperatures and energy consumption are reported back to Domoticz. It was very funny two weekends project. One weekend familiarization with ESPeasy and next weekend regulator and Domoticz integration making. But it is not final stage, because ESP is very energy "hungry" and 4 lines of my UTP cable is not enough for cca 7 Wemos with relays on each part of bus. And I do not want wi-fi using for my sensors. But I need quick solution and it was.

@alowhum Zigbee being "a standard" is not an advantage at all. As you put it, it is indeed not true at all. Using "a standard" in the meaning of "a formal definition of one of the piece of your puzzle" is only an advantage when you want to potentially replace that piece by a piece produced by another manufacturer and still get that talking to the rest of the puzzle. You should also consider that there are two kind of standards : "committee" standards, where experts provide a formal document and people pay to adopt that way of doing things, and "de facto" standard, where there are enough users that do things the same way (or buy the same thing) that it guarantees sufficient resiliency. For example, USB is a committee standard (but if you use A, micro, mini etc. you have to adapt), Arduino Uno is a de facto standard (and there as well, you can choose between Uno or micro, etc.), and its success made possible the clones costing a few bucks.

You can buy on LCSC also, I bought a bunch of components there together with PCB (at jlcpcb, same company), price is not as low as AliExpress (and some US components are even more expensive than legit sellers like Arrows) but they have a lot of things at "Chinese price" that you can get all at once. I found a few things like connectors, battery protection IC etc that are hard to find or expensive on Ali/Ebay.

Thanks. Unfortunately, none of those resources had the part identifiers for the parts that I have. So, lesson learned: I'll create my own ID catalog every time I buy a receive a new part. That way, if need be, I can identify it later.

@akya the number of times you can read a DHT11 in a given time period isn't limited. You can read as fast as you want. The limit widely mentioned (at various rates of around once every 2 seconds) has to do with the heating effect of turning on current to the temperature sensitive resistor to take a reading. Someone tested and noticed that reading at high speed caused a slightly elevated temperature reading. You can test for yourself and see at what read rate you notice an increase, or just limit to once every 2 seconds or less.

I'm using them, I got the ones from soshine and the stated capacity is just a little more than the one measured by the charger.

I'd check this out: https://forum.mysensors.org/topic/6528/mh-z19-co2-sensor/17

@รอเร-อ Then I suggest you please re-READ, and as I suggested, Google, as Abraham Lincoln once said, "Never believe absolutely everything you read on the Internet". The 5v is irrelevant other than the threshold voltage which registers as a HIGH to it's I2C control. The 3v3 as Master dictates the HIGH as a factor of it's VCC on the I2C bus. THAT is the issue. As Vcc is never absolutely accurate you may strike lucky on a 3v3, there again you might not, your choice... ;) EDIT - To avoid any confusion, what I am referring to here is conventional I2C system. The input HIGH for a 5v is say 0.7 of Vcc, so 3.5v is required on the 5v I2C line to register as a HIGH. Even if a 3.3v Arduino were to put full Vcc on the I2C line it is just below the threshold for the 5v device. That is where the factor I referred to comes in, and I read elsewhere it can be 0.6 but cannot recall which device that referred to. Hopefully that clarifies what I was referring to.

Thanks! I guess I'd love to see a big player create products that are open to tinkering.