Posts made by Sergio Rius

Sergio Rius

@scalz After the "cleaning" there should be an example on each supported endpoint platform. I mean, if rj45+mqtt is supported, rfm should have a working example with all the components (level adjusters, etc...)

The big problem with rf24, said that it's so dependant on the environment, is that different countries have different regulations. And could be that what seems perfectly ok for some or all developers, doesn't work for other people in their houses.

Documentation doesn't say anything about checking country's wireless regulations as it's neglected.

Sergio Rius

@alex28 In my opinion you are presenting fair points.

Sergio Rius

@ramwal I'm sorry for my late response. And I'm glad you solved your problem.
In my case, the board just kept giving problems and problems.
It started with aberrant readings from the sensors. I sent it back only to be told that the board was perfect.
When it came back I had a condenser failure and after the fix, intermittent serial bus fail (all leds on and hangs at simple debug prints)...

...until one day, it mysteriously jumped into a rain puddle (while still connected to the battery pack, from a considerable height). So I said bye and never look back.

Sergio Rius

@tmaster WiFi devices will behave as you program them, there are several "conventional" projects there for them, like espeasy, tasmota, espurna (my preference) and with luck one more by the next year.
They poll the network for several things, like mqtt and ping status messages. Some are configurable.
But on top of that, there's own wifi ttl, leases and other green implementations that need re-registering from time to time.
So for battery powered devices could be tricky as that increases drastically wakeup.

I had once a problem in a company where mobile devices where repeatedly disconnected from Cisco APs, due to a bad ttl config in them. That's how I know about it.

Sergio Rius

Also... Continuing with the supposed vulnerability in the article. If you correctly program the arm chip, not with fancy joke web portal, but with secure protocols, etc... And then as the article says, you set the fuses to avoid firmware changes...
Where extreme risk would be? (Legit question)
Those chips are cheap enough to start consider them as one use.

Sergio Rius

This article @NeverDie published doesn't involve or talks about WiFi. It talks about physically accessing the chip and messing signals to program it.
That is a nonsense if you already have physically access to the device. And it should apply to any device.

That is what I mean. WiFi has been a nice word in the mouth of everyone for decades. It's so easy to simplify and confuse using a word as a flag.
If a company created a new ideal device for mys and this device would be easily hacked, would not mean that mys is the culprit or bad.

Sergio Rius

That's like saying one would never travel by plane because accidents happen. Your simplifying in excess the wifi concept.

Tell me how a WiFi connection can be hacked, if it implements an "inclusion mode"

Sergio Rius

@skywatch said in WI-FI IOT modules:

It does not support VLAN however

It's not a L2 switch? What is it?
In fact, switches only have to comply to 801.1x... whatever for vlan "passthrough" it's the router that's managing it. Also wifi APs has to be able to bring up several ssids and tag them.

I have opnsense virtualized in my server as the router, and a small physical shitty appliance as failover.

But @alowhum mysensors only works bc it's not widely used. You know what I mean. Just imagine a building with as mys installations as WiFis you can get nowadays.
And don't even think on phone telling your mother she has to modify bootloaders, firmwares, to switch a channel that perhaps it's also occupied. It's not realistic.

Anything can be done though. Those are tribulations, like wondering what will be next on cars, electrics or hydrogen.

Sergio Rius

Ok, send me your address

RF are not more secure. Kids spoofed garage door key fobs for decades and now are used to do more complicated things with cars. We are the accommodated ones.
Nrfs are also jammed at the same time that WiFi.

A good starting point to learn to do things with network is open-wrt. You can flash almost any router and start playing (and repurpose them for other things). And today you can find retired good L2 switches on eBay on a budget.
DLinks are very friendly, don't jump on a Cisco only bc they're cheap. (Or HP )
Professional & Soho switches have nice features like Poe & unused ports power down. With 48p or more they can be hungry beasts.

Sergio Rius

It feels wrong to me when someone says that WiFi (and by extent private networks & appliances) is extremely insecure, being what it is, with so many years of development.
Today there's everything for WiFi. And WiFi is not a protocol nor a transport.
How many here run their inet provider access point? That's dangerous.

Start learning about vlans, network segregation, AP mesh and redundancy.
And there are some tricks for l2 enc & auth.
Got to know the infrastructures of today houses.

Sergio Rius

@badmannen @Yveaux You're absolutely right. I was lazy, only changed a symbol and gave a bad advice. My response should be changed to <=4.

Still I don't understand what the original question was.

Sergio Rius

It's as easy as trying it.

@yveaux said in Dynamic change of variable name:

That will cause a buffer overrun at the end again...

Really? I can't see why a loop trough 1, 2, 3, 4 could overflow a 5 elements array.

In my code, I manually add 0 (the device itself, for vcc) before entering the loop. So in this case, still 5 elements.

Sergio Rius

@mfalkvidd said in Dynamic change of variable name:

int myarray[5] would have positions 0 thorugh 4. Position 5 would be outside the array. In the code above, position 0 is never used.

So either make the array 1 element larger than actually needed (with position 0 unused), or let i start at 0:

In fact, I interpreted it more like @skywatch
Notice the <=

 int value[5];
 for (i=1; i<=5; i++){
   value[i] = debouncer[i].read();
 }

I just made something like this for indexing sensors in a node, where idx 0 was the node itself, and thus already filled before the loop.

Sergio Rius

Voilá.
And it maintains a live inventory of clients.
Some points are so difficult to achieve. But I was looking at message identification as a response to the sequence switch problem.

Sergio Rius

@rozpruwacz said in Build retry funtionality into the mysensors library:

But MQTT broker is not running on the 1kB ram mcu

I'm not saying to make a mqtt broker run on an arduino. Just picking the process logic as a guideline.
MQTT is not a protocol made for raspberries, it's only that often run on them.

Sergio Rius

@mfalkvidd said in Build retry funtionality into the mysensors library:

How do you handle if the same actuator is changed multiple times before the earlier changes have been reliably delivered?

How MQTT qos 1 does? I think it should be similar to it.

Also I don't think changes in between should be dropped. That would be like dropouts in a metered system (logged to influx, fEx) and probably do strange things with scenes and group switching.

Sergio Rius

In my attempts to become a better C++ (Arduino) developer, so I can make those advanced nodes I'm thinking on, I often dismantle and see inside of big avr projects.
In case of MyS, I can't understand how, in an archiectural point of view, can work.

Let me explain: I created a new project in Platformio for ESP8266. Then I took the bare minimum from MyS lib, to be able to debug send a message, and stripped all other content. Even removing the ability for hook setup and loop, removing MyHwHAL and replacing with normal functions.
So it has a main.ino with setup and loop that calls mysensorscore setup and loop.
Other files, with content stripped that still remain are main mysensors.h, myconfig.h and hal for 8266. Nothing more. In hal I only leave debug related content, initilizing serial in hwInit() (called in core without conditional inclusion).

As is, it never compiles. It throws error for two reasons. Core.cpp doesn't see content in hwHal (hwInit, DEBUG macros), and files in hwHal doesn't see the serial macros defined in config.
I tried 4 and 5 times, with fresh projects and I can't make it work. I even thought it was something with the linux/platformio compiler, so switched to VS+vsmicro and then arduinoIDE without any success.

Yesterday I took all the content and incorporated "as is" in order of call in the Mysensors.h file, and it compiled. Then I took out all the files one by one to reveal those two avobe problems in cpps.
Then I took another copy of the bare project and eliminated the mysensors-mysensorscore level. I moved the coding from core to mys.h and it worked well and solved 1 problem. But Still have to reference myconfig in myhwesp8266 for it to see the debug macros.

I'm sure it's my ignorance, so perhaps someone more expert in avr-c++ can explain me how mys library ignores those problems?

Sergio Rius

@kimot said in My experiences with MySensors:

But you can use one AP for your computers and TV and etc. and other for your sensors.
AP hw is cheap....

Or you can get a VLAN compliant Wifi access point, do the things as should be and implement a separate VLAN for your IoT devices and services.
If you buy, for example an ubiquity AP, you can configure as many SSIDs as you need, each one on it's own VLAN, and even you can specify that the IoT network should only be N-type increasing the range.
By using only one access point you also reduce radio interferences. Radio appliances are not perfectly made and cheap ones tend to be noisy and get worse with the age.

I'm not particulary an ubiquity fan, in fact I only have the ap_ac_pro one, but I'm so satisfied with it that I would recommend their switch+router solution. The web management is awesome.
For my adventures I prefer having an ordinary 10gb d-link switch and a custom opnsense router.

Range of the ap_ac_pro inside a 20m radius house with 25cms stone walls is just in the limit. Just one in the very center. A long range unit would cover anything, but mine is freaking fast.

Sergio Rius

@tbowmo Thanks Thomas, I was trying to make an ENC28J60 module work with RF24 then RFM69, and I was getting crazy at it. Finally the module was a failed one. I'm so embarrased, as I was convinced I first tested the module on arrival, and I missed the point.
I've already ordered a W5100, but it may take weeks.

Sergio Rius

I've been fiddling with the radio alone (serial gw), softspi and changing pins, and I think there's something else here.
Well those are my findings:

With this base definition and without the module wired:

#define MY_RADIO_RFM69
#define MY_RFM69_NEW_DRIVER
#define MY_IS_RFM69HW

#define MY_DEBUG_VERBOSE_RFM69

#define MY_GATEWAY_ENC28J60

It works as expected.

0 MCO:BGN:INIT GW,CP=RPNGA---,REL=255,VER=2.3.1
4 TSM:INIT
5 TSF:WUR:MS=0
6 RFM69:INIT
7 RFM69:INIT:PIN,CS=10,IQP=2,IQN=0
11 RFM69:PTX:LEVEL=5 dBm
13 TSM:INIT:TSP OK
15 TSM:INIT:GW MODE
16 TSM:READY:ID=0,PAR=0,DIS=0
19 MCO:REG:NOT NEEDED
72 GWT:TIN:IP=192.168.50.211
1075 MCO:BGN:STP
1077 MCO:BGN:INIT OK,TSP=1
1081 TSM:READY:NWD REQ
1083 RFM69:SWR:SEND,TO=255,SEQ=0,RETRY=0
1088 RFM69:CSMA:RSSI=-98
1090 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:

If I try to change CS pin to any other with #define MY_RFM69_CS_PIN 4 for example, I always get:

0 MCO:BGN:INIT GW,CP=RPNGA---,REL=255,VER=2.3.1
4 TSM:INIT
5 TSF:WUR:MS=0
6 RFM69:INIT
7 RFM69:INIT:PIN,CS=4,IQP=2,IQN=0
11 RFM69:PTX:LEVEL=5 dBm
13 TSM:INIT:TSP OK
14 TSM:INIT:GW MODE
16 TSM:READY:ID=0,PAR=0,DIS=0
19 MCO:REG:NOT NEEDED

So I revert the CS pin change and activate softspi and change irq #define MY_SOFTSPI and #define MY_RFM69_IRQ_PIN 3 And it works well:

0 MCO:BGN:INIT GW,CP=RPNGA---,REL=255,VER=2.3.1
4 TSM:INIT
5 TSF:WUR:MS=0
6 RFM69:INIT
7 RFM69:INIT:PIN,CS=10,IQP=3,IQN=1
11 RFM69:PTX:LEVEL=5 dBm
13 TSM:INIT:TSP OK
15 TSM:INIT:GW MODE
16 TSM:READY:ID=0,PAR=0,DIS=0
19 MCO:REG:NOT NEEDED
72 GWT:TIN:IP=192.168.50.211
1075 MCO:BGN:STP
1077 MCO:BGN:INIT OK,TSP=1
1079 TSM:READY:NWD REQ
1081 RFM69:SWR:SEND,TO=255,SEQ=0,RETRY=0
1086 RFM69:CSMA:RSSI=-98
1091 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:

Then I add the eth module and I get:

0 MCO:BGN:INIT GW,CP=RPNGA---,REL=255,VER=2.3.1
4 TSM:INIT
5 TSF:WUR:MS=0
6 RFM69:INIT
7 RFM69:INIT:PIN,CS=10,IQP=3,IQN=1
11 RFM69:PTX:LEVEL=5 dBm
13 TSM:INIT:TSP OK
15 TSM:INIT:GW MODE
16 TSM:READY:ID=0,PAR=0,DIS=0
19 MCO:REG:NOT NEEDED

And stays here forever.

Of course all those test are made using a double (5v+3v3) good power source, a level shifter... and changing the wires accordingly.

I have some questions:

Its normal MY_RFM69_CS_PIN not having effect and breaking the radion connection?
Without being able to change this, I don't know if it's spi interference.
In the last test, it seems to halt when initialising the network. Doesn't it?
Is there a way I can further know if the problem is with the eth module? I've tried it alone with the nano and it works.

I would thank guidance for debugging this.

Sergio Rius

@cabat Oh, no! Thanks for your help. It has inspired me. Now I'm trying something more.

Sergio Rius

@nagelc said in ENC28J60 Ethernet gateway:

I think this was fixed in the W5200 and W5500.

Noooooo..... Just ordered a W5100

@cabat It may not do for me. I'm trying to use rfm69 now. I could not leave my existing network down and brought the nrfs back to where they belonged.

Also the eth module I have here is the shield for nano one. As it stacks below the nano, it may be that is interfering more pins than I expected.

What I would want to know is that the rfm69 needs a different pinout with this shield or not. I can't find any reference that tells me this, so I can start debugging the problem.

Sergio Rius

You know... Great power comes with a great responsibility

Sergio Rius

@cabat Could you please share you pinout for radio and module, and the sketch configuration?
I can't make it work and I don't know if it's a matter of connections or something to activate, like softspi.

Sergio Rius

@scalz Thanks for your help. Unfortunately I can't get a w5100 in my country and would order it outside. I had those rfms for years and I want to test range before buying a sensebender.
And I'm convinced to stop using the wifi for a gw.

I had hope that any used had the same hw already running.

Sergio Rius

So after being unable to make the nrf24 to work with the ENC28J60, I'm trying now something different. I started by making an rfm69 serial gateway with success.

Then I want to see if it could be possible to convert it to ethernet with the ENC28J60.
I searched and found everything in the forum. I arrived to the conclussion (that is probably wrong) that I must wire both radio and eth module using the same spi pins, activating a new driver and nothing more. But this doesn't work on the proto-board.

There's something else to be done? Thanks.

Sergio Rius

@scalz C'mon, would you leave the forum with just one hit?
In fact I understand your point completely. Open source has become more and more caotic. Internet is atemporal, and often people has the bad habit of not putting the complete date at the top of their "articles" that makes that search engines cannot filter and order properly.
Everyone has a blog and writes whatever gets out him. The majority of people uses that as a remainder for themselves and... whynot getting reward. So there are zillions of howtos made anyhow. They are not written for helping people.

If the sources and destination are always one, why there aren't the binaries available and all writeups talk about messing the computer and compiling? I think that's because nowadays people seek praise for having achieved it.

Scalz point is about economy of time. Because time is money, even if it's spare time, and yes, a paid/proprietary probe becomes cheap, giving the documentation on the internet, today.

Also the point of view depends in the situation of everyone and its age. Someone at the 5thies feels earlier that it's wasting time, and there comes frustration, and complaining posts, unfortunately
Just buy a probe, forget about it until it gets delivered.

@monte BTW, I was trying to program an stm32 board with a jlink. Not a Jlink. Maybe if there was a way to get an already compiled binary (to avoid all those dependencies errors) and program the jlink with a normal serial ttl...

Sergio Rius

That is just the point I had in my mind. I'm convinced that mysensors is a great project and the work done here is golden, really. But I would like to know why the documentation always seems to recommend hardware that when you fail to implement, at some point someone tells you that it was expected.
That happened me again this week with the Ethernet gw. Following the documentation, hours and hours trying to make the module work, to share spi port, etc... and then someone tells me better getting a w5100. Then why is this board in the official docs? Let's take it out and put a warning.
The docs are full of pinout pics of nrf24. But if you use the search (for hours) you get plenty of posts from vip telling... Better going with rfm69.
I hope it's not the same with rfm69.

Sergio Rius

As I was having low reliability with my gateway, I'm trying to build an ethernet one. But I can't make it work. I have those components:
arduino nano
ENC28J60 nano ethernet shield (this one)
An original nrf24, shielded pa+lna

I'm burning this sketch, sligtly altered from examples:

#define MY_DEBUG

// Enables and select radio type (if attached)
#define MY_RADIO_RF24
//#define MY_RADIO_RFM69
//#define MY_RADIO_RFM95

#define MY_GATEWAY_MQTT_CLIENT

// Set this node's subscribe and publish topic prefix
#define MY_MQTT_PUBLISH_TOPIC_PREFIX "mys-in"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mys-out"

// Set MQTT client id
#define MY_MQTT_CLIENT_ID "mys-langw-mqtt"

// MQTT broker ip address or url. Define one or the other.
//#define MY_CONTROLLER_URL_ADDRESS "m20.cloudmqtt.com"
#define MY_CONTROLLER_IP_ADDRESS 192,168,50,201

// The MQTT broker port to to open
#define MY_PORT 1883

// Enable these if your MQTT broker requires username/password
//#define MY_MQTT_USER "username"
//#define MY_MQTT_PASSWORD "password"

#define MY_SOFTSPI
//#define MY_SOFT_SPI_SCK_PIN 14
//#define MY_SOFT_SPI_MISO_PIN 16
//#define MY_SOFT_SPI_MOSI_PIN 15

// When ENC28J60 is connected we have to move CE/CSN pins for NRF radio
#define MY_RF24_CE_PIN 5
#define MY_RF24_CS_PIN 6

// Enable gateway ethernet module type 
#define MY_GATEWAY_ENC28J60

// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
#define MY_IP_ADDRESS 192,168,50,211

// If using static ip you can define Gateway and Subnet address as well
#define MY_IP_GATEWAY_ADDRESS 192,168,50,1
#define MY_IP_SUBNET_ADDRESS 255,255,255,0

// The port to keep open on node server mode / or port to contact in client mode
// #define MY_PORT 5003   

// Controller ip address. Enables client mode (default is "server" mode). 
// Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere. 
//#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 254   
 
// The MAC address can be anything you want but should be unique on your network.
// Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use.
// Note that most of the Ardunio examples use  "DEAD BEEF FEED" for the MAC address.
#define MY_MAC_ADDRESS 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED

/*
// Enable inclusion mode
#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
//#define MY_INCLUSION_BUTTON_FEATURE
// Set inclusion mode duration (in seconds)
#define MY_INCLUSION_MODE_DURATION 60
// Digital pin used for inclusion mode button
//#define MY_INCLUSION_MODE_BUTTON_PIN  3

// Flash leds on rx/tx/err
#define MY_LEDS_BLINKING_FEATURE

// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300

// Flash leds on rx/tx/err
// Uncomment to override default HW configurations
//#define MY_DEFAULT_ERR_LED_PIN 16  // Error led pin
//#define MY_DEFAULT_RX_LED_PIN  16  // Receive led pin
//#define MY_DEFAULT_TX_LED_PIN  16  // the PCB, on board LED
*/

#include <Arduino.h>
#include <SPI.h>
#include <UIPEthernet.h>
#include <MySensors.h>

void setup()
{
  // Setup locally attached sensors
}

void presentation()
{
  // Present locally attached sensors here
}

void loop()
{
  // Send locally attached sensors data here
}

I copied the UPIEthernet v1.0.4 from the example.

But all I get in debug is:

18:25:24.979 -> 0 MCO:BGN:INIT GW,CP=RNNGA---,REL=255,VER=2.3.1
18:25:24.979 -> 4 TSM:INIT
18:25:24.979 -> 5 TSF:WUR:MS=0
18:25:24.979 -> 11 TSM:INIT:TSP OK
18:25:24.979 -> 13 TSM:INIT:GW MODE
18:25:24.979 -> 15 TSM:READY:ID=0,PAR=0,DIS=0
18:25:24.979 -> 17 MCO:REG:NOT NEEDED

I had to introduce the SoftSpi because I was getting radio init errors. But now, there's no traffic at all.
I've done everything possible, checked the wiring many times... Independly feeding the components...

Does anyone use that setup? Thanks

EDIT: OK, so now I found that this module is not recommended.

Sergio Rius

@monte I may be wrong, but from what I understand while reading on it, it seems that the debugger is implemented in the probe. The program you run is an interface.
I see it like a Ilogger interface that you implement in a program.

Sergio Rius

@monte I guess he means taking the debugger program to the computer layer and leave only the com channel to a TTL device.

Sergio Rius

Any charitative soul can help me prepare a black magic probe? I'm following the guides but at some point I can't continue.
For example, following this one: https://hackaday.io/project/28180-bluetooth-gamepad-phone-case/log/71316-stm32-black-magic-probe-flashing
I do:

$ mkdir mbp && cd mbp
$ wget https://raw.githubusercontent.com/jsnyder/stm32loader/master/stm32loader.py
$ chmod 774 stm32loader.py
$ sudo apt install python-pip
$ pip install pyserial # There I remove '--assume-yes' as this is a wrong parameter

# Then here starts the funk
$ sudo apt install arm-none-eabi-gdb  # The package does not exist.
# I found online that it may be already incorporated and my worth a try, so I continue.
# So I change the boot0 jumper to 1, that it not said in the guide, connect the two boards and plug it into the computer.

$ dmesg | grep tty
# Nothing.

$ sudo dmesg | tail
[10680.891711] usb 1-12: Product: STM32 STLink
[10680.891714] usb 1-12: Manufacturer: STMicroelectronics
[10680.891716] usb 1-12: SerialNumber: PÿqRpQP2$g
[11990.202434] usb 1-12: USB disconnect, device number 7
[11998.926846] usb 1-12: new full-speed USB device number 8 using xhci_hcd
[11999.076060] usb 1-12: New USB device found, idVendor=0483, idProduct=3748, bcdDevice= 1.00
[11999.076066] usb 1-12: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[11999.076069] usb 1-12: Product: STM32 STLink
[11999.076072] usb 1-12: Manufacturer: STMicroelectronics
[11999.076074] usb 1-12: SerialNumber: PÿqRpQP2$g
# But no usb port. So I add udev rule.

$ ls -l /dev/stl*
lrwxrwxrwx 1 root root 15 oct 15 14:32 /dev/stlinkv2_12 -> bus/usb/001/008

$ sudo ./stm32loader.py -p /dev/stlinkv2_12
Traceback (most recent call last):
  File "./stm32loader.py", line 427, in <module>
    cmd.open(conf['port'], conf['baud'])
  File "./stm32loader.py", line 71, in open
    timeout=5               # set a timeout value, None for waiting forever
  File "/home/sergio/.local/lib/python2.7/site-packages/serial/serialutil.py", line 240, in __init__
    self.open()
  File "/home/sergio/.local/lib/python2.7/site-packages/serial/serialposix.py", line 272, in open
    self._reconfigure_port(force_update=True)
  File "/home/sergio/.local/lib/python2.7/site-packages/serial/serialposix.py", line 326, in _reconfigure_port
    raise SerialException("Could not configure port: {}".format(msg))
serial.serialutil.SerialException: Could not configure port: (25, 'Inappropriate ioctl for device')

$ sudo apt install gdb-multiarch
# Same effect.

And here I am. Does anyone knows what kind of magic is required to put inside this little thing?

Sergio Rius

@NeverDie Interesting. What have pulled you from nrf52 towards PICs?
Can you post a link on the board you ordered, (or one like that)? Thanks.

Sergio Rius

@tbowmo You see, it's a lottery.
I also live in the countryside, and also having problems.
What about ble capabilities of the nrf52? Some claim that a Bluetooth network works.
I really doubt it, it was the most affected band by the microwave, when I analyzed interference.

Bs:

Adaptive signal power
Low level checksum error control and retry
Channel analysis and automatic selection
Double channel / twin radio gw
Nrf52 ble advertising/handshake and then regular 2.4g transmission?

Sergio Rius

@scalz Regarding WiFi I'm not saying that mysensors should overcome the problems of crowded or noisy environments. I'm just saying that if that's the war field, it should have slided to another one.

I spent more than 4 years on those problems. I'm physician and software architect/analyst, and my father was ham radio fanatic. Not boasting, only saying that I have a minimum knowledge. I created a nice environment with only one WiFi device, good ubiquity equipment, with nodes without boards or ground planning issues, studying the band and choosing channels and still had nightmares.

Yesterday I learned how to easily hang a node by sending a message to it. That shouldn't be possible.

I'm not saying that this is crap or that this doesn't worth playing with it. Only think that it needs some love on the low level even if it has to move to slightly powerful devices. Or adding capabilities on powerful architectures while still supporting the good old ino.

Perhaps combined with a custom nrf52 development board or something to make easier burn and solder them. Make an nrf52 mysensors starter kit, and convert sensebender to it.

Sorry, as you said I don't have the knowledge to make long run boards to contribute with them.

Sergio Rius

Well, unfortunately I cannot agree with the stories of success.

It's ok that a tool works for someone, but it can't be so weak that things like radio clones, track shapes or cap variations renders something unusable. And still did not mention interference or houses construction materials. All things that should be tested. WiFi/mobile interference should not be a problem, everyone has em.

Just only think that if Chinese manufacturers are making these clones in that volumes, and they are sold, it's because they took a look at the original and made a product profile with what specs are acceptable for the expected application and clones are the result. I mean that perhaps mysensors expected to much from them.

I guess everyone already knows that I only had problems trying to use mysensors, and now I have a defeating gw problem while using original radios all around. I have nrf52s in the box for testing but I'm so defeated, that I have no strength to try them.
I've ordered parts for making a good ole rj45 gw, but I'm already working in a custom base sketch for moving to esp+mqtt.
My influx data is full of "holes"

Now I'm thinking in the fact that my gw started to make this more or less after the installation of a Google home and a echo Dot, for testing. It already seems paranoia.

Sergio Rius

Seems that I may have been hit again by the radio sync problem:

613757 RF24:RBR:REG=23,VAL=17
613788 RF24:RBR:REG=23,VAL=17
613820 RF24:RBR:REG=23,VAL=17
613851 RF24:RBR:REG=23,VAL=17
613883 RF24:RBR:REG=23,VAL=17
613914 RF24:RBR:REG=23,VAL=17
613946 RF24:RBR:REG=23,VAL=17
613977 RF24:RBR:REG=23,VAL=17
614009 RF24:RBR:REG=23,VAL=17
614040 RF24:RBR:REG=23,VAL=17
614072 RF24:RBR:REG=23,VAL=17
614103 RF24:RBR:REG=23,VAL=17
614135 RF24:RBR:REG=23,VAL=17
614166 RF24:RBR:REG=23,VAL=17

@tekka I've conducted a debug test with the radio timing code and the results can be found there:
GW_DEBUG: https://drive.google.com/open?id=1Ji-6E_iAcE86gTzxSTjOihVlQREHjwLN
NODE_DEBUG: https://drive.google.com/open?id=1skaAWlYWqjNRqAjcTAVudw0DAZiAFEqs

Sergio Rius

For some time I had issues with mysensors communications that prevented the deployment I had planned. After dedicating some time to rebuilding for better debug, I have finnaly found some problems:

The use of fake/cloned radio modules. Everything has been said. It masked the problems and prevented me to debug properly.
Domoticz unwanted replies that where interpreted as new commands. I never thrust on Domoticz, and after changing for node-red, that allowed me to better debug communications and see that now and then, Domoticz is replying with a message that seems to announce it's capabilities with respect to the received node and value. It's like an ack, but with a relatively big content, with unwanted things like battery management capabilities (even to connected devices). Those messages where interpreted by the node as new commands and, for example, it made my garage door node to stop while it was opening or closing, without any notice (with the problems it represents). Also those messages sometimes interrupted devices presentation.
Gateway going lazy after some time.

The two first problems are easy to solve and I have them under control. But this last problem is what is drawing me nuts. It appears in MYSController as the communication activity becoming slow.
I have several devices and one of them is an 8-channel power meter that it's embedded inside my home power distribution box. It monitors each phase of the installation and has a small screen for instant measurements. So far has been a great help detecting failing appliances with residual consumption, as I made it with a great low power resolution using adc chips with amplification.

Well, this device sends a minimum of 6 values in a row each minute. When the problem in the gateway is present, those values appear in the debug window as one every two seconds and after the third all get lost. I noticed that the values for total consumption and kitchen where so deviated, and checked that the screen showed real fresh values and it announced sending the data.
For temp/hum sensors, gw misses one of the values.

When this happens, the only solution is getting a stair and reaching the gateway in the ceiling and turning it off-on. After some hours, it happens again.
Can someone help me to fix this problem? Or sending me advice in how more the gw can be debugged?

The gateway is a nodemcu Lolin v3 board with a direct soldered wirings to a genuine pa-lna rf24 factory shielded radio. Has a cap. It is powered from a good and clean power source.
It's burned now with the default v2.3.1 library and I removed ArduinoOTA and the web portal I implemented, so using the default espgw example. As I'm later converting received serial data to mqtt, I also tried with the mqtt sketch in case that induced some problem, but had the same results.
GW debug doesn't show anything bad. I don't see any problem with wifi. I have good control of my network.

Any ideas?

Sergio Rius

@mfalkvidd If you look close, I'm only sending as a response to a request from the "controller".

But I'm still wrong for insist getting the received value from the property bValue. Seems logical to me that it would contain the boolean value instead of a byte size or whatever.

If I had used the method ".getBool()" I would had the boolean value. Although, if the controller sets a boolean, the node still gets wrong values, so you still have to transmit an integer 0/1. I don't like it, because it forces processing all the values as integers in node-red, for example.

As usual, I'll leave this, my stupidity, behind in the hopes it serves to anyone else.

Sergio Rius

I've built up a new dummy sensor so I can debug it in my desk. The results still are so confusing:

Initialising...
loadState(0): 255  // The expected behavior for a non initialised slot.
passiveMode: 1    // Makes the variable true. All ok.
loadState(0): 255
passiveMode: 1
Received value: 48  // If I Set to 0 bValue is 48??
Storing...
passiveMode: 1
Received value: 102  // If I Set false...
Storing...
passiveMode: 1
loadState(0): 1
passiveMode: 1
Received value: 70   //If I Set False...
Storing...
passiveMode: 1

That's so interesting. But not what I expected.

Sergio Rius

I'm opening this topic because I'm getting strange results in a sketch I'm modifying, and perhaps is it something that I misunderstand.

I created a "virtual" binary sensor in my device, so I can put it in passive mode, so it is still available, sends it's sensors info but doesn't do any action. Doesn't switch on and off.

bool passiveMode = false;
...
#define CHILD_ID_PASSIVEMODE  4
MyMessage msgPassiveMode(CHILD_ID_PASSIVEMODE, V_STATUS);
...
void sendStatus() {
...
  send(msgPassiveMode.set(passiveMode));
}

void setup() {
...
  passiveMode = loadState(0);
}

void presentation() {
...
  present(CHILD_ID_PASSIVEMODE, S_BINARY, "ModoPasivo");
}
...
void receive(const MyMessage &message) {

  const uint16_t commandType = mGetCommand(message);
  if (commandType == 2) {
    if (message.type == V_STATUS && message.sensor == CHILD_ID_PASSIVEMODE) {
      send(msgPassiveMode.set(passiveMode));
    }
  }
  else if (commandType == 1) {
    if (message.type == V_STATUS && message.sensor == CHILD_ID_PASSIVEMODE) {
      if (message.bValue != passiveMode) {
        passiveMode = message.bValue;
        saveState(0, passiveMode);
      }
    }
}

Well, that's all the code added. In the first run, without the memory slot been set, returned a value of "1" for passiveMode. Then, I set it to "0" and requested it again, and it replied again "1".

I'm wondering what I I've misunderstood. Is not possible to store that value in the sketch as a boolean and rely on implicit conversions?
The problem can be:
The storage: Does saveState and readState understand true/false as 1/0?
The Set/Req: I interpret that those functions should enforce the conversions as message has a bValue property available and send has overloads for it.

I could change passiveMode to an uint8_t and never look back, but I need to understand what's the problem, here.

Sergio Rius

I was not sure about it, and the paranoia took control.

Sergio Rius

When declaring/presenting sensors for a node, what it's the first id to consume, zero or one?

I was looking at the network topology when I saw that the sketch I made for relay modules, has the relays starting at 0. Where all other nodes I made are starting at 1. That's because for that relay nodes, the sketch uses a template and populates the sensors from an array, that could be passed from the network (as var, text...). So it starts with item 0. And I never looked back.

But I think the sensor 0 is reserved for internal messages isn't it?
The sensors for those nodes are presented as binary but it happens that they appear in every controller as dust sensor. Now I'm suspecting from everything.

Sergio Rius

Seems that the problem was that influxdb always configures the field type the first time a series is accessed.
I thought that the value was something like a "variant" and would eat anything I throw at it. So when I altered the data types in the flow, the db refused to save.
A drop and re create solved the problem.

Sergio Rius

I'm trying to save the sensor data received from mqtt into two different measurements, if they are internal network messages, I want them in "internal" and all the sensor values into "values"
For that I tried using a switch module checking the "sensor" attribute being 255, but I can't make it save on the internal "table"

To my confussion, the switch seems to work, as I put debug nodes on the output (1, 2) and it keeps printing 1 or 2 correctly depending on the message.
But from the two DB/measurement connections that hangs on it only executes the second one. Nothing is written into "internal", although the debug is hit and also the measurement has received the series :

key
---
internal,node=0,sensor=255,subType=I_HEARTBEAT_RESPONSE
internal,node=1,sensor=255,subType=I_DISCOVER_RESPONSE
values,node=1,sensor=1,subType=V_KWH
values,node=1,sensor=1,subType=V_VAR1
values,node=1,sensor=1,subType=V_WATT
values,node=1,sensor=2,subType=V_WATT
values,node=1,sensor=3,subType=V_WATT
values,node=1,sensor=4,subType=V_WATT

Can someone give me a clue of what is happening? I'm newb with node-red and influxdb.

Sergio Rius

I partially run my IoT implementation on docker. Today I was trying to test a mqtt broker inside docker. I always create my containers with permanent volumes and I maintain a separate folder for containers in my nas.

I installed all kinds of containers and pointing the storage to their config folder like -v /mnt/docker-data/mqtt/config:/mosquitto/config always worked. But mosquitto didn't want to run using remote volumes. Always complains about not being able to access the config file:

1565537402: Error: Unable to open config file /mosquitto/config/mosquitto.conf.

It doesn't matter if you try to change the owner of the folders or even give rwx to anyone.
After studying the project's dockerfile and folder structure I came to the conclusion that it's not prepared to be installed in one go, using persistent volumes (can be done in two execs). The project docker directions are not so clear and seem to be made for auto-consumption (like not providing a default configuration file)

So I made a small snippet to properly install and do a minimal configuration for the mosquitto container, pasted below.

Usage: # ./mqtt.sh /mnt/<thefolderwhereyoupersistdockervolumes>

#!/bin/bash
VOLUME="$1"

# Only if persistent volumes/configuration doesn't exist >>>>>
if [ ! -d "$VOLUME"/mqtt ]; then
  mkdir -p $VOLUME/mqtt/config $VOLUME/mqtt/data $VOLUME/mqtt/log

  curl https://raw.githubusercontent.com/eclipse/mosquitto/master/mosquitto.conf -o $VOLUME/mqtt/config/mosquitto.conf
  cat <<EOT >> $VOLUME/mqtt/config/mosquitto.conf

persistence true
persistence_location /mosquitto/data/
log_dest file /mosquitto/log/mosquitto.log
EOT

  chown -R 1883:1883 $VOLUME/mqtt
fi

docker run --name mqtt --restart=unless-stopped \
  -p 1883:1883 \
  -p 9001:9001 \
  -v $VOLUME/mqtt/config/mosquitto.conf:/mosquitto/config/mosquitto.conf:ro \
  -v $VOLUME/mqtt/data:/mosquitto/data \
  -v $VOLUME/mqtt/log:/mosquitto/log \
  -v /etc/localtime:/etc/localtime:ro \
  -d eclipse-mosquitto

docker exec -it mqtt mosquitto_passwd -c /mosquitto/config/pwfile iot
# Add to a shared network between iot containers. (Node-Red, InfluxDb...)
docker network create iot
docker network connect iot mqtt

Notes: This snippet is stupid. It doesn't care what he gets as parameter, for example. So be smart when using it. And remember not adding the name of the container to the route. He always adds and assumes "mqtt"
Sample parameter: /mnt/docker-data will create: /mnt/docker-data/mqtt so take into account if you already have that folder.

Sergio Rius

@yveaux said in nRF24L01+ Communication Failure: Root Cause and “Solution”:

E.g. in your last post "as it works if debug is activated. Also Tekka Code works." That suggests there is a working solution for you, with tekka's patch and debug disabled. Is this correct?

Yes @yveaux with my posts on this thread I was only hoping to help testing this situation, as I found interesting to also add control to TX sequences. But to my surprise the issue #941 appeared on a node (in my desk 0.5m away from gw) that never showed it before and I thought it could help with that one, as still wasn't solved. I thought I found a clue to prove that it has to do with node radio processing speed (alas SW, not HW). I don't know how pairing is synced between nodes and gw. It makes sense to me for the gw to wait and adapt to a new incoming node should already be implemented, so this issue has no logic to me.

It's true that my range it's very poor. I only have two sensors operative, and the two are in clear line of sight to the gw. The garage door controller was giving so many problems that had to deactivate it (only one floor between and just under gw) and the strips controllers work one day of ten. But it has passed some time and I should do testing again.

PS: As for at where I was with my installation (I had two operations on my hands and a baby, so I've been disconnected) my problems are nodes that appear comms dead after putting them in place and starting. Not completing the registering sequence. Others working as expected and after a while being totally disconnected from the network and at the same situation above. Randomly registering after leaving them alone for days. So two kinds of nodes, ones that finally register on their own and others never, even being so much near to the gw (4mt)
I don't find it to be a range or radio issue. It smells to me to be a network management problem.

Sergio Rius

@yveaux said in nRF24L01+ Communication Failure: Root Cause and “Solution”:

@sergio-rius said in nRF24L01+ Communication Failure: Root Cause and “Solution”:

#define MY_RF24_CHANNEL 108

Your range issues could be caused by this high channel number; clones perform worse in my experience at high channel numbers. Did you try with lower channels? (less than 90)

Yes. That was the lower channel that allowed communication. Perhaps in laboratory conditions would be true, but not in reality.

I don't think it has anything to do with failing yo pair, as it works if debug is activated. Also Tekka Code works.

It's not my intention to be rude. It's only that I had plenty of developments planned that were all thrown in the box as this is not taking off. I will try with nrf5 and if it doesn't work I'll ditch it all completely. Sorry.

Sergio Rius

@odritter The gateway is an esp8622 with my personal touch for the wifi management. Other than that the standard sketch from the site. Running the plain MyS v2.3.1
But in relation to the issue I referred, yes, should be a fast gw for it.

#define MY_RADIO_RF24
#define MY_RF24_CHANNEL	108
#define MY_GATEWAY_ESP8266

The node is a normal Arduino nano, bare driving an 8 relay board. The sketch is more complicated, as I developed a library that allows "discovering" the relays with minimal configuration independent of the number of them. But it doesn't trigger until the setup and the node it's failing before.
The relevant parts:

/////// Mysensors options /////
// Radio
#define MY_RADIO_RF24
#define MY_RF24_IRQ_PIN 2
#define MY_RF24_CHANNEL	108

#define MY_DEBUG
#define MY_DEBUG_VERBOSE_RF24

#include <MySensors.h>

As you can see I'm using a hw interrupt, and also MyS v.2.3.1 BUT using the Tekka RF24.cpp file with the changes above to include your "waiting for interrupt". Nothing too complicated.

What I don't understand is that supposedly, the problem in the github issue appears when a node is slower than the gw, and is not still ready when the gateway answers the registration request. But your changes should make the node switch to listening faster. And then if I remove the define for irq on the node the "else" part works as expected, and also if I use IRQ on the standard v2.3.1 it works.

PS. Is that the answer from the GW doesn't have an acknowledge that a slower node can make it fail? Doesn't make sense to me. I confess that I still haven't had any time to look at it.

Sergio Rius

This is what I get with @odritter code:

09:37:10.346 ->  
09:37:10.346 ->  __  __       ____
09:37:10.346 -> |  \/  |_   _/ ___|  ___ _ __  ___  ___  _ __ ___
09:37:10.346 -> | |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
09:37:10.346 -> | |  | | |_| |___| |  __/ | | \__ \  _  | |  \__ \
09:37:10.346 -> |_|  |_|\__, |____/ \___|_| |_|___/\___/|_|  |___/
09:37:10.346 ->         |___/                      2.3.1
09:37:10.346 -> 
09:37:10.346 -> 16 MCO:BGN:INIT NODE,CP=RNNNA---,REL=255,VER=2.3.1
09:37:10.346 -> 26 MCO:BGN:BFR
09:37:10.346 -> 27 TSM:INIT
09:37:10.346 -> 28 TSF:WUR:MS=0
09:37:10.379 -> 35 TSM:INIT:TSP OK
09:37:10.379 -> 37 TSF:SID:OK,ID=6
09:37:10.379 -> 38 TSM:FPAR
09:37:10.379 -> 40 TSF:MSG:SEND,6-6-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
09:37:12.387 -> 2048 !TSM:FPAR:NO REPLY
09:37:12.387 -> 2050 TSM:FPAR
09:37:12.387 -> 2052 TSF:MSG:SEND,6-6-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
09:37:14.398 -> 4059 !TSM:FPAR:NO REPLY
09:37:14.398 -> 4061 TSM:FPAR
09:37:14.398 -> 4063 TSF:MSG:SEND,6-6-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
09:37:16.417 -> 6070 !TSM:FPAR:NO REPLY
09:37:16.417 -> 6072 TSM:FPAR
09:37:16.417 -> 6074 TSF:MSG:SEND,6-6-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
09:37:18.409 -> 8081 !TSM:FPAR:FAIL
09:37:18.409 -> 8082 TSM:FAIL:CNT=1
09:37:18.409 -> 8084 TSM:FAIL:DIS
09:37:18.409 -> 8086 TSF:TDI:TSL
09:37:28.413 -> 18088 TSM:FAIL:RE-INIT
...

Edit: There was no coding error, but I found that if MY_DEBUG_VERBOSE_RF24 is enabled, the code starts to work with IRQs.
And dumps:

09:47:01.018 ->  
09:47:01.018 ->  __  __       ____
09:47:01.018 -> |  \/  |_   _/ ___|  ___ _ __  ___  ___  _ __ ___
09:47:01.018 -> | |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
09:47:01.018 -> | |  | | |_| |___| |  __/ | | \__ \  _  | |  \__ \
09:47:01.018 -> |_|  |_|\__, |____/ \___|_| |_|___/\___/|_|  |___/
09:47:01.018 ->         |___/                      2.3.1
09:47:01.018 -> 
09:47:01.018 -> 16 MCO:BGN:INIT NODE,CP=RNNNA---,REL=255,VER=2.3.1
09:47:01.018 -> 26 MCO:BGN:BFR
09:47:01.018 -> 27 TSM:INIT
09:47:01.018 -> 28 TSF:WUR:MS=0
09:47:01.018 -> 30 RF24:INIT:PIN,CE=9,CS=10
09:47:01.053 -> 32 RF24:SBY
09:47:01.053 -> 33 RF24:WBR:REG=0,VAL=14
09:47:01.053 -> 40 RF24:WBR:REG=3,VAL=3
09:47:01.053 -> 43 RF24:WBR:REG=4,VAL=95
09:47:01.053 -> 45 RF24:WBR:REG=5,VAL=108
09:47:01.053 -> 48 RF24:WBR:REG=6,VAL=37
09:47:01.053 -> 50 RF24:WBR:REG=29,VAL=4
09:47:01.053 -> 52 RF24:RBR:REG=29,VAL=4
09:47:01.053 -> 54 RF24:RBR:REG=6,VAL=37
09:47:01.053 -> 56 RF24:RBR:REG=5,VAL=108
09:47:01.053 -> 59 RF24:WBR:REG=2,VAL=2
09:47:01.053 -> 61 RF24:WBR:REG=1,VAL=0
09:47:01.053 -> 63 RF24:WBR:REG=28,VAL=3
09:47:01.053 -> 65 RF24:FRX
09:47:01.053 -> 66 RF24:FTX
09:47:01.088 -> 67 RF24:WBR:REG=7,VAL=112
09:47:01.088 -> 70 TSM:INIT:TSP OK
09:47:01.088 -> 71 RF24:WBR:REG=2,VAL=3
09:47:01.088 -> 73 RF24:WBR:REG=1,VAL=1
09:47:01.088 -> 76 RF24:STL
09:47:01.088 -> 77 RF24:WBR:REG=0,VAL=15
09:47:01.088 -> 79 RF24:WBR:REG=10,VAL=6
09:47:01.088 -> 81 TSF:SID:OK,ID=6
09:47:01.088 -> 83 TSM:FPAR
09:47:01.088 -> 84 RF24:SPL
09:47:01.088 -> 86 RF24:WBR:REG=0,VAL=14
09:47:01.088 -> 88 RF24:OWP:RCPT=255
09:47:01.088 -> 90 RF24:WBR:REG=10,VAL=255
09:47:01.088 -> 92 RF24:WBR:REG=16,VAL=255
09:47:01.088 -> 95 RF24:TXM:TO=255,LEN=7
09:47:01.088 -> 97 RF24:FTX
09:47:01.088 -> 98 RF24:TXM:IRQ_PIN_WAIT
09:47:01.088 -> 100 RF24:TXM:IRQ_PIN_WAIT
09:47:01.088 -> 101 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 103 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 105 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 107 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 108 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 110 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 112 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 113 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 115 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 117 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 118 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 120 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 122 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 124 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 125 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 128 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 130 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 131 RF24:TXM:IRQ_PIN_WAIT
09:47:01.123 -> 133 RF24:RBR:REG=8,VAL=31
09:47:01.123 -> 135 RF24:TXM:AIR=1188,EFF=37112,OBS=15,CNT= 31
09:47:01.158 -> 140 RF24:WBR:REG=7,VAL=48
09:47:01.158 -> 142 ?RF24:TXM:MAX_RT
09:47:01.158 -> 144 RF24:FTX
09:47:01.158 -> 145 RF24:STL
09:47:01.158 -> 146 RF24:WBR:REG=0,VAL=15
09:47:01.158 -> 148 RF24:WBR:REG=10,VAL=6
09:47:01.158 -> 151 TSF:MSG:SEND,6-6-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:01.610 -> 603 RF24:RXM:LEN=8
09:47:01.610 -> 605 RF24:WBR:REG=7,VAL=64
09:47:01.610 -> 607 TSF:MSG:READ,0-0-6,s=255,c=3,t=8,pt=1,l=1,sg=0:0
09:47:01.610 -> 612 TSF:MSG:FPAR OK,ID=0,D=1
09:47:03.178 -> 2158 TSM:FPAR:OK
09:47:03.178 -> 2159 TSM:ID
09:47:03.178 -> 2160 TSM:ID:OK
09:47:03.178 -> 2162 TSM:UPL
09:47:03.178 -> 2163 RF24:SPL
09:47:03.178 -> 2164 RF24:WBR:REG=0,VAL=14
09:47:03.178 -> 2167 RF24:OWP:RCPT=0
09:47:03.178 -> 2169 RF24:WBR:REG=10,VAL=0
09:47:03.178 -> 2171 RF24:WBR:REG=16,VAL=0
09:47:03.178 -> 2174 RF24:TXM:TO=0,LEN=8
09:47:03.178 -> 2177 RF24:FTX
09:47:03.178 -> 2178 RF24:TXM:IRQ_PIN_WAIT
09:47:03.178 -> 2180 RF24:RBR:REG=8,VAL=16
09:47:03.178 -> 2183 RF24:TXM:AIR=1220,EFF=4388,OBS=0,CNT= 50
09:47:03.178 -> 2187 RF24:WBR:REG=7,VAL=48
09:47:03.178 -> 2189 RF24:STL
09:47:03.178 -> 2190 RF24:WBR:REG=0,VAL=15
09:47:03.178 -> 2193 RF24:WBR:REG=10,VAL=6
09:47:03.213 -> 2195 TSF:MSG:SEND,6-6-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
09:47:03.213 -> 2201 RF24:RXM:LEN=8
09:47:03.213 -> 2203 RF24:WBR:REG=7,VAL=64
09:47:03.213 -> 2206 TSF:MSG:READ,0-0-6,s=255,c=3,t=25,pt=1,l=1,sg=0:1
09:47:03.213 -> 2211 TSF:MSG:PONG RECV,HP=1
09:47:03.213 -> 2213 TSM:UPL:OK
09:47:03.213 -> 2215 TSM:READY:ID=6,PAR=0,DIS=1
09:47:03.213 -> 2219 RF24:SPL
09:47:03.213 -> 2220 RF24:WBR:REG=0,VAL=14
09:47:03.213 -> 2223 RF24:OWP:RCPT=0
09:47:03.213 -> 2224 RF24:WBR:REG=10,VAL=0
09:47:03.213 -> 2227 RF24:WBR:REG=16,VAL=0
09:47:03.248 -> 2229 RF24:TXM:TO=0,LEN=9
09:47:03.248 -> 2232 RF24:FTX
09:47:03.248 -> 2233 RF24:TXM:IRQ_PIN_WAIT
09:47:03.248 -> 2235 RF24:RBR:REG=8,VAL=16
09:47:03.248 -> 2237 RF24:TXM:AIR=1252,EFF=4380,OBS=0,CNT= 50
09:47:03.248 -> 2241 RF24:WBR:REG=7,VAL=48
09:47:03.248 -> 2244 RF24:STL
09:47:03.248 -> 2245 RF24:WBR:REG=0,VAL=15
09:47:03.248 -> 2247 RF24:WBR:REG=10,VAL=6
09:47:03.248 -> 2250 TSF:MSG:SEND,6-6-0-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
09:47:03.248 -> 2256 RF24:RXM:LEN=9
09:47:03.248 -> 2258 RF24:WBR:REG=7,VAL=64
09:47:03.248 -> 2262 TSF:MSG:READ,0-0-6,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
09:47:03.283 -> 2267 RF24:SPL
09:47:03.283 -> 2268 RF24:WBR:REG=0,VAL=14
09:47:03.283 -> 2271 RF24:OWP:RCPT=0
09:47:03.283 -> 2273 RF24:WBR:REG=10,VAL=0
09:47:03.283 -> 2275 RF24:WBR:REG=16,VAL=0
09:47:03.283 -> 2278 RF24:TXM:TO=0,LEN=12
09:47:03.283 -> 2280 RF24:FTX
09:47:03.283 -> 2281 RF24:TXM:IRQ_PIN_WAIT
09:47:03.283 -> 2283 RF24:RBR:REG=8,VAL=16
09:47:03.283 -> 2286 RF24:TXM:AIR=1348,EFF=4388,OBS=0,CNT= 50
09:47:03.283 -> 2290 RF24:WBR:REG=7,VAL=48
09:47:03.283 -> 2292 RF24:STL
09:47:03.283 -> 2293 RF24:WBR:REG=0,VAL=15
09:47:03.283 -> 2296 RF24:WBR:REG=10,VAL=6
09:47:03.317 -> 2298 TSF:MSG:SEND,6-6-0-0,s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=OK:2.3.1
09:47:03.317 -> 2306 RF24:SPL
09:47:03.317 -> 2307 RF24:WBR:REG=0,VAL=14
09:47:03.317 -> 2310 RF24:OWP:RCPT=0
09:47:03.317 -> 2312 RF24:WBR:REG=10,VAL=0
09:47:03.317 -> 2314 RF24:WBR:REG=16,VAL=0
09:47:03.317 -> 2317 RF24:TXM:TO=0,LEN=8
09:47:03.317 -> 2319 RF24:FTX
09:47:03.317 -> 2320 RF24:TXM:IRQ_PIN_WAIT
09:47:03.317 -> 2322 RF24:RBR:REG=8,VAL=16
09:47:03.317 -> 2324 RF24:TXM:AIR=1220,EFF=4380,OBS=0,CNT= 50
09:47:03.317 -> 2328 RF24:WBR:REG=7,VAL=48
09:47:03.352 -> 2331 RF24:STL
09:47:03.352 -> 2332 RF24:WBR:REG=0,VAL=15
09:47:03.352 -> 2335 RF24:WBR:REG=10,VAL=6
09:47:03.352 -> 2337 TSF:MSG:SEND,6-6-0-0,s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=OK:0
09:47:03.352 -> 2343 RF24:RXM:LEN=8
09:47:03.352 -> 2345 RF24:WBR:REG=7,VAL=64
09:47:03.352 -> 2348 TSF:MSG:READ,0-0-6,s=255,c=3,t=6,pt=0,l=1,sg=0:M
09:47:03.352 -> 2353 RF24:RXM:LEN=8
09:47:03.352 -> 2355 RF24:WBR:REG=7,VAL=64
09:47:03.352 -> 2358 TSF:MSG:READ,0-0-6,s=255,c=3,t=6,pt=0,l=1,sg=0:M
09:47:03.352 -> 2363 RF24:SPL
09:47:03.352 -> 2364 RF24:WBR:REG=0,VAL=14
09:47:03.352 -> 2367 RF24:OWP:RCPT=0
09:47:03.387 -> 2368 RF24:WBR:REG=10,VAL=0
09:47:03.387 -> 2371 RF24:WBR:REG=16,VAL=0
09:47:03.387 -> 2373 RF24:TXM:TO=0,LEN=26
09:47:03.387 -> 2376 RF24:FTX
09:47:03.387 -> 2377 RF24:TXM:IRQ_PIN_WAIT
09:47:03.387 -> 2379 RF24:RBR:REG=8,VAL=16
09:47:03.387 -> 2381 RF24:TXM:AIR=1796,EFF=4384,OBS=0,CNT= 50
09:47:03.387 -> 2385 RF24:WBR:REG=7,VAL=48
09:47:03.387 -> 2388 RF24:STL
09:47:03.387 -> 2390 RF24:WBR:REG=0,VAL=15
09:47:03.387 -> 2393 RF24:WBR:REG=10,VAL=6
09:47:03.387 -> 2395 TSF:MSG:SEND,6-6-0-0,s=255,c=3,t=11,pt=0,l=19,sg=0,ft=0,st=OK:MySimple_MultiRelay
09:47:03.422 -> 2403 RF24:SPL
09:47:03.422 -> 2404 RF24:WBR:REG=0,VAL=14
09:47:03.422 -> 2407 RF24:OWP:RCPT=0
09:47:03.422 -> 2409 RF24:WBR:REG=10,VAL=0
09:47:03.422 -> 2411 RF24:WBR:REG=16,VAL=0
09:47:03.422 -> 2414 RF24:TXM:TO=0,LEN=10
09:47:03.422 -> 2416 RF24:FTX
09:47:03.422 -> 2417 RF24:TXM:IRQ_PIN_WAIT
09:47:03.422 -> 2419 RF24:RBR:REG=8,VAL=16
09:47:03.422 -> 2422 RF24:TXM:AIR=1284,EFF=4380,OBS=0,CNT= 50
09:47:03.422 -> 2426 RF24:WBR:REG=7,VAL=48
09:47:03.422 -> 2428 RF24:STL
09:47:03.422 -> 2429 RF24:WBR:REG=0,VAL=15
09:47:03.422 -> 2433 RF24:WBR:REG=10,VAL=6
09:47:03.422 -> 2435 TSF:MSG:SEND,6-6-0-0,s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=OK:1.2
09:47:03.456 -> 2442 RF24:SPL
09:47:03.456 -> 2443 RF24:WBR:REG=0,VAL=14
09:47:03.456 -> 2446 RF24:OWP:RCPT=0
09:47:03.456 -> 2447 RF24:WBR:REG=10,VAL=0
09:47:03.456 -> 2450 RF24:WBR:REG=16,VAL=0
09:47:03.456 -> 2452 RF24:TXM:TO=0,LEN=13
09:47:03.456 -> 2455 RF24:FTX
09:47:03.456 -> 2456 RF24:TXM:IRQ_PIN_WAIT
09:47:03.456 -> 2458 RF24:RBR:REG=8,VAL=16
09:47:03.456 -> 2460 RF24:TXM:AIR=1380,EFF=4380,OBS=0,CNT= 50
09:47:03.456 -> 2464 RF24:WBR:REG=7,VAL=48
09:47:03.456 -> 2467 RF24:STL
09:47:03.456 -> 2468 RF24:WBR:REG=0,VAL=15
09:47:03.456 -> 2471 RF24:WBR:REG=10,VAL=6
09:47:03.491 -> 2473 TSF:MSG:SEND,6-6-0-0,s=0,c=0,t=3,pt=0,l=6,sg=0,ft=0,st=OK:Zone 1
09:47:03.526 -> 2530 RF24:SPL
09:47:03.526 -> 2531 RF24:WBR:REG=0,VAL=14
09:47:03.526 -> 2534 RF24:OWP:RCPT=0
09:47:03.526 -> 2535 RF24:WBR:REG=10,VAL=0
09:47:03.526 -> 2538 RF24:WBR:REG=16,VAL=0
09:47:03.526 -> 2540 RF24:TXM:TO=0,LEN=7
09:47:03.561 -> 2543 RF24:FTX
09:47:03.561 -> 2544 RF24:TXM:IRQ_PIN_WAIT
09:47:03.561 -> 2546 RF24:RBR:REG=8,VAL=16
09:47:03.561 -> 2548 RF24:TXM:AIR=1188,EFF=4380,OBS=0,CNT= 50
09:47:03.561 -> 2552 RF24:WBR:REG=7,VAL=48
09:47:03.561 -> 2555 RF24:STL
09:47:03.561 -> 2556 RF24:WBR:REG=0,VAL=15
09:47:03.561 -> 2558 RF24:WBR:REG=10,VAL=6
09:47:03.561 -> 2562 TSF:MSG:SEND,6-6-0-0,s=0,c=0,t=24,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:03.631 -> 2618 !MCO:SND:NODE NOT REG
09:47:03.666 -> 2670 RF24:SPL
09:47:03.666 -> 2671 RF24:WBR:REG=0,VAL=14
09:47:03.666 -> 2674 RF24:OWP:RCPT=0
09:47:03.666 -> 2675 RF24:WBR:REG=10,VAL=0
09:47:03.666 -> 2678 RF24:WBR:REG=16,VAL=0
09:47:03.666 -> 2680 RF24:TXM:TO=0,LEN=7
09:47:03.701 -> 2683 RF24:FTX
09:47:03.701 -> 2684 RF24:TXM:IRQ_PIN_WAIT
09:47:03.701 -> 2686 RF24:RBR:REG=8,VAL=16
09:47:03.701 -> 2689 RF24:TXM:AIR=1188,EFF=4384,OBS=0,CNT= 50
09:47:03.701 -> 2693 RF24:WBR:REG=7,VAL=48
09:47:03.701 -> 2696 RF24:STL
09:47:03.701 -> 2697 RF24:WBR:REG=0,VAL=15
09:47:03.701 -> 2699 RF24:WBR:REG=10,VAL=6
09:47:03.701 -> 2702 TSF:MSG:SEND,6-6-0-0,s=0,c=2,t=2,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:03.701 -> 2708 RF24:RXM:LEN=8
09:47:03.701 -> 2710 RF24:WBR:REG=7,VAL=64
09:47:03.701 -> 2712 TSF:MSG:READ,0-0-6,s=0,c=2,t=2,pt=0,l=1,sg=0:0
09:47:03.771 -> 2758 RF24:SPL
09:47:03.771 -> 2759 RF24:WBR:REG=0,VAL=14
09:47:03.771 -> 2762 RF24:OWP:RCPT=0
09:47:03.771 -> 2763 RF24:WBR:REG=10,VAL=0
09:47:03.771 -> 2766 RF24:WBR:REG=16,VAL=0
09:47:03.771 -> 2768 RF24:TXM:TO=0,LEN=13
09:47:03.771 -> 2771 RF24:FTX
09:47:03.771 -> 2772 RF24:TXM:IRQ_PIN_WAIT
09:47:03.771 -> 2775 RF24:RBR:REG=8,VAL=16
09:47:03.771 -> 2777 RF24:TXM:AIR=1380,EFF=4384,OBS=0,CNT= 50
09:47:03.771 -> 2781 RF24:WBR:REG=7,VAL=48
09:47:03.771 -> 2784 RF24:STL
09:47:03.805 -> 2785 RF24:WBR:REG=0,VAL=15
09:47:03.805 -> 2788 RF24:WBR:REG=10,VAL=6
09:47:03.805 -> 2790 TSF:MSG:SEND,6-6-0-0,s=1,c=0,t=3,pt=0,l=6,sg=0,ft=0,st=OK:Zone 2
09:47:03.839 -> 2846 RF24:SPL
09:47:03.839 -> 2847 RF24:WBR:REG=0,VAL=14
09:47:03.839 -> 2850 RF24:OWP:RCPT=0
09:47:03.839 -> 2851 RF24:WBR:REG=10,VAL=0
09:47:03.839 -> 2854 RF24:WBR:REG=16,VAL=0
09:47:03.874 -> 2856 RF24:TXM:TO=0,LEN=7
09:47:03.874 -> 2860 RF24:FTX
09:47:03.874 -> 2861 RF24:TXM:IRQ_PIN_WAIT
09:47:03.874 -> 2863 RF24:RBR:REG=8,VAL=16
09:47:03.874 -> 2865 RF24:TXM:AIR=1188,EFF=4380,OBS=0,CNT= 50
09:47:03.874 -> 2869 RF24:WBR:REG=7,VAL=48
09:47:03.874 -> 2872 RF24:STL
09:47:03.874 -> 2873 RF24:WBR:REG=0,VAL=15
09:47:03.874 -> 2875 RF24:WBR:REG=10,VAL=6
09:47:03.874 -> 2878 TSF:MSG:SEND,6-6-0-0,s=1,c=0,t=24,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:03.944 -> 2934 !MCO:SND:NODE NOT REG
09:47:03.979 -> 2987 RF24:SPL
09:47:03.979 -> 2988 RF24:WBR:REG=0,VAL=14
09:47:03.979 -> 2991 RF24:OWP:RCPT=0
09:47:03.979 -> 2992 RF24:WBR:REG=10,VAL=0
09:47:03.979 -> 2995 RF24:WBR:REG=16,VAL=0
09:47:04.013 -> 2997 RF24:TXM:TO=0,LEN=7
09:47:04.013 -> 3000 RF24:FTX
09:47:04.013 -> 3001 RF24:TXM:IRQ_PIN_WAIT
09:47:04.013 -> 3003 RF24:RBR:REG=8,VAL=16
09:47:04.013 -> 3005 RF24:TXM:AIR=1188,EFF=4380,OBS=0,CNT= 50
09:47:04.013 -> 3009 RF24:WBR:REG=7,VAL=48
09:47:04.013 -> 3012 RF24:STL
09:47:04.013 -> 3013 RF24:WBR:REG=0,VAL=15
09:47:04.013 -> 3015 RF24:WBR:REG=10,VAL=6
09:47:04.013 -> 3018 TSF:MSG:SEND,6-6-0-0,s=1,c=2,t=2,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:04.013 -> 3024 RF24:RXM:LEN=8
09:47:04.013 -> 3026 RF24:WBR:REG=7,VAL=64
09:47:04.047 -> 3028 TSF:MSG:READ,0-0-6,s=1,c=2,t=2,pt=0,l=1,sg=0:0
09:47:04.081 -> 3074 RF24:SPL
09:47:04.081 -> 3075 RF24:WBR:REG=0,VAL=14
09:47:04.081 -> 3078 RF24:OWP:RCPT=0
09:47:04.081 -> 3079 RF24:WBR:REG=10,VAL=0
09:47:04.081 -> 3082 RF24:WBR:REG=16,VAL=0
09:47:04.081 -> 3084 RF24:TXM:TO=0,LEN=13
09:47:04.081 -> 3087 RF24:FTX
09:47:04.081 -> 3088 RF24:TXM:IRQ_PIN_WAIT
09:47:04.081 -> 3090 RF24:RBR:REG=8,VAL=16
09:47:04.081 -> 3092 RF24:TXM:AIR=1380,EFF=4384,OBS=0,CNT= 50
09:47:04.081 -> 3096 RF24:WBR:REG=7,VAL=48
09:47:04.115 -> 3099 RF24:STL
09:47:04.115 -> 3100 RF24:WBR:REG=0,VAL=15
09:47:04.115 -> 3103 RF24:WBR:REG=10,VAL=6
09:47:04.115 -> 3105 TSF:MSG:SEND,6-6-0-0,s=2,c=0,t=3,pt=0,l=6,sg=0,ft=0,st=OK:Zone 3
09:47:04.149 -> 3161 RF24:SPL
09:47:04.149 -> 3162 RF24:WBR:REG=0,VAL=14
09:47:04.182 -> 3165 RF24:OWP:RCPT=0
09:47:04.182 -> 3166 RF24:WBR:REG=10,VAL=0
09:47:04.182 -> 3169 RF24:WBR:REG=16,VAL=0
09:47:04.182 -> 3171 RF24:TXM:TO=0,LEN=7
09:47:04.182 -> 3174 RF24:FTX
09:47:04.182 -> 3175 RF24:TXM:IRQ_PIN_WAIT
09:47:04.182 -> 3177 RF24:RBR:REG=8,VAL=16
09:47:04.182 -> 3179 RF24:TXM:AIR=1188,EFF=4384,OBS=0,CNT= 50
09:47:04.182 -> 3183 RF24:WBR:REG=7,VAL=48
09:47:04.182 -> 3186 RF24:STL
09:47:04.182 -> 3187 RF24:WBR:REG=0,VAL=15
09:47:04.182 -> 3189 RF24:WBR:REG=10,VAL=6
09:47:04.182 -> 3192 TSF:MSG:SEND,6-6-0-0,s=2,c=0,t=24,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:04.250 -> 3248 !MCO:SND:NODE NOT REG
09:47:04.319 -> 3300 RF24:SPL
09:47:04.319 -> 3301 RF24:WBR:REG=0,VAL=14
09:47:04.319 -> 3304 RF24:OWP:RCPT=0
09:47:04.319 -> 3305 RF24:WBR:REG=10,VAL=0
09:47:04.319 -> 3308 RF24:WBR:REG=16,VAL=0
09:47:04.319 -> 3310 RF24:TXM:TO=0,LEN=7
09:47:04.319 -> 3313 RF24:FTX
09:47:04.319 -> 3314 RF24:TXM:IRQ_PIN_WAIT
09:47:04.319 -> 3316 RF24:RBR:REG=8,VAL=16
09:47:04.319 -> 3318 RF24:TXM:AIR=1188,EFF=4380,OBS=0,CNT= 50
09:47:04.319 -> 3322 RF24:WBR:REG=7,VAL=48
09:47:04.319 -> 3325 RF24:STL
09:47:04.319 -> 3326 RF24:WBR:REG=0,VAL=15
09:47:04.319 -> 3329 RF24:WBR:REG=10,VAL=6
09:47:04.319 -> 3332 TSF:MSG:SEND,6-6-0-0,s=2,c=2,t=2,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:04.353 -> 3338 RF24:RXM:LEN=8
09:47:04.353 -> 3340 RF24:WBR:REG=7,VAL=64
09:47:04.353 -> 3342 TSF:MSG:READ,0-0-6,s=2,c=2,t=2,pt=0,l=1,sg=0:0
09:47:04.387 -> 3388 RF24:SPL
09:47:04.387 -> 3389 RF24:WBR:REG=0,VAL=14
09:47:04.387 -> 3392 RF24:OWP:RCPT=0
09:47:04.387 -> 3393 RF24:WBR:REG=10,VAL=0
09:47:04.387 -> 3396 RF24:WBR:REG=16,VAL=0
09:47:04.387 -> 3398 RF24:TXM:TO=0,LEN=13
09:47:04.387 -> 3401 RF24:FTX
09:47:04.387 -> 3402 RF24:TXM:IRQ_PIN_WAIT
09:47:04.421 -> 3404 RF24:RBR:REG=8,VAL=16
09:47:04.421 -> 3406 RF24:TXM:AIR=1380,EFF=4380,OBS=0,CNT= 50
09:47:04.421 -> 3410 RF24:WBR:REG=7,VAL=48
09:47:04.421 -> 3414 RF24:STL
09:47:04.421 -> 3415 RF24:WBR:REG=0,VAL=15
09:47:04.421 -> 3418 RF24:WBR:REG=10,VAL=6
09:47:04.421 -> 3420 TSF:MSG:SEND,6-6-0-0,s=3,c=0,t=3,pt=0,l=6,sg=0,ft=0,st=OK:Zone 4
09:47:04.489 -> 3476 RF24:SPL
09:47:04.489 -> 3477 RF24:WBR:REG=0,VAL=14
09:47:04.489 -> 3480 RF24:OWP:RCPT=0
09:47:04.489 -> 3481 RF24:WBR:REG=10,VAL=0
09:47:04.489 -> 3484 RF24:WBR:REG=16,VAL=0
09:47:04.489 -> 3486 RF24:TXM:TO=0,LEN=7
09:47:04.489 -> 3489 RF24:FTX
09:47:04.489 -> 3490 RF24:TXM:IRQ_PIN_WAIT
09:47:04.489 -> 3492 RF24:RBR:REG=8,VAL=16
09:47:04.489 -> 3494 RF24:TXM:AIR=1188,EFF=4384,OBS=0,CNT= 50
09:47:04.489 -> 3499 RF24:WBR:REG=7,VAL=48
09:47:04.489 -> 3502 RF24:STL
09:47:04.523 -> 3503 RF24:WBR:REG=0,VAL=15
09:47:04.523 -> 3505 RF24:WBR:REG=10,VAL=6
09:47:04.523 -> 3508 TSF:MSG:SEND,6-6-0-0,s=3,c=0,t=24,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:04.556 -> 3564 !MCO:SND:NODE NOT REG
09:47:04.625 -> 3616 RF24:SPL
09:47:04.625 -> 3617 RF24:WBR:REG=0,VAL=14
09:47:04.625 -> 3620 RF24:OWP:RCPT=0
09:47:04.625 -> 3621 RF24:WBR:REG=10,VAL=0
09:47:04.625 -> 3624 RF24:WBR:REG=16,VAL=0
09:47:04.625 -> 3627 RF24:TXM:TO=0,LEN=7
09:47:04.625 -> 3630 RF24:FTX
09:47:04.625 -> 3631 RF24:TXM:IRQ_PIN_WAIT
09:47:04.625 -> 3633 RF24:RBR:REG=8,VAL=16
09:47:04.625 -> 3635 RF24:TXM:AIR=1188,EFF=4384,OBS=0,CNT= 50
09:47:04.625 -> 3639 RF24:WBR:REG=7,VAL=48
09:47:04.660 -> 3642 RF24:STL
09:47:04.660 -> 3643 RF24:WBR:REG=0,VAL=15
09:47:04.660 -> 3645 RF24:WBR:REG=10,VAL=6
09:47:04.660 -> 3648 TSF:MSG:SEND,6-6-0-0,s=3,c=2,t=2,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:04.660 -> 3654 RF24:RXM:LEN=8
09:47:04.660 -> 3656 RF24:WBR:REG=7,VAL=64
09:47:04.660 -> 3658 TSF:MSG:READ,0-0-6,s=3,c=2,t=2,pt=0,l=1,sg=0:0
09:47:04.695 -> 3704 RF24:SPL
09:47:04.695 -> 3705 RF24:WBR:REG=0,VAL=14
09:47:04.695 -> 3708 RF24:OWP:RCPT=0
09:47:04.695 -> 3709 RF24:WBR:REG=10,VAL=0
09:47:04.730 -> 3713 RF24:WBR:REG=16,VAL=0
09:47:04.730 -> 3715 RF24:TXM:TO=0,LEN=13
09:47:04.730 -> 3718 RF24:FTX
09:47:04.730 -> 3719 RF24:TXM:IRQ_PIN_WAIT
09:47:04.730 -> 3721 RF24:RBR:REG=8,VAL=16
09:47:04.730 -> 3723 RF24:TXM:AIR=1380,EFF=4384,OBS=0,CNT= 50
09:47:04.730 -> 3727 RF24:WBR:REG=7,VAL=48
09:47:04.730 -> 3730 RF24:STL
09:47:04.730 -> 3731 RF24:WBR:REG=0,VAL=15
09:47:04.730 -> 3734 RF24:WBR:REG=10,VAL=6
09:47:04.730 -> 3736 TSF:MSG:SEND,6-6-0-0,s=4,c=0,t=3,pt=0,l=6,sg=0,ft=0,st=OK:Zone 5
09:47:04.800 -> 3792 RF24:SPL
09:47:04.800 -> 3793 RF24:WBR:REG=0,VAL=14
09:47:04.800 -> 3796 RF24:OWP:RCPT=0
09:47:04.800 -> 3798 RF24:WBR:REG=10,VAL=0
09:47:04.800 -> 3801 RF24:WBR:REG=16,VAL=0
09:47:04.800 -> 3803 RF24:TXM:TO=0,LEN=7
09:47:04.800 -> 3806 RF24:FTX
09:47:04.800 -> 3807 RF24:TXM:IRQ_PIN_WAIT
09:47:04.800 -> 3809 RF24:RBR:REG=8,VAL=16
09:47:04.800 -> 3811 RF24:TXM:AIR=1188,EFF=4384,OBS=0,CNT= 50
09:47:04.800 -> 3815 RF24:WBR:REG=7,VAL=48
09:47:04.835 -> 3818 RF24:STL
09:47:04.835 -> 3819 RF24:WBR:REG=0,VAL=15
09:47:04.835 -> 3821 RF24:WBR:REG=10,VAL=6
09:47:04.835 -> 3824 TSF:MSG:SEND,6-6-0-0,s=4,c=0,t=24,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:04.869 -> 3880 !MCO:SND:NODE NOT REG
09:47:04.936 -> 3933 RF24:SPL
09:47:04.936 -> 3934 RF24:WBR:REG=0,VAL=14
09:47:04.936 -> 3937 RF24:OWP:RCPT=0
09:47:04.936 -> 3938 RF24:WBR:REG=10,VAL=0
09:47:04.936 -> 3941 RF24:WBR:REG=16,VAL=0
09:47:04.936 -> 3943 RF24:TXM:TO=0,LEN=7
09:47:04.936 -> 3946 RF24:FTX
09:47:04.936 -> 3947 RF24:TXM:IRQ_PIN_WAIT
09:47:04.936 -> 3949 RF24:RBR:REG=8,VAL=16
09:47:04.970 -> 3951 RF24:TXM:AIR=1188,EFF=4384,OBS=0,CNT= 50
09:47:04.970 -> 3955 RF24:WBR:REG=7,VAL=48
09:47:04.970 -> 3958 RF24:STL
09:47:04.970 -> 3959 RF24:WBR:REG=0,VAL=15
09:47:04.970 -> 3961 RF24:WBR:REG=10,VAL=6
09:47:04.970 -> 3964 TSF:MSG:SEND,6-6-0-0,s=4,c=2,t=2,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:04.970 -> 3971 RF24:RXM:LEN=8
09:47:04.970 -> 3973 RF24:WBR:REG=7,VAL=64
09:47:04.970 -> 3975 TSF:MSG:READ,0-0-6,s=4,c=2,t=2,pt=0,l=1,sg=0:0
09:47:05.038 -> 4021 RF24:SPL
09:47:05.038 -> 4022 RF24:WBR:REG=0,VAL=14
09:47:05.038 -> 4025 RF24:OWP:RCPT=0
09:47:05.038 -> 4026 RF24:WBR:REG=10,VAL=0
09:47:05.038 -> 4029 RF24:WBR:REG=16,VAL=0
09:47:05.038 -> 4031 RF24:TXM:TO=0,LEN=13
09:47:05.038 -> 4034 RF24:FTX
09:47:05.038 -> 4035 RF24:TXM:IRQ_PIN_WAIT
09:47:05.038 -> 4037 RF24:RBR:REG=8,VAL=16
09:47:05.038 -> 4039 RF24:TXM:AIR=1380,EFF=4380,OBS=0,CNT= 50
09:47:05.038 -> 4043 RF24:WBR:REG=7,VAL=48
09:47:05.038 -> 4046 RF24:STL
09:47:05.038 -> 4047 RF24:WBR:REG=0,VAL=15
09:47:05.038 -> 4050 RF24:WBR:REG=10,VAL=6
09:47:05.038 -> 4052 TSF:MSG:SEND,6-6-0-0,s=5,c=0,t=3,pt=0,l=6,sg=0,ft=0,st=OK:Zone 6
09:47:05.106 -> 4109 RF24:SPL
09:47:05.106 -> 4110 RF24:WBR:REG=0,VAL=14
09:47:05.106 -> 4113 RF24:OWP:RCPT=0
09:47:05.106 -> 4114 RF24:WBR:REG=10,VAL=0
09:47:05.106 -> 4117 RF24:WBR:REG=16,VAL=0
09:47:05.106 -> 4119 RF24:TXM:TO=0,LEN=7
09:47:05.141 -> 4122 RF24:FTX
09:47:05.141 -> 4123 RF24:TXM:IRQ_PIN_WAIT
09:47:05.141 -> 4125 RF24:RBR:REG=8,VAL=16
09:47:05.141 -> 4127 RF24:TXM:AIR=1188,EFF=4380,OBS=0,CNT= 50
09:47:05.141 -> 4131 RF24:WBR:REG=7,VAL=48
09:47:05.141 -> 4134 RF24:STL
09:47:05.141 -> 4135 RF24:WBR:REG=0,VAL=15
09:47:05.141 -> 4137 RF24:WBR:REG=10,VAL=6
09:47:05.141 -> 4141 TSF:MSG:SEND,6-6-0-0,s=5,c=0,t=24,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:05.211 -> 4197 !MCO:SND:NODE NOT REG
09:47:05.246 -> 4249 RF24:SPL
09:47:05.246 -> 4250 RF24:WBR:REG=0,VAL=14
09:47:05.246 -> 4253 RF24:OWP:RCPT=0
09:47:05.246 -> 4254 RF24:WBR:REG=10,VAL=0
09:47:05.246 -> 4257 RF24:WBR:REG=16,VAL=0
09:47:05.246 -> 4259 RF24:TXM:TO=0,LEN=7
09:47:05.281 -> 4262 RF24:FTX
09:47:05.281 -> 4263 RF24:TXM:IRQ_PIN_WAIT
09:47:05.281 -> 4265 RF24:RBR:REG=8,VAL=16
09:47:05.281 -> 4268 RF24:TXM:AIR=1188,EFF=4384,OBS=0,CNT= 50
09:47:05.281 -> 4272 RF24:WBR:REG=7,VAL=48
09:47:05.281 -> 4275 RF24:STL
09:47:05.281 -> 4276 RF24:WBR:REG=0,VAL=15
09:47:05.281 -> 4278 RF24:WBR:REG=10,VAL=6
09:47:05.281 -> 4281 TSF:MSG:SEND,6-6-0-0,s=5,c=2,t=2,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:05.281 -> 4287 RF24:RXM:LEN=8
09:47:05.281 -> 4289 RF24:WBR:REG=7,VAL=64
09:47:05.281 -> 4291 TSF:MSG:READ,0-0-6,s=5,c=2,t=2,pt=0,l=1,sg=0:0
09:47:05.350 -> 4337 RF24:SPL
09:47:05.350 -> 4338 RF24:WBR:REG=0,VAL=14
09:47:05.350 -> 4341 RF24:OWP:RCPT=0
09:47:05.350 -> 4342 RF24:WBR:REG=10,VAL=0
09:47:05.350 -> 4345 RF24:WBR:REG=16,VAL=0
09:47:05.350 -> 4347 RF24:TXM:TO=0,LEN=13
09:47:05.350 -> 4350 RF24:FTX
09:47:05.350 -> 4352 RF24:TXM:IRQ_PIN_WAIT
09:47:05.350 -> 4354 RF24:RBR:REG=8,VAL=16
09:47:05.350 -> 4356 RF24:TXM:AIR=1380,EFF=4384,OBS=0,CNT= 50
09:47:05.350 -> 4360 RF24:WBR:REG=7,VAL=48
09:47:05.350 -> 4363 RF24:STL
09:47:05.350 -> 4364 RF24:WBR:REG=0,VAL=15
09:47:05.350 -> 4367 RF24:WBR:REG=10,VAL=6
09:47:05.385 -> 4369 TSF:MSG:SEND,6-6-0-0,s=6,c=0,t=3,pt=0,l=6,sg=0,ft=0,st=OK:Zone 7
09:47:05.420 -> 4425 RF24:SPL
09:47:05.420 -> 4426 RF24:WBR:REG=0,VAL=14
09:47:05.420 -> 4429 RF24:OWP:RCPT=0
09:47:05.420 -> 4430 RF24:WBR:REG=10,VAL=0
09:47:05.420 -> 4433 RF24:WBR:REG=16,VAL=0
09:47:05.420 -> 4435 RF24:TXM:TO=0,LEN=7
09:47:05.455 -> 4439 RF24:FTX
09:47:05.455 -> 4440 RF24:TXM:IRQ_PIN_WAIT
09:47:05.455 -> 4442 RF24:RBR:REG=8,VAL=16
09:47:05.455 -> 4444 RF24:TXM:AIR=1188,EFF=4384,OBS=0,CNT= 50
09:47:05.455 -> 4448 RF24:WBR:REG=7,VAL=48
09:47:05.455 -> 4451 RF24:STL
09:47:05.455 -> 4452 RF24:WBR:REG=0,VAL=15
09:47:05.455 -> 4454 RF24:WBR:REG=10,VAL=6
09:47:05.455 -> 4457 TSF:MSG:SEND,6-6-0-0,s=6,c=0,t=24,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:05.525 -> 4513 !MCO:SND:NODE NOT REG
09:47:05.560 -> 4566 RF24:SPL
09:47:05.560 -> 4567 RF24:WBR:REG=0,VAL=14
09:47:05.560 -> 4570 RF24:OWP:RCPT=0
09:47:05.560 -> 4571 RF24:WBR:REG=10,VAL=0
09:47:05.560 -> 4574 RF24:WBR:REG=16,VAL=0
09:47:05.595 -> 4576 RF24:TXM:TO=0,LEN=7
09:47:05.595 -> 4579 RF24:FTX
09:47:05.595 -> 4580 RF24:TXM:IRQ_PIN_WAIT
09:47:05.595 -> 4582 RF24:RBR:REG=8,VAL=16
09:47:05.595 -> 4584 RF24:TXM:AIR=1188,EFF=4380,OBS=0,CNT= 50
09:47:05.595 -> 4588 RF24:WBR:REG=7,VAL=48
09:47:05.595 -> 4591 RF24:STL
09:47:05.595 -> 4592 RF24:WBR:REG=0,VAL=15
09:47:05.595 -> 4594 RF24:WBR:REG=10,VAL=6
09:47:05.595 -> 4597 TSF:MSG:SEND,6-6-0-0,s=6,c=2,t=2,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:05.595 -> 4603 RF24:RXM:LEN=8
09:47:05.595 -> 4605 RF24:WBR:REG=7,VAL=64
09:47:05.595 -> 4608 TSF:MSG:READ,0-0-6,s=6,c=2,t=2,pt=0,l=1,sg=0:0
09:47:05.665 -> 4653 RF24:SPL
09:47:05.665 -> 4654 RF24:WBR:REG=0,VAL=14
09:47:05.665 -> 4657 RF24:OWP:RCPT=0
09:47:05.665 -> 4658 RF24:WBR:REG=10,VAL=0
09:47:05.665 -> 4661 RF24:WBR:REG=16,VAL=0
09:47:05.665 -> 4663 RF24:TXM:TO=0,LEN=13
09:47:05.665 -> 4666 RF24:FTX
09:47:05.665 -> 4667 RF24:TXM:IRQ_PIN_WAIT
09:47:05.665 -> 4669 RF24:RBR:REG=8,VAL=16
09:47:05.665 -> 4671 RF24:TXM:AIR=1380,EFF=4384,OBS=0,CNT= 50
09:47:05.665 -> 4675 RF24:WBR:REG=7,VAL=48
09:47:05.665 -> 4678 RF24:STL
09:47:05.699 -> 4679 RF24:WBR:REG=0,VAL=15
09:47:05.699 -> 4682 RF24:WBR:REG=10,VAL=6
09:47:05.699 -> 4684 TSF:MSG:SEND,6-6-0-0,s=7,c=0,t=3,pt=0,l=6,sg=0,ft=0,st=OK:Zone 8
09:47:05.734 -> 4740 RF24:SPL
09:47:05.734 -> 4741 RF24:WBR:REG=0,VAL=14
09:47:05.734 -> 4744 RF24:OWP:RCPT=0
09:47:05.734 -> 4745 RF24:WBR:REG=10,VAL=0
09:47:05.734 -> 4748 RF24:WBR:REG=16,VAL=0
09:47:05.734 -> 4750 RF24:TXM:TO=0,LEN=7
09:47:05.769 -> 4753 RF24:FTX
09:47:05.769 -> 4754 RF24:TXM:IRQ_PIN_WAIT
09:47:05.769 -> 4756 RF24:RBR:REG=8,VAL=16
09:47:05.769 -> 4758 RF24:TXM:AIR=1188,EFF=4384,OBS=0,CNT= 50
09:47:05.769 -> 4762 RF24:WBR:REG=7,VAL=48
09:47:05.769 -> 4765 RF24:STL
09:47:05.769 -> 4766 RF24:WBR:REG=0,VAL=15
09:47:05.769 -> 4768 RF24:WBR:REG=10,VAL=6
09:47:05.769 -> 4771 TSF:MSG:SEND,6-6-0-0,s=7,c=0,t=24,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:05.839 -> 4827 !MCO:SND:NODE NOT REG
09:47:05.874 -> 4879 RF24:SPL
09:47:05.874 -> 4880 RF24:WBR:REG=0,VAL=14
09:47:05.874 -> 4883 RF24:OWP:RCPT=0
09:47:05.874 -> 4884 RF24:WBR:REG=10,VAL=0
09:47:05.874 -> 4887 RF24:WBR:REG=16,VAL=0
09:47:05.874 -> 4889 RF24:TXM:TO=0,LEN=7
09:47:05.909 -> 4892 RF24:FTX
09:47:05.909 -> 4893 RF24:TXM:IRQ_PIN_WAIT
09:47:05.909 -> 4895 RF24:RBR:REG=8,VAL=16
09:47:05.909 -> 4897 RF24:TXM:AIR=1188,EFF=4380,OBS=0,CNT= 50
09:47:05.909 -> 4901 RF24:WBR:REG=7,VAL=48
09:47:05.909 -> 4904 RF24:STL
09:47:05.909 -> 4905 RF24:WBR:REG=0,VAL=15
09:47:05.909 -> 4908 RF24:WBR:REG=10,VAL=6
09:47:05.909 -> 4911 TSF:MSG:SEND,6-6-0-0,s=7,c=2,t=2,pt=0,l=0,sg=0,ft=0,st=OK:
09:47:05.909 -> 4917 RF24:RXM:LEN=8
09:47:05.909 -> 4919 RF24:WBR:REG=7,VAL=64
09:47:05.909 -> 4921 TSF:MSG:READ,0-0-6,s=7,c=2,t=2,pt=0,l=1,sg=0:0
09:47:05.979 -> 4967 MCO:REG:REQ
09:47:05.979 -> 4968 RF24:SPL
09:47:05.979 -> 4970 RF24:WBR:REG=0,VAL=14
09:47:05.979 -> 4972 RF24:OWP:RCPT=0
09:47:05.979 -> 4974 RF24:WBR:REG=10,VAL=0
09:47:05.979 -> 4976 RF24:WBR:REG=16,VAL=0
09:47:05.979 -> 4979 RF24:TXM:TO=0,LEN=8
09:47:05.979 -> 4981 RF24:FTX
09:47:05.979 -> 4983 RF24:TXM:IRQ_PIN_WAIT
09:47:05.979 -> 4984 RF24:RBR:REG=8,VAL=16
09:47:05.979 -> 4987 RF24:TXM:AIR=1220,EFF=4388,OBS=0,CNT= 50
09:47:05.979 -> 4992 RF24:WBR:REG=7,VAL=48
09:47:06.014 -> 4994 RF24:STL
09:47:06.014 -> 4996 RF24:WBR:REG=0,VAL=15
09:47:06.014 -> 4998 RF24:WBR:REG=10,VAL=6
09:47:06.014 -> 5000 TSF:MSG:SEND,6-6-0-0,s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=OK:2
09:47:06.014 -> 5007 RF24:RXM:LEN=8
09:47:06.014 -> 5009 RF24:WBR:REG=7,VAL=64
09:47:06.014 -> 5011 TSF:MSG:READ,0-0-6,s=255,c=3,t=27,pt=1,l=1,sg=0:1
09:47:06.014 -> 5016 MCO:PIM:NODE REG=1
09:47:06.014 -> 5018 MCO:BGN:STP
09:47:06.014 -> 5020 RF24:RBR:REG=6,VAL=37
09:47:06.014 -> 5022 RF24:RBR:REG=5,VAL=108
09:47:06.014 -> 5025 MCO:BGN:INIT OK,TSP=1

This is a Multi-relay sketch.
So it seems that (for me) the OP alterations makes https://github.com/mysensors/MySensors/issues/941 bug more patent. @Yveaux @alowhum

Sergio Rius

I've been having range issues so I gave this approach a try. I've been testing the @odritter solution along with the @tekka improvements and while the no interrupt code is totally operative, the proposed is not. At least on my network. I'll be reviewing it as I think it may be some bug on the coding.

That's:

	do {
#ifdef MY_RF24_IRQ_PIN
		RF24_DEBUG(PSTR("RF24:TXM:IRQ_PIN_WAIT\n"));
		RF24_status = hwDigitalRead(MY_RF24_IRQ_PIN);
	} while (RF24_status && timeout--);
        // timeout value after successful TX on 16Mhz AVR ~ 65500, i.e. msg is transmitted after ~36 loop cycles
        RF24_status = RF24_getStatus();
#else
		delayMicroseconds(MINIMAL_AIR_TIME_US + len * AIR_TIME_BYTE_US);
		RF24_status = RF24_getStatus();
	} while (!(RF24_status & (_BV(RF24_MAX_RT) | _BV(RF24_TX_DS))) && timeout--);
#endif

Sergio Rius

@yveaux said in MY_RF24_IRQ_PIN on ESP8266 GW:

True, and next it doesn't use it?

This could be reformulated as an affirmative sentence.
I cut the bridge wiring and continued working as nothing happened.

Sergio Rius

@mfalkvidd yes, I saw those posts. And there are changes in both the esp firmware and the Arduino core. I had to re-implement the ArduinoOta, for example. And it still doesn't work. But compiles.

@tekka said in MY_RF24_IRQ_PIN on ESP8266 GW:

@yveaux Defining MY_RF24_IRQ_PIN does not enable the RX queue feature per se. Therefore it compiles

That's the impression I had, that hadn't any effect. That was the reason I asked. Does actually have any functionality on esp?

Sergio Rius

So there's so limited functionality on esp. I think you can guess where I was going.

So I thought it could be some trouble because I saw some strange behavior, sometimes the start stuck, and keep flashing the led. I saw that d4 controls the inboard led, but as the gw worked after a reset and was so late I left for the day.
I may swap that pin, but I don't know what is available and it's internal number.

Sergio Rius

Hi guys, I just updated a gateway to the latest version and I also activated IRQ for the radio.
I wired the irq to the pin marked D4 on the NodeMcu v1 and set: #define MY_RF24_IRQ_PIN (2)
Due to the weird mapping on this board I don't know if its correctly wired. The gw seems to work.
Do you guys knows how to know if the feature is correctly working? Thanks.

Sergio Rius

This lost message is sent isolated, or it is a part of several ones sent at the same time?
I ask for this because if several messages are sent in a row this is is somewhat expected. You will find examples of "sleep between send"

What also does make sense to me is that if happens at nodes, also should happen at the gateway.
I've experienced nodes being dropped by the gateway when a section of the network powers up at the same time.

How do you control your messages? Do you use only domoticz or are monitoring with myscontroller? (Take care with domoticz)

Sergio Rius

I would check the radio modules. Did you source them from China? I had similar problems and they where caused by fake nrfs only aggravated by one repeater.
My modules only had range to next room, with luck. Some only had 3mt of range.
I think the repeater feature can only be used it you have very reliable radio modules, for the gateway and the repeater itself, and I would stay away from nrf24 for that.

Sergio Rius

@neverdie Does it have compression or checksum of the payload? I'm not used to that library, but it seems some processing is done. First try with plain repeating characters or numbers to discard encoding issues.

Sergio Rius

@neverdie On platformio, what do you use for programming? A black magic probe?

And about the 255 payload, have you looked for a wrong sized variable or type? If you want me to give it a go on visual studio+resharper just send me a sample. I still don't have a programmer and still haven't received my nrfs so I would only look for programming errors.

Sergio Rius

I was thinking more on a service that also could monitor temperatures and control power. But for being able to do that, it must be running while the computer is down. And also, should be impossible to use the existing networking. So a complete node would be preferred. I guess the nrf52 dongle could be a nice candidate for this. Inserted on an internal USB port and perhaps also connected to the MB switches and LEDs port.

Sergio Rius

I just had this idea where I thought about adapting the Linux GW code for acting as a computer service for sharing to the mysensors network the internal sensors and/or PW consumption or on/off/sleep features of a headless server.
What I don't like is the fact that as the coms would be easier through the existing lan, as opposed to implementing a radio, it would be in fact a new independent gateway.
What do you guys think about? Perhaps someone already thought about this.

Sergio Rius

Do you think this board could be used for a wifi gateway?
https://es.aliexpress.com/store/product/Nrf52840-development-board-ESP32-development-board-Mini/2956052_32921001572.html

Sergio Rius

@NeverDie Thanks for your time and good work!
I was thinking on start fiddling with the nrf52, but after the reading I don't know if I would handle it.

Sergio Rius

In fact, I had updates blocked using a group policy, and it worked for a while. But someday I noticed that the PC was turning itself on while I was not there. I thought it was the cat hitting the keyboard so I deactivated mouse and keyboard wake up and powering while off. But it didn't help. I also discarded wake on lan because the PC was doing it even without lan cable.
One day I saw that updates where happening and I realized that windows was turning the computer on for it. And then this message saying "we'll run updates when we find your computer is so behind on them" appeared below the one indicating that I blocked then by group policy, in updates screen. And last week, the computer was up to date.
So that's the way it is.

Even if you create firewall rules, I think they'll surpass them for their sake. I have opnsense as router/firewall, and I saw that now mistersoft uses thirty party cdns for their updates, so blocking them may be also a problem.

Sergio Rius

If anyone is interested, that was my channel scan when I decided to migrate to 108

Starting Poor Man's Wireless 2.4GHz Scanner ...

Channel Layout
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
|   +RRWRRWRWRWRWWWWWW+.                                                      ....                                             | 27
|   WWWWRWWWWRWRWWRWWW                                           ..      .........                                             | 26
|  .RWWWRWWWWWWRWRWWRW*                           .                      .......                                               | 26
|   +RRWWWRWWWWWWRWWWW*.                                                 .......                                               | 27
| ...RWRWRaRRWRWRRWRRRR..                                                      ...                                             | 29
|   aWWRWRWRRWRWRWWWWR-                                                 .....                                                  | 26
|   =WWWWWWRWWWWRWRWRWR                                                  ......                                                | 26
|   RWRWRWWWWRWRWWWWRW.                                                   . ......                                             | 27
|   *aRRRWRWRWRRWRWRWW-.                                                     ....                                              | 28
|...RWWRWRWRRWRWRWRRWRW..  .                                                 .....                                             | 29
|   WWRWRWWWWRWRWWRWRWW                                                 .........                                              | 26
|   WRWWWWRWRWWRWRWRRRa  .                                                   .....                                             | 27
|   RWRRWRWRWWWWRWWWWRW     .                                                .....                                             | 27
|   RWRWRWRRWRWRWRRWRWR.. .                                                      .                                             | 27
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
|...WRWWRWRWRWWRWRWRWRR...                                               .........                                             | 29
|   RWRRRRWRWRRWRWRWRWW                                                  ...                                                   | 27
|   WRWWRWRWRRRRWRWRRWR                                                  .......                                               | 28
|   RWWRWRWRRWRWRWRRWRW                                                  ..   ....                                             | 27
|   RRRWRWRRWRWRWRRWRWR                                                  .........                                             | 28
|...*aWaWRWWRWaWRWWRWaa.. .                                              ....                                                  | 31
|   aWRWRRRRWRWRRWRWRWa    ..                                           ..........                                             | 27
|   WRWRWWRWRWRRWRWRWRR                                                 ..........                                             | 27
|   RWRRRRWaWRRRaWaWRRR                                                   ...... .                                             | 28
|   WRWWRWRWWWWRWRWWRWR.                                                 ..   ....                                             | 27
|...RWRRWaWRWRRWRWWWWRW... ..                                           ....    ..                                             | 30
|   WRRRRWRWRRWRWRWWRWR                                                  .........                                             | 27
|   RWWRWRWRRWaWRWRRWRW                                                 .. ....                                                | 27
|   WWRWRWRRWRWRWRRRaWa                                                  .........                                             | 28
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
| ..RRWRWRRWRRaRaaWRRRR  .               .  .. .. .. ... ...   .  .  .. ... .. ...                                             | 29
| ..RRaRRWRRRaWRWRaRaWa..                  .  ..  .     . .      .  ..  ......... .                                            | 33
|   aRRRWRWRRWRWRWWRWRW   .                                              ..... ..                                              | 28
|  .RRaRaWaRRaWRWRRWRWR                                                        ...                                             | 28
|   RRWRWRWRaWRWRWWRWRW                                                     .....                                              | 27
|   WWRWRWRRRRWRWRRWRWR                                                 ...                                                    | 27
|   RRWRWRWRRWRWRRRaWRW                                                     ......                                             | 28
|   WRRWRWRWRRWRWRWWRWR                                                     ......                                             | 27
| . RRRaWaWRRRaWRWRRWRW                                                                                                        | 28
|   WWRWRWRWRRWRWRWWRW* ..                                                .......                                              | 27
|   RWRRWRWRRRRWRWRRRR- .                                                ..    ...                                             | 28
|   WRRWRWRWRRWRWRRRaR                                                      ......                                             | 28
|   +RRRWaWRRRRWRWRRRa- .     .                                          ........                                              | 28
|   +RWRRWRWRRWRWRWWaa.                                                  ..                                                    | 28
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
|   aaRaWRWRaWRWRWRRWRW.                                                 .... ....                                             | 28
|   aRRWaWRWRRWaWRWWRWa ..                                              .       ..                                             | 29
|  .RWRRWRWRWRRWRWRWWRW  ..                                             .......                                                | 26
|  .WRWRRWRWRWRRWRWRRWaa  .                                                 ...                                                | 28
|   aWRWRRWRWRWRRWaWRRRa                                                .     ....                                             | 28
|   RRWaWRRRRWRWRRWRWRRW                                                     .....                                             | 28
|   RRaWRWRaRaWRWRRWRWRW   .                                                ......                                             | 28
|   RWWRWRWRRWRWRWRRWRWR.                                                       ..                                             | 27
|  .WRWRRWRWRRWRWRWaaWaW...   ..                                            .. ...                                             | 28
| ..RWRWRRWRWRWRRWRWRRWR   .  .                                         .....                                                  | 28
|   RaWaWRaWRWRWRRWaWRR*.                                                     .....                                            | 29
|   RRRWRWaaRaWRWRRWRWRa      .  .                                       .........                                             | 28
|   RRWRWRWRRRaWRRRaWRW.                                                    ......                                             | 27
|.. WRRWRWRWRaWaWRRRaWa.                                                                                                       | 28
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
|   RRWRWRWWRWRWRRWRWR .                                                     ....                                              | 27
|   RWRWRWRRRaWRRRaRaW.                                                 .......                                                | 28
|   aRRRWRWRRWRWRWWRWRa..                                                .......                                               | 28
|   aaaRaWRRRRWRWWWWaW=.                    ..                          ......  ..                                             | 29
|   aWWRWRWRRRaWRWRRWa=.                         .                      ..                                                     | 30
|   WRWWRWRWRRRaWRWRRWR    .                                            ... .. ...                                             | 27
|   RWWRWRWRWRaRaWRRRaR .                .      . .                     ....                                                   | 28
|   WRWRRWRWRWWRWRWRRRa                     .                           ......                                                 | 29
|   aWaRRaRRWRRRRWRWRRW  .                                               ..                                                    | 28
|   WRWRRRaRaWRRWRWRWRR                                                 .........                                              | 28
|   RWRWRRRRWaWRRWRWRWR    .                                              . .....                                              | 27
|   WRWRWRRWRWRRRaWRWRR .                                                .........                                             | 28
|   RWRWRWWRWRWRRRRWaWR     .                                                ....                                              | 28
|   RRWRWRRWRWRWWRWRWR+                                                     ......                                             | 27
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
|   *WRWRRWaWRWRRWRRRR+.   .                                                .......                                            | 29
|  .aaRaRaRRRWaWWaWWWaW. .               . ...  .  .  .. .. ..  . .  ..  ..  . ...                                             | 31
| . WRRRaWaRaaWRWaWRaWR  .                 .   .  .  .. .. .  .. ..  .  ..  . ....                                             | 30
|   RWRRWRWRWRRWRWRRWRW  ..                                                    ...                                             | 26
|   WRRWRWRWRRRaWRRRaWa.                                                     .....                                             | 29
|  .aWRRWRWRWRRWRWRWWRW+                 .. .                                 ..                                               | 27
|  .*aa*a*a**a*a*aaaaaaa      . ...........::-++WWWWRaa=:.               .. ....   ...... ... .......                          | 37
|. .*a*aa*a*aaaaaRaaa*Ra    ..............:-*RWWR*=:..                           ..    .........:-:::..                        | 33
|  .RWRWWRWRRRRRRWRWWRWR .  ..............::-+aRWW*+--::.                    ... .        ...........                          | 27
|  .WRWRWRaRaWRRaaRaRaRR                                                                                                       | 29
|  -RWRWRWWRWRWRRWRWRWRR                                                  . ...                                                | 27
|  -RWWWWRWRWWWWWWRWWRWW.......:.::........-++a+=-:....                     ......   ..... ..::=*+-.                           | 27
|  :****a*a*a*aa*aaaa*Ra   ..............::=+aRWWa*=:...                     ..    .... .......                                | 35
|  :RWRWWRWRWRWWRWRWRRWR..... .......:....::--:=----::...     .  ...........::::-..:....::.                                    | 27
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
| .-WaWRWRaWRWRWWaWRWRRW     .                                              ....                                               | 28
|  -WWRWRWRRWRWRRWRWRWRR                                                                                                       | 27
|   RRWRWRRWRWRWWRWRWRR.                                                    .....                                              | 27
| ..RRaWRWRRWRWWWWRWRWR-.                                                   ...                                                | 30
|  .aaWaWRRRRWRWWWWRWRW-...                                                                                                    | 30
|   RRaRaRaRRaWaRRRRRWRa                                                  ......                                               | 29
| ..*WWRWRWRRWRWRWWRWRW.                                                        .                                              | 27
|  .=RRWaWRRRaWaRRRRRWa                                                       ..                                               | 28
|   -RWRWRWRRWRWRRRaWRR                                                    ....                                                | 28
|   aRaRaWaaRaWRWRaWRWR.. .............    .                              . ....                                               | 29
|   RaRaWRRRaWRWRRWRWRW:            .             ..                          ..                                               | 28
|   aWRWRWRRRRWRWRRWRWW+..     .                                          .....                                                | 27
| . aWWRWRWWRWRWRRRRWRW-                                  .                ......                                              | 27
|   RRRWRWRWWRWRWRRRaWa=                                                   .    .                                              | 28
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
|   =RWRWRWWRWRWRRRRWRR:...                                               . ...                                                | 28
|   RRRWRWWRWRWRWRRWaWR-                      .                           ......                                               | 28
|   aRRRWRWRRWRWRWWRWRW   .                 .                             . .                                                  | 27
|   aRaRaWRRRaWRWRRWRWR.                                                    .....                                              | 28
|   *WWRWRWRRWRWRWWRWRW.       .                                                                                               | 26
|  .*RRWRWWRRRWRWRRWaWR*.        .                                          .                                                  | 28
|   =WWRWRWRWWRWRWRRWRW.       ..                                                                                              | 27
|  .*aaRaWaRRaRaWRRRRWR..                                                 .....                                                | 29
|  .aWRRRaWRWRRWRWRWWRWR      .                                                                                                | 28
|  .aRWWRWRWRWRRWRWRRWa=                                                  . ....                                               | 27
|  .-RRWWRWRWWWWRWRWR==:                                                                                                       | 27
|  .RaWRRRaWRWRaRaWRRR*-                                                  ....                                                 | 29
|   RWRWRRWRWWWWRWRWWWW:                                                    ....                                               | 27
|  :RaRaWRaWaWRRRaWRWRRa                                                    .....                                              | 28
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
|..RaWRWRRRaWRRRaWaWRRRa                                                   ....                                                | 29
| .aRRWaWRWRRWaWRRRRWRWa..      .                                               .                                              | 27
| ..WRRRaWRWRaRaRaRRaRaW .  .            .  .  .. .. ..  . .  ..  .  .  ..  .....  .                                           | 29
| .:aWRWRaRRWRWaaWRRRRRR.  .               .  .. .. .. .. .. ..  :  .. .. ..  ..  .                                            | 30
|  +RaWRWRWRRWRWRRWRWRWR                          ..                      ......                                               | 28
| ..WRRWaWRWRRWRWRWWRWRW                                                    .....                                              | 28
|  .RWRRRRWRWRRWRWRWWRWa         .                                              .                                              | 27
|  .WRWRWRRWRWRRWRWWWRR+        .   .             ..                     .. .                                                  | 27
|  -aWRWRWRaWRWRRRRWRRa+                                                  .....                                                | 28
|  -RRWRWRWWRWRWRWRRWaWR                                                 ..                                                    | 28
|..-WRWWRWRWRRRRWRWRRWRR                                                  ....                                                 | 28
|  -RWRWRaWRWRWRRWRWRWWR                                                  .     .                                              | 27
|  =RRWRWRRRRWRWRRRRWRWR                                                  ....                                                 | 27
|  -WRRWRWRRRRWRWRaWaWRR                              .                  ... .....                                             | 28
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
|  :RRWRWRWRaRaWRWRRWRWR                                                 ........                                              | 28
|. .WRRWRWRWRRWRWRWRaWaW                                                 ......                                                | 28
|  -RWRWWRWRWRWWRWRWRaWa.                                                ........                                              | 28
|  .RaWaWRaRaWRWRRWRWRRR.                                              .........                                               | 28
| .:WRaWaWRRRaWRWRRWRWRW   ..                                        .                                                         | 28
|  -RWRRWRWRRRRWRWRRWRWR                                          .     . .......                                              | 27
|...WRWRRWRWRWaaWaRaRRaR..                                               ..                                                    | 31
|  :aWRWRWRRWRWRRRRWRWRa                               .                       ..                                              | 28
|  :aaRaWaWRaWRWRWRRWRWR. .                     . .                       . ..... .                                            | 29
| .:WaWRaRaRaWRRWRWRRWRW   ..                                                   ...                                            | 28
| ..RWRWRRWRWRWRaWRWRWR=   ..                                                   ..                                             | 27
|...WRWRWRWRaWaRaaRaRaR    ..   ...                                            ....                                            | 30
|  :WRRWRWRWRRWaWRRRaWa:  ...                                              ........                                            | 28
| .:RWRRRRWRWRRWRWRWRRWa. ..                                                ......                                             | 28
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
| ..WRWRRRRWRWRRWaWRRRa*  ...                   ..  .                       .......                                            | 28
|   RWRWRRRRWRWWRWRWRWW:  .               ..      ...                       ......                                             | 27
|  -RaWaWWRRRWRWRRWRWRWR  ...                                             ......                                               | 30
|  =WWRWRWRWRRWaWRRRRWRW  ...                                                   ...                                            | 27
|   -*RRWRWRWWRWRWRRRa=.                                                    .......                                            | 27
|  .RRWRRWRWRWWRWRWRRWa-  ...                                               ...                                                | 28
|  .aRaWRaWaWRRRRWRWRRR*  ...                                             .  ....                                              | 29
|..*RRWRWaaRRWRWRaWRWRWR  ...                                            ..       .                                            | 28
|  aWRRWRWRWRaWRWRRWRWRW   ..                                             .      ..                                            | 27
|..=aWWRaaRRWWWWRWRWWRWa......                                .....  ..  . ............. .                                     | 32
|   aaWRWRWRaWRWRRRaWaR.  ...                                             .........                                            | 29
|  .aRaRaWRRRRWRWRRWRWR-  ...                                               .... ..                                            | 28
|...RWaRRRWRWRRWRWRWRaW=  .. .                                            . ... ...                                            | 30
|   WaWRRRaWaWRRRaWRWRR=  ...                                             ..     ..                                            | 28
|0         1         2         3         4         5         6         7         8         9         10        11        12    |
|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
|  :aWRWRaWaRRWRRWRWRWW*   .                                    ..    .. ..                                                    | 28
|  :WRWRWWRRaWRWRRWRWRWW                                                       ..                                              | 27
|  *WRRWRWRWRRWRWRRWRWRR                                                                                                       | 28
| .+aWaRRRWRWaaWaWRWRaR*.  .            .  .   .  .  .     .  .  .. .. .. ...  .                                               | 31
|. -*a**R*Ra*RRWRWRaWaR*....... ....       .  .  .  .. .. .. .. .. .. ..........  .                                            | 36
|  -*RaWRRaaWRWRRRaWRWWR....:...:::.:::-::::::.:::...::::::.::::::...............   ......  .......... ........ ...... .    . .| 30
|. =aWRRRRWRWRRWRWRRRWWR... .::..:.............            . ......        .........                                           | 30
|..-aRWRWaWRRWRWRRRRWaWW..  .                                                 ...                                              | 33
|..:aRWWWWWRRWWWRRWRWRRa.....:.::....:::...::::..::::::...:::..............                                                    | 34
| ..RWWWWRWRWRRWRWWWWRWa.......................                .. ... ..     ...         .....                                 | 29
|...RaWRWWWRRWRWRRWaWRW+... ............  ... ..    ....            ..      ...                                                | 31
|.. WRWRaWRWRRWRWRWRRWR.                                                     ....                                              | 28
| ..RRRWWWWWWWWRWRWWWWR....::::...:----:...::::................ ....... ........                                               | 30
| ..RWRWRRRaWaWRRRaWaRR.  .                                               ......                                               | 28
|0         1         2         3         4         5         6         7         8         9         10        11        12    |

And that's the worse I get today:

|012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345|
|                             .  aRaRRRWRWaa ..                                                                                | 28
|                               .RRaRWWWWRRR                                                                                   | 26
|                                WRWWWWWRWWW   .                                                                               | 25
|                                RRWWWWRRRWR                                                                                   | 24
|                                :WWWWRRRWWW                                                                                   | 25
|                             ....WWWRWRRWWa .                                                                                 | 25
|                                :WWWWRWWWW-                                                                                   | 27
|                                +WWWRWWWWWR                                                                                   | 25
|                                WWRRRWWWWRR  .                                                           ..                   | 25
|                            ....aWRWRWRRRRR....                                                                               | 26
|                            ..:.RWRRWWWWRRW.:..                                                                               | 30
|   ...     . ...   .....    :...+WRRRRaRWWW....     ...     ..   ..   ..   ..                                                 | 29
|                            :...WWWWRaaRRaW-:..     ..                                                                        | 32
|                                RWWRRRRRWWR                                                                                   | 27

I'm using a new device so still I may have something to adjust in the scanner as I don't get the band being so clean. I've changed the old wifi AP for an ubiquity thou.

Sergio Rius

@gerard-van-seventer Thanks Gerard for the hint on version. I wonder how you manually choose betwenn drives in windows. I guess you simply uninstall the existing when the device is present and then install the wanted one?

Sergio Rius

@yveaux Thanks! Good point. I'll first give another go to the scanner and try with a lower channel.

Sergio Rius

I'm trying to improve my nrf24 network range, that currently is worse than shit (in good manners) and I'm having really strange issues that I think could not be related to radio power.
For testing I have an esp8266 gateway (pa+lna,isolated+dedicated power), a custom power meter on steroids (regular nrf, good dedicated power) that has been connected for months and then one board that I wanted to use for a met station (regular nrf & phone batt powered, design from oh.io).
I'm using the 108 channel to avoid interference from some time ago and before I could not make work anything.
The power node is at clear sight at, say 7 meters. Gw at the ceiling of a "balcony" second floor, PwMeter in a wall at the lower floor. was working with no problems.
The met station I can't separate to a meter from the gw that it doesn't sync. I tried swapping radios, isolation and antenna mods without success. Other nodes seemed to have similar problems. Even my garage door controller that runs a good power source and pa+lna It can't communicate only through a floor.
That's one problem.

So I thought of using a mysRGBW node as a repeater for the met station and I put it on the next room. Then the met.station linked, but the power meter not. So I powered all down and removed the new aggregations and left gw+power.meter. Now it seems like pm tries to register to the network, but the gw it's loosing messages. Looses half of the presentation and then the node halts. When it succeeds, it regularly misses some SET messages. I realized that it survives the presentation when domoticz is not started and those hearbeat messages are not around.
What those things can be caused?

Sergio Rius

Yes, I think it must be a windows native driver that tried to self install, something "Prolific..." alike. But when I came to the updates history, it showed as a fail.
I could try with my wifes laptop, but it's also win10.
I'll have to bring a fresh windows 7 in an htpc board I have around.

Do anyone knows what's the latest working version of the brand drivers, and perhaps have a copy to send me?

Sergio Rius

@bjacobse My system gets all the updates. That means at least one major every month. So identifying the culprit or going back can be impossible, as I wasn't using those devices for a while. Sure that's the problem.

Althought I've been raising a new ubuntu VM in my esxi server in the hope I could configure it for mysensors developments, but I stepped into so many problems that I'm now turning it of definitely.
First ubuntu (18.04) desktop didn't resolve names in my intranet. I had to ditch it's fancy networking interface and go back to the old school /etc/network/interfaces file.
Then I had problems mounting samba shares and had to do it with nfs. And when I tried to open my shared sketches folder with the Arduino IDE I realized that it can't browse network mounts even when I have full access to them.
Also I passed through the servers usb controller to the VM and tried to get the ftdi device shown in ubuntu, but the passthrough doesn't work on any usb controller.

I feel like I've been cursed.

Sergio Rius

Today I realized that none, absolutely none of my usb to serial converters works. I've been using them in the past, but lately I was uploading sketches through ISP and I didn't need anything to debug.
Seems that my Windows 10 throws a different error for every one like "the device did not turn on" or "error 43, requesting device descriptor"
Is this happening only me or is anyone having such problems?
I read something about original brands distributing malicious drivers and wrecking supposedly fake chips, but I didn't even update any driver.
What you guys are using for serial debugging?

Sergio Rius

@MrRobots that was exactly my first problem, and never find the cause. Just switched to an esp gateway with a good power source.

Then the second issue seems like the gw "banning" the network or a part of it after receiving something it wasn't prepared to. Just my speculation.
Does that last one seems like anything you have?

Sergio Rius

I recommend that you build a WiFi or Ethernet gateway and you will discard several causes in one shot. I had the same problems with the RPI gw and that helped a lot.
Could be problems with the gw service, wiring, but also the RPI2 power limit reached on the USB lane, the power supply not being enough specially if you added WiFi to the RPI, or the system being resource hungry at some moment.

Also for diagnosing I would stop some nodes and try. After solving the first point I had this problem. It happen to be a far node sending something weird to the gw due to the long distance.
You can stop the farther nodes or the ones of one kind. You could end with a working system excluding only one node, like in my case.

Sergio Rius

@alexsh1 Truly, but that's what it's meant to be.

Sergio Rius

@gohan +1 to that.

My father was electrician and tought me something. I'm programmer and I also do lots of database and network design and management... And I can assure you that combining skills needed for today's ha development is not trivial.

It's because microcontrollers language and flashing methods. If powerful and efficient ones that could run any Java or lua like language, loaded through simple Bluetooth were developed, the situation would radically change.

Sergio Rius

@gohan Yeah, but what is not that intiutive for me is why when load increases in the mosfets side, the ams regulator goes away.

Anyways, no one knows what max led strip length is this board good for?

Sergio Rius

@gohan As you suspected, it was 12v.

Sergio Rius

Mmmmm... How much have you pushed this board? I mean, in terms of load.
I just had one fail at me and I'm trying to understand what component may have been the weak link.

It was driving a 5m white stripe when it turned himself off and on again, but although the light was still on the node was down. I took it out and almost burned my hand. Not the mosfets, but the arduino and radio. Nothing seems bad (components good looking, arduino seems to start) but as soon as you apply 12v, even without load it starts the barbecue.

It seems that the mosfets are good to 4,2Ah if I understand it. So what would be the boards specs?

Sergio Rius

@mfalkvidd Look in the ide for language inspection errors.
Sometimes while crawling the sources vs decides you have some invalid code files or dependencies, then it changes the file types to avoid live dependency resolution loop.
Then you loose auto completion, error detection, navigation, etc.
Specially if you use resharper plug-in.

Libraries like mysensors confuses the ide.

Sergio Rius

@gohan +1 on vs+vsmicro.
I'm a be developer from is first version and I could only seriously start programming in Arduino when I found the plug-in.

Last week, also stumped into other free ide that reuses the vs distributable, while trying to get mysbootloader to compile. It seems a nice stand alone solution. I can't remember is name but I think visual micro comes from it.

Sergio Rius

@rejoe2 No, I didn't see this. Been out more than a year by an accident and I'm still getting used to all the changes.
Thanks!

Sergio Rius

@neverdie If you are referring to me, no. I'm not complaining. Just wanting to contribute but I'm to slow to take the train in time. Sorry if seemed anything else.

Sergio Rius

Of course, projects are always difficult to manage and often they must be completely flipped like an omelet.
But what seems recurrent is that only a small group of people knows whats the next step in development. So someone starts doing anything and by the time he wants to pr discovers that the sources had changed path and what he has done, now doesn't make sense. Or simply, opinions and ideas are ignored as they happen to be incompatible or undesirable for the (secret) idea of the project.
I think is something inherent with open source projects. But sometimes is discouraging.
I think it may be solutions for publishing wanted changes and preventing people annoying developers.
I would like a future where desired functionalities would be published in a list and anyone could sign for doing them.

Sorry if words look rough, I assure is not intended, I still have problems with the english.

Sergio Rius

@scalz said in Fewer home automation postings? What's behind it?:

I can't tell you more

Yes, that's what I was referring to. But anyways, I should be ignored again.

Edit: definitely should.

Sergio Rius

In my opinion, and a way to leave this topic, I find the project is a bit uncoordinated. (There are some brilliant people there. That's out question)

I mean, we have the mysensors library, that needs slight configuration when used in nodes. But definitely one must set some things, as channel. (Other things are part of the hardware)
Then is signing and encryption. And it's understanding and use is not trivial.
Then nodemanager and mysbootloader.
Every "module" by its own.

The bootloader has the ability to rewrite the program in the node. It could be feasible to parametrize security and operation settings (in EEPROM?) and the bootloader set them initially only requiring radio settings being hard coded.
And those ones could be added as parameters to bootloader compilation.

That should make something more useable. But someone must have already thought about it. I'm not that clever.

I've already started some interesting things myself, but always abandon them by fear of project changing paths , little time to invest at the right moment, or simply not being a popular contributor.

I'm a .net programmer and been waiting the opportunity to do something for emby in this platform. If someone know about the recent "changes" in that project, will understand my sadness. So when I saw a not so friendly project I start to fear.

Sergio Rius

@gohan What do you mean? The rPi or the Esp?
For the rPi I first used a NRF24 pa lna getting power from the 5v line with a voltage regulator (ams1117 based)
Then I thought could be problems with this radio or supply and ditched it for a normal NRF24. With identical behavior. Sometimes works for a week or a couple of them or I have to restart the whole Pi several times a day only for being able to go out of home.
When I first implemented the rPiGw worked for weeks. Then the problem appeared. then vanished and was working for months until some point that became worse.
I even thought that my wifi hotspot could be dying and changed it for a unify-pro (nice gadget)
I live in a house far from others, so wifi interference seems not an issue.

I run the Pi from a readonly sd for boot partition and then uses an usb drive for the system+controller. logs on tmpfs.

I was fastly implementing it in my home, but as this problems arose, I only have the power monitor node, the garaje door node and a doorbell that is offline because suspiciously started to eat batteries two months ago.

I'm in Domoticz beta.

For the esp gw it's just a nodemcu board on a breadboard paired to a normal nrf24.

Edit: Ups! mysensors versions are all 2.2.0. The arduinos are all 3v3 8mhz boards and one 5v (power)

Sergio Rius

About the issue of my gateway I talked before. I found that the problem must be induced by domoticz.
As I was tired of reseting the GW during those tests (and not being able to open my door garaje), I built a new esp gateway. I ran a 2.4Ghz scanner that covers all the channels and decided for a clean 100+ channel.
The gateway passed the tests and I connected it to domoticz.
I re-configured two nodes for working with it, but they weren't registering. I then realized that my rPi gw was in it's "halt" status... but also the wifi one.
So I've restarted Domoticz and bingo, the nodes started registering on the wifi gw.
Seems that my Domoticz installation may be sending something that makes gw freeze. I thought that could be my mains consumption counter as it was a big number, but I resetted to zero two days ago for this sake.
If devels want to make me dump logs or anything I'll be putting my installation on quarantine.

It's halted again. When that occurs this is the only registered on MYSC:

Sergio Rius

Playing with another node I realized that burning bl+sketch through avrdude gives a node with MYSBL that boots asking for sketch but immediately goes on with the sketch. So far is a good solution.

The firsts still uploading the 30B sketch
Are you sure that it's normal?

Edit: It has been uploading (i think several times) for the last 50mins and now is stuck in "Booting: 50.1 (BL1.3)"

Sergio Rius

@tekka I have some news.
After burning this version, the board doesn't accept loading a sketch through FTDI.

Sketch uses 7666 bytes (24%) of program storage space. Maximum is 30720 bytes.
Global variables use 348 bytes (16%) of dynamic memory, leaving 1700 bytes for local variables. Maximum is 2048 bytes.
C:\Users\sergio\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/bin/avrdude -CC:\Users\sergio\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/etc/avrdude.conf -v -patmega328p -carduino -PCOM8 -b57600 -D -Uflash:w:C:\Users\sergio\AppData\Local\Temp\arduino_build_767496/DimmableLEDActuator.ino.hex:i 

avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2014 Joerg Wunsch

         System wide configuration file is "C:\Users\sergio\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/etc/avrdude.conf"

         Using Port                    : COM8
         Using Programmer              : arduino
         Overriding Baud Rate          : 57600
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0xaf
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0xaf
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0xaf
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0xaf
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0xaf
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0xaf
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0xaf
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0xaf
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0xaf
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0xaf

avrdude done.  Thank you.

Problem uploading to board.  See http://www.arduino.cc/en/Guide/Troubleshooting#upload for suggestions.

But it shows a new "Booting" node in MYSController and seems FW can be uploaded, but at an absord slow speed.

May this speed be a problem of mine with the rPI gateway. The part of the service that handles radio hangs in periodically and I have to SSH into the rPi and restart the service. During this, MYSC talks with the service but nothing is sent or received.

10 minutes already passed and it's still writing the 30B sketch.

Sergio Rius

Just a flash question, I suppose I must clone the 8Mhz RC settings for fuses... but even being a pro mini board with an external xtal?

Sergio Rius

@tekka WOOOOOOWWWW! THANNKYUUU!!!!

Sergio Rius

@tekka I'm using the RGBW Controller by LastSamurai, and it rearranges the pins. So I can't change anything there.
Yes, I'm already on that page comparing the two settings and the size was the only one thing left to discover. Thank you.

I suppose I'll have to drop mysbootloader for all those nodes

Sergio Rius

@tekka
My pin settings for the radio are:

#define MY_RF24_CE_PIN 4 //<-- NOTE!!! changed, the default is 9
#define MY_RF24_CS_PIN 10 // default is 10

What should I change in BL code for making it to work?

Fuses yes, I also have them wrong. I read them from a brand new board and they are

  Low Fuse      0xFF
  High Fuse     0xDA
  Extended Fuse 0×05
  LB            0x3F

And mines are:

  Low Fuse      0xE2
  High Fuse     0xD2
  Extended Fuse 0×06
  LB            0x0F

What I'm trying to learn is whay mysbl ones are also different from the stock ones.

Sergio Rius

@tekka But it's mandatory, like this for the FOTA to work?

Well, obviously yes, if it's incorporated to the code. So I suppose that I would have to compile my own version.
It's there any description for the fuses being different than the stock ones?

Sergio Rius

I would like to say yes, as I'm currently programming a 3v3 Arduino pro mini board like this. But I'm having some problems.
I would like someone to give me a hand on this.
I'm trying to get a rgbwdimmer programmed with the MysBootloader and the operating sketch. But I can only do one or another. If I burn the bootloader first, the board seems to do nothing on start. Even it doesn't react to reset. And I can't load a sketch.
Then I have to burn back the Pro Mini 3v3 8Mhz bootloader with the IDE and then accepts the sketch and works. If I burn back the mysbootloader, goes back to the previous situation.
I'm using the IDE and avrdudess with Arduino as ISP and for loading the sketch a simple USB to TTL.

Also, should be possible to load the compiled sketch+bootloader through avrdude, but when I do, the board also freezes on power.

Can anyone tell me what I'm misunderstanding?
@tekka Does the mysbootloader relies on the standard pinout for the nrf?