Development

I usualy have it set at 10000. Give the network some time to connect.

Agree with @Yveaux. V_ARMED can be used in battery powered door sensors to preserve battery, or to reduce traffic. don't send V_TRIPPED if V_ARMED is not set. Sounding alarm is controller's decision.

@Sasquatch Thanks, it was a connection issue with HomeAssistant to MySensors GW. Now it is time to clean up the sketch and put it to operation again. Also thanks you other guys that have been helpful @mfalkvidd @Yveaux @niclas

@henk-herck - thanks for your reply and suggestions. I changed the pins to output and set them as high, but unfortunately it didn't change the outcome. In the end I soldered some wire into the OpenSprinkler's expansion board to help me get to that row of pins which allowed me to work around my issue. I'd never really looked at the Orange Pi range before and went a bit down a rabbit hole looking at them yesterday. They're quite interesting and I'll look into them a bit more today.

@henk-herck said in Why is stropts.h included ?: the manufactures are not that interested There is this, which is true, and then there is outright hostility towards F/LOSS development, which is typically a product of dinosaur business model lock-in mindset (RPi, Nvidea, etc...), which I can only hope will finally die off sooner or later. @henk-herck said in Why is stropts.h included ?: amlogic ,allwinner ,rockchip are less known socs but have nice features Yes, personally I am well aware, but good to mention for others reading. Currently I am eagerly awaiting the release of the version of Helios64 (Rockchip based, IIRC) which is supposed to come with ECC RAM! This will eventually become my new 64-bit ARM ECC ZFS NAS (wow that was a lot of alphabet soup!). :laughing:

@ozrex, I don't want to assume your knowledge level. However the truth is that you will probably need to put together different bits and pieces from various threads in order to come up with your own custom solution (the A/C interface (IR) part, the battery part, etc...). Maybe it is worth it to create your own new thread, or maybe you want to keep researching / trying on your own a little longer first. The latter is admirable, and is the way I usually do it, too. Some times to a fault in my own case. :) Don't suffer along in silence if you are struggling to find the information, make a thread instead. If it becomes too difficult you may give up. We all need some small successes along the way to keep motivated and keep it fun. :) Probably best to create a new thread (I don't want to derail this one too much) but something you might want to look into is OpenMQTTGateway. I use it for my 433mhz, but it also supports RF, BLE, LoRa (and perhaps others in future) all on the same gateway! To me that was the way to go... And so far has been flawless for me.

Besides what Bob (?) mentioned (you seem to be making progress, breadboard unreliability, specifics), I would point out that there have been a number of discussions about ACKs, re-sending, reliability, keeping stats of NACK percentages (as a possible indicator of some problem), etc. over the years. The most recent I can recall was probably this one that I learned about when @BearWithBeard mentioned it here in my evidence based radio testing method (and capacitors) thread. My thread is more about hardware and radio testing, but we get into the subject of software ACKs etc. there in my thread a bit, and also in the linked thread. Is that the sort of stuff you are looking for?

Well I'm sorry you took it that way. By the time I happened along into the thread, you had already pronounced your diagnosis. I offered my thoughts into the thread, this way if your first diagnosis turns out not to be correct, you have other ideas to try. These issues can be complicated, and (I know from experience) some times what we think at first ends up not actually being the problem. As I said, I could be wrong anyway. @mhkid said in Node registration problem: And your comment was not based on any evidence it was just a feeling you had Each of us are chock full of thoughts, memories, things we learned which we are no longer consciously aware of. The sum total of all this "sub-conscious" thoughts and memories can manifest itself as a "gut feeling" but perhaps you are unaware of this. At any rate, it is not as if you need to be a "radio whisperer" or that this is some obscure subset of problems. Rather I would submit to you that these are the most common type of problems. @mhkid said in Node registration problem: you offered no solutions In fact I said "It sounded like radio propagation issues to me." No need for me to go into any further detail, if exchanging the gateway has solved the problem. However if you continue to experience problems, please share new information and we can continue from there.

@mhkid here you go : https://arduino-esp8266.readthedocs.io/en/latest/esp8266wifi/station-class.html

@TRS-80 said in wait() with interrupt: @Yveaux & @mfalkvidd, I can't help but make it complicated, I'm descended from Germans! :D :D :D Aber das Traue ich dir.

hello, he runs, after much effort and nerves :-) The values are a little bit very fluctuating? Probably you can only get away with a very accurate stable voltage of 5.0V. [image: 1590678946359-screenshot_20200528_165820.png]

Good to her you found that point :smile:. Imo you'd better change also your receive functions to not react on "ack" messages (via "else" prior to message.type-comparison).

Ok. So, answer will be "for some cases he can, but not must". Thanks for participations.

Well.. The quick answer I guess would be Yes, it is possible. But I imagine you would need to know a little bit about how the different components work. I also use the LoRa library from Sandeep Mistry and if you take a look at the code that initializes the card you find the following: // check version uint8_t version = readRegister(REG_VERSION); if (version != 0x12) { return 0; } Which is using the function readRegister: uint8_t LoRaClass::readRegister(uint8_t address) { return singleTransfer(address & 0x7f, 0x00); } Which is using the function singleTransfer: uint8_t LoRaClass::singleTransfer(uint8_t address, uint8_t value) { uint8_t response; digitalWrite(_ss, LOW); _spi->beginTransaction(_spiSettings); _spi->transfer(address); response = _spi->transfer(value); _spi->endTransaction(); digitalWrite(_ss, HIGH); return response; } Which is using pretty simple SPI commands. So perhaps you could do the same and select the LoRa library if the version is 0x12 or else select the nRF library. I don't know if there is enough space on the 328p to load both the libraries? And if you want to use the mysensors library it would be more complicated i suppose..

@tekka Right now, I am looking where your files are different from mine. I do not understand where I went wrong. perhaps I should also delete the other files that make creates, not just the hex. Either way. A lot of thanks.

@Oitzu Great work. Looking forward to use it. I have a use for this (some remote roof drain that gets clogged with leaves). Thanks!

@monte, I've implemented in PR https://github.com/mysensors/NodeManager/pull/517 something going in the direction you pointed out. Before explaining just a simple assumption first: NodeManager is intended to run on a number of different boards, most of them with limited memory so this capability has to take this constraint into consideration (hence no json parsing, reuse of existing communication mechanism, capability disabled by default, etc.) Apart from this, I found a sort of compromise to enable/disable sensors, even remotely and optionally persisting the status across a reboot. All the implementation details are within the PR (down below, the PR also include other enhancements) feel free to provide comments here or on Github. Hope it could be useful to avoid reimplementing the entire logic from scratch

Sadly it occured again a few minutes later, even after uploading the most basic arduino sketch (blink) in which I added a Serial.println. It appears sometimes it works , and sometimes not ! I ended up downloading the java IDE, which I can confirm works perfectly. There is definitely an issue with the serial monitor when using Arduino create web IDE (and not specific to mysensors debug mode). Hope this helps !