Thanks electrik, for the tip. It is indeed the MQTT gateway causing the issues. I unplugged and removed the gateway and all is well now. Disabling doesn't work. It must be disconnected. I'm not sure why. I'm using the canned mQTT gateway app from the site. Something is obviously dorked with it.
Thanks again
Dan

Posts made by dpcons
-
RE: 2.4G Gateway Posts "Unknown" nodes
-
RE: 2.4G Gateway Posts "Unknown" nodes
Do all your gateways use separate channels and/or base radio id?
All my gateways are basically 'canned code' which I downloaded from the MySensors site. I haven't made any changes to the code. Do I need to?
Everything has been running just great for about 10 months or more.
I just started seeing these anomalies lately.Can you see any patterns in which node ids are unknown?
I see no patterns that I would recognize. Node IDs generally seen to increment, but by random amounts, but some IDs seem to be 200 or higher.Have you reflashed any of your gateways lately?
No...I added a larger 22uF cap to the power/ground on the 2.4G radio after this started happening, but it had no improvement.Are there any other messages in the log that can give a clue to what is happening?
I've sent three images. One of the Hardware/2.4G setup, One of the error list and one of a child node with an unknown temp and humidity node that shouldn't be there. I get about 10-15 Unknowns appearing every day. I just delete them and move on.Could someone else have deployed a MySensors network near you?
I'd say that's pretty unlikely but I could put out a notice on our Home owners association website.The system seems to be running normally except for this issue. If I need to make changes regarding the channels, base radio, etc. I'll certainly do it.
Thanks for the response...I appreciate it
-
2.4G Gateway Posts "Unknown" nodes
Hi All,
I'm using three gateways with various sensors connected to my RPI Domoticz Controller. Recently my 2.4G ESP8266 WiFi gateway has been logging an increasing number of "Unknown" nodes. It's also showing an annoyingly large number of "Unknown" nodes for the child sensors also. Maybe it's a Domoticz issue, but the other gateways are fine, nothing weird. It's been operating for many months till lately. Any ideas?
Thanks - Dan -
RE: Pro Mini issues
This problem has been resolved. It appears my ANKER 10 port USB Hub is the problem. It's associated with the lower 4 ports of the hub. The remaining 6 are OK. I'm not sure what the actual problem is yet. The hub has a 60W power supply attached so I doubt it's a power issue...maybe noise? I now have a 10 port Amazon Hub which works well. As for the DTR signal, I've always used it and have seldom used the reset buttons. Also, I think most of the Arduinos and clones have it implemented through the serial convertor chip as well. It's also on all the ESP32 and ESP 8266 clones I've used. Again, thanks everyone for your comments and suggestions.
-
RE: Pro Mini issues
Hey Guys,
Thanks for the response. I've uploaded a jpg to show the connections. Yes, it's a 3V device. Before I use the minis I put 5V on RAW and check VCC. I've also selected the correct 328 configuration in the Arduino IDE. I've checked DTR with a scope and it's working fine, but I've held the reset button before programming, just to be safe. I've also used different Hub ports and cables as well as different FTDI programmers and Pro Mini boards. I even went back to the old version of the Arduino AVR Library. That's the reason for the posting. I've just started using the mysensors library, so I wasn't sure if all the examples worked on all devices and I didn't want to dig in the code. If you're telling me the Mini works with this code, then I can continue to look into other areas. Again, thanks to all! I appreciate your interest.
Dan
-
Pro Mini issues
Hi All.
I'm using a 3V Pro Mini and having issues loading the BinarySwitchSleepSensor2 app straight from web site. Sketch fails after a few seconds of loading.Details:
Sketch uses 12768 bytes (41%) of program storage space. Maximum is 30720 bytes.
Global variables use 446 bytes (21%) of dynamic memory, leaving 1602 bytes for local variables. Maximum is 2048 bytes.
avrdude: verification error, first mismatch at byte 0x1c55
0x7f != 0x5f
avrdude: verification error; content mismatch
avrdude: verification error; content mismatchThe Pro Mini loads and runs Blink app and others but fails with this. The nRF24L01 radio is hooked up as shown in Guide, although this doesn't matter. Won't load without the radio attached either.
The app loads and runs just fine on the ESP8266. Has anyone else had issues with the pro mini?
Thanks,
Dan