Topics created by tekka

@pikim No, I am not. My original plan was to deploy more and more RFM-based nodes as they seemed superior over NRF24 in general, but I realized that my NRF24 network was rock solid and reliable, so there was no need for the added complexity and cost to support and integrate another transport. Plans are made to change them. That being said, I used the multiRF gateway for months without issues. The gateway operated as stable as the single transport 2.3.2 gateway. No issues at all, except with the automatic TX power adjustment (ATC) of the RFM transceivers, due to what I believe might be a timing issue within the library. I described the issue in this thread. Basically, the RFM nodes were not able to reduce their transmit power, unnecessarily blasting the environment and wasting battery power. Introducing small delays in various places was all it needed to work around this issue successfully, seemingly without adverse side effects. This issue has not been properly remedied since the introduction of the multiRF gateway though. For all I know, it is still tekka's personal fork of the MySensors 2.4 branch and has not been updated, so any new fixes and features for version 2.4 since March 2020 will not be available to this fork, unless you manually implement them. So I guess it is up to you if you prefer to use the multiRF gateway without all the mainline 2.4 changes, or the up-to-date 2.4 branch without the multiRF feature. It should not make much of a difference currently, according the the commits since the multiRF fork, unless you want to use PJON transport or deploy NRF5-based nodes. I really wish that the development on MySensors revives, as it is feeling kinda stale at the moment. It would be a shame if this project got silently abandoned. I would be glad to help out wherever I can.

what would you like as a novelty ??? " MySensors is dead ?" ... No, in my house it is still alive. but it's true you are right to ask the question. the programmers, the creators are always The ????? what!? bought by the competition so that MySensors does not evolve any more? it makes damage to the commercial product

@Trand Well, sorry, but nothing else comes to mind. If you have a scope or logic analyzer then you need to watch the actual signals on the wires and see what is happening. If you don't, then you should pick up a cheap logic analyzer. You can get one for $10 and it's invaluable for tracking down things like this. I don't know where you are based, but I see them on Aliexpress all the time.

@karlheinz2000 said: But if I'm not using MYSB, I can flash a sketch with defined ID and this will work instantly in the network. Yes With MYSB I always have to do assign a new ID just to get the node to run the first time after flashing. Only true if EEPROM (i.e. ID address location) was cleared. Any chance to get MYSB to know, if a sketch is an flash? And start this sketch, which then will use the defined ID or request a new ID from controller and writes the eeprom? During booting, MYSBootloader calculates the FW CRC in flash and verifies it against the FW CRC stored in EEPROM (which is written after a successful OTA FW update) - if it matches, the sketch starts, if not, the bootloader remains active.

@tekka Is there any changelog to it also or it was just made officially available again? although last online status was 22 AUG 2020, so anyone else can confirm anything about it? I'd just be cautious without confirmation.

https://drive.google.com/file/d/14h8-8UccetEXxKET6ylry5_OcifdcJPz/view?usp=sharing