Same issue here. HA receives data from Ethernet Gateway for only a few minutes and then:
DEBUG (MainThread) [mysensors.gateway_tcp] Connection lost with <_SelectorSocketTransport closing fd=42 read=idle write=<idle, bufsize=0>>
I also have MYSController connected to the GW and it remains connected. There is an open issue as others are also having the same problem. Am wondering if anyone here is having success with Ethernet Gateway connected to HA.
@mfalkvidd Thanks for the prompt reply and your persistent monitoring of the forums. Correct- I didn't even realize there were compatibility issues until I myself fell into this hole. Thanks for pointing it out.
After I posted, I tried to get a ESP32-based gateway going and ran into the same compile error. Then, I also tried uploading a blink sketch and that too yielded a compile error. This prompted me to update my Arduino IDE to v1.8.19 (from 1.8.13) but that didn't help. So in this case, it's not a MySensors issue, but an issue with ESP32 boards in general (at least on my machine). It sucks that advanced boards have become beyond the reach of hobbyists like me...
Was trying to get a ESP8266-based Gateway working and kept getting a "exit status 1" error that then said "Error compiling for board xxx" where xxx is any ESP8266 board. Once I downgraded esp8266 boards file to version 3.0.2, the compile error was gone, and everything worked fine.
The only clue as to what's wrong with newer versions is this text from the compile window (except for first and last line, everything was in orange text):
"C:\\Users\\Doug\\AppData\\Local\\Arduino15\\packages\\esp8266\\tools\\xtensa-lx106-elf-gcc\\3.1.0-gcc10.3-e5f9fec/bin/xtensa-lx106-elf-g++" -D__ets__ -DICACHE_FLASH -U__STRICT_ANSI__ -D_GNU_SOURCE -DESP8266 "@C:\\Users\\Doug\\AppData\\Local\\Temp\\arduino_build_788282/core/build.opt" "-IC:\\Users\\Doug\\AppData\\Local\\Arduino15\\packages\\esp8266\\hardware\\esp8266\\3.1.0/tools/sdk/include" "-IC:\\Users\\Doug\\AppData\\Local\\Arduino15\\packages\\esp8266\\hardware\\esp8266\\3.1.0/tools/sdk/lwip2/include" "-IC:\\Users\\Doug\\AppData\\Local\\Arduino15\\packages\\esp8266\\hardware\\esp8266\\3.1.0/tools/sdk/libc/xtensa-lx106-elf/include" "-IC:\\Users\\Doug\\AppData\\Local\\Temp\\arduino_build_788282/core" -c "@C:\\Users\\Doug\\AppData\\Local\\Arduino15\\packages\\esp8266\\hardware\\esp8266\\3.1.0/tools/warnings/extra-g++" -Os -g -free -fipa-pta -Werror=return-type -mlongcalls -mtext-section-literals -fno-rtti -falign-functions=4 -std=gnu++17 -MMD -ffunction-sections -fdata-sections -fno-exceptions -DMMU_IRAM_SIZE=0x8000 -DMMU_ICACHE_SIZE=0x8000 -DNONOSDK22x_190703=1 -DF_CPU=80000000L -DLWIP_OPEN_SRC -DTCP_MSS=536 -DLWIP_FEATURES=1 -DLWIP_IPV6=0 -DARDUINO=10813 -DARDUINO_ESP8266_WEMOS_D1MINI -DARDUINO_ARCH_ESP8266 "-DARDUINO_BOARD=\"ESP8266_WEMOS_D1MINI\"" "-DARDUINO_BOARD_ID=\"d1_mini\"" -DFLASHMODE_DIO "-IC:\\Users\\Doug\\AppData\\Local\\Arduino15\\packages\\esp8266\\hardware\\esp8266\\3.1.0\\cores\\esp8266" "-IC:\\Users\\Doug\\AppData\\Local\\Arduino15\\packages\\esp8266\\hardware\\esp8266\\3.1.0\\variants\\d1_mini" "-IC:\\Users\\Doug\\Documents\\Arduino\\libraries\\MySensors" "-IC:\\Users\\Doug\\AppData\\Local\\Arduino15\\packages\\esp8266\\hardware\\esp8266\\3.1.0\\libraries\\SPI" "-IC:\\Users\\Doug\\AppData\\Local\\Arduino15\\packages\\esp8266\\hardware\\esp8266\\3.1.0\\libraries\\ESP8266WiFi\\src" "-IC:\\Users\\Doug\\AppData\\Local\\Arduino15\\packages\\esp8266\\hardware\\esp8266\\3.1.0\\libraries\\EEPROM" "C:\\Users\\Doug\\AppData\\Local\\Temp\\arduino_build_788282\\sketch\\LoRa_GatewayESP8266OTA_RFM95_v1.ino.cpp" -o "C:\\Users\\Doug\\AppData\\Local\\Temp\\arduino_build_788282\\sketch\\LoRa_GatewayESP8266OTA_RFM95_v1.ino.cpp.o"
In file included from C:\Users\Doug\Documents\Arduino\libraries\MySensors/MySensors.h:235,
from C:\Users\Doug\Documents\Arduino\LoRa_GatewayESP8266OTA_RFM95_v1\LoRa_GatewayESP8266OTA_RFM95_v1.ino:174:
C:\Users\Doug\Documents\Arduino\libraries\MySensors/core/MyGatewayTransportEthernet.cpp: In function 'bool gatewayTransportAvailable()':
C:\Users\Doug\Documents\Arduino\libraries\MySensors/core/MyGatewayTransportEthernet.cpp:430:44: warning: 'WiFiClient WiFiServer::available(uint8_t*)' is deprecated: Renamed to accept(). [-Wdeprecated-declarations]
430 | clients[i] = _ethernetServer.available();
| ^
In file included from C:\Users\Doug\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.0\libraries\ESP8266WiFi\src/ESP8266WiFi.h:40,
from C:\Users\Doug\Documents\Arduino\libraries\MySensors/hal/architecture/ESP8266/MyHwESP8266.h:23,
from C:\Users\Doug\Documents\Arduino\libraries\MySensors/hal/architecture/ESP8266/MyHwESP8266.cpp:20,
from C:\Users\Doug\Documents\Arduino\libraries\MySensors/MySensors.h:58,
from C:\Users\Doug\Documents\Arduino\LoRa_GatewayESP8266OTA_RFM95_v1\LoRa_GatewayESP8266OTA_RFM95_v1.ino:174:
C:\Users\Doug\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.0\libraries\ESP8266WiFi\src/WiFiServer.h:85:14: note: declared here
85 | WiFiClient available(uint8_t* status = NULL) __attribute__((deprecated("Renamed to accept().")));
| ^~~~~~~~~
In file included from C:\Users\Doug\Documents\Arduino\libraries\MySensors/MySensors.h:235,
from C:\Users\Doug\Documents\Arduino\LoRa_GatewayESP8266OTA_RFM95_v1\LoRa_GatewayESP8266OTA_RFM95_v1.ino:174:
C:\Users\Doug\Documents\Arduino\libraries\MySensors/core/MyGatewayTransportEthernet.cpp:445:48: warning: 'WiFiClient WiFiServer::available(uint8_t*)' is deprecated: Renamed to accept(). [-Wdeprecated-declarations]
445 | EthernetClient c = _ethernetServer.available();
| ^
In file included from C:\Users\Doug\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.0\libraries\ESP8266WiFi\src/ESP8266WiFi.h:40,
from C:\Users\Doug\Documents\Arduino\libraries\MySensors/hal/architecture/ESP8266/MyHwESP8266.h:23,
from C:\Users\Doug\Documents\Arduino\libraries\MySensors/hal/architecture/ESP8266/MyHwESP8266.cpp:20,
from C:\Users\Doug\Documents\Arduino\libraries\MySensors/MySensors.h:58,
from C:\Users\Doug\Documents\Arduino\LoRa_GatewayESP8266OTA_RFM95_v1\LoRa_GatewayESP8266OTA_RFM95_v1.ino:174:
C:\Users\Doug\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.0\libraries\ESP8266WiFi\src/WiFiServer.h:85:14: note: declared here
85 | WiFiClient available(uint8_t* status = NULL) __attribute__((deprecated("Renamed to accept().")));
| ^~~~~~~~~
In file included from C:\Users\Doug\Documents\Arduino\libraries\MySensors/MySensors.h:441,
from C:\Users\Doug\Documents\Arduino\LoRa_GatewayESP8266OTA_RFM95_v1\LoRa_GatewayESP8266OTA_RFM95_v1.ino:174:
C:\Users\Doug\Documents\Arduino\libraries\MySensors/hal/architecture/ESP8266/MyMainESP8266.cpp: In function 'bool can_yield()':
C:\Users\Doug\Documents\Arduino\libraries\MySensors/hal/architecture/ESP8266/MyMainESP8266.cpp:95:9: error: 'cont_can_yield' was not declared in this scope; did you mean 'can_yield'?
95 | return cont_can_yield(g_pcont);
| ^~~~~~~~~~~~~~
| can_yield
C:\Users\Doug\Documents\Arduino\libraries\MySensors/hal/architecture/ESP8266/MyMainESP8266.cpp: In function 'void esp_yield_within_cont()':
C:\Users\Doug\Documents\Arduino\libraries\MySensors/hal/architecture/ESP8266/MyMainESP8266.cpp:101:2: error: 'cont_yield' was not declared in this scope; did you mean 'can_yield'?
101 | cont_yield(g_pcont);
| ^~~~~~~~~~
| can_yield
C:\Users\Doug\Documents\Arduino\libraries\MySensors/hal/architecture/ESP8266/MyMainESP8266.cpp: In function 'void loop_task(ETSEvent*)':
C:\Users\Doug\Documents\Arduino\libraries\MySensors/hal/architecture/ESP8266/MyMainESP8266.cpp:199:26: error: invalid operands of types 'void' and 'int' to binary 'operator!='
199 | if (cont_check(g_pcont) != 0) {
| ~~~~~~~~~~~~~~~~~~~ ^~ ~
| | |
| void int
Using library MySensors at version 2.3.2 in folder: C:\Users\Doug\Documents\Arduino\libraries\MySensors
``@d-smes said in transportPowerDown() with v2.2.0:
transportPowerDown()
Thanks guys; that worked! And if anyone else is interested, the radio automatically re-enables when you send a message.
@gohan - I monitor several temperatures, water levels, and flow rates associated with a duck pond and filtration system. Things can get out of whack fairly quickly due to pump inlet blockages, full filters, equipment failures, and weather induced surprises. Need quick updates so if there's a problem, I can intervene before a pump runs dry or I lose too much water.
sleep() puts the arduino (and radio) to sleep. I need a way to put the radio in a low current consumption state while the micro stays awake and acquires data from sensors and processes that info which can take a few seconds. Only then do I need to send the data after-which I can sleep.
In my use case, without transportPowerDown(), I burn an extra 14 mA for 2 seconds every minute. This equates to just over 11 mA-hr per day or over 330 mA-hr per month of needless energy consumption!
Re: How to Disable / Enable Radio within Loop
With MySensors v2.2.0, I observe that transportPowerDown() no longer works. With version 2.1.1, current consumption would drop from 17.5 mA to 3.5 mA (pro-mini @ 8MHz powered by 2x AA batteries, nRF24L01 direct connected, and no sensors) when the function was called.
Is there an equivalent / new command for v2.2.0 that will put the nRF radio in Standby or Power Down mode?
On other sites, they sell a 3.3V version and a 5V version. The 5V version has level translators and an on-board 3.3V LDO regulator. I can't tell which is which from the Ali description.
During normal operation, when a node wakes up from sleep, it looks like the radio is enabled right away and stays enabled until the node goes back to sleep. For my use case, I need the node to wake up with the radio disabled so I can acquire data for several seconds. After acquisition, I'd like to manually enable the radio to send the messages. When complete, node goes back to sleep (which automatically disables radio).
Are there commands to manually enable and disable the radio? Radio is a nRF24 on a pro-mini arduino if that matters.
@Yveaux said:
@d-smes Had a better look at the code. There are default LED pins, but these are 4, 5 & 6 for non-ESP (https://github.com/mysensors/MySensors/blob/development/MySensors.h#L113) and 7, 8 & 9 for ESP.
Thanks Yveaux. Those seem like the wrong defaults (4, 5, & 6 for non-ESP) because both the WizNET (W5100) and ENC28J60 Ethernet wiring instructions use pins 5 & 6 for the NRF24L01 Radio. And the MySensors 1.5.x Ethernet Sketch Example on that page has these definitions:
#define RADIO_CE_PIN 5 // radio chip enable
#define RADIO_SPI_SS_PIN 6 // radio SPI serial select
#define RADIO_ERROR_LED_PIN 7 // Error led pin
#define RADIO_RX_LED_PIN 8 // Receive led pin
#define RADIO_TX_LED_PIN 9 // the PCB, on board LED
It's also a bit confusing when you say " 7, 8 & 9 for ESP" because according to the ESP8266 WiFi Gateway page, pins 7 & 8 are used for the NRF Radio and pin 16 is the LED. Can you explain?
@Martin-Tellblom - Thanks Martin, that did the trick. I thought the defaults were pins 7, 8, & 9. But true enough, one must un-comment those three overrides to get the LEDs to work.
@Yveaux - MySensors 2.0.0
Thanks guys!
Oh, one last stupid question - How do I edit the topic to add "[Solved]"?
@mfalkvidd - The sketch is based off the EthernetGateway example in MySensors 2.0 and I have confirmed the # defines are done before the #include <MySensors.h>
Gateway is W5100 Ethernet with Nano. Uploaded Ethernet Gateway sketch with Arduino 1.6.7 IDE and debug shows data is being received and it registers in MYSController 1.0. So everything works as before except the RX, TX, and ERR LEDs no longer blink. #define MY_LEDS_BLINKING_FEATURE is NOT commented out in the sketch and LEDs are connected to pins 7, 8, and 9 (default). Again, these worked before the upgrade to MySensors 2.0. Any ideas?
@Boots33 - You'd the Man Boots!!! That was it. Commented that line out, and it's working! After inspecting the code again, I noticed the "!" (NOT) defined for "MY_W5100_SPI_EN" which indeed must have stopped Soft SPI. Thanks again!
Just updated to v2.0 and uploaded the GatewayW5100 example to a Nano with W5100 Ethernet board that I had been using with v1.5. I did un-comment the line "#define MY_W5100_SPI_EN 4 " so it would use Soft SPI. In the serial monitor, I get this:
0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0)
0;255;3;0;9;TSM:INIT
0;255;3;0;9;!TSM:RADIO:FAIL
0;255;3;0;9;!TSM:FAILURE
0;255;3;0;9;TSM:PDT
I doubt it's a radio failure because it was receiving messages just fine before I uploaded the new gateway sketch. Any ideas?
@Dick said:
gw.present(CHILD_ID_TEMP1, S_TEMP);
gw.present(CHILD_ID_TEMP1, S_TEMP);
Try changing the second ID to CHILD_ID_TEMP2 (note the "2") and see if that works better.
@derwish said:
Now I can only advise to make all the nodes in the new sub-panels.
I tried that- I had a new sub-panel open and then went to the Main Panel and deleted the nodes. Unfortunately, the MySensor nodes were re-created in the Main Panel instead of the sub-panel. Is there a setting I missed that directs where they are created?
I've just started playing with MyNodes and so far, it is REALLY GREAT! Thanks for all your hard work.
Newbie question: All the MySensor nodes are created in the Main Panel. How do I move them to a different panel?
The Dashboard gets really busy with just a single column of UI readings. Obviously this problem is solved if one splits up the Main Panel into multiple sub panels; ideally one panel per MySensor node. I know how to created a new panel, but there is no way to import the main panel. And in the Main Panel, I haven't found a way to export itself so I can import the MySensor nodes in the new sub panel.
In my temperature / humidity / barometer sensors, I have metric = false and send values in imperial units (degrees F and inches of mercury). In Domoticz, it appears the 29.5 deg F temperature value sent by the sensor is interpreted as Celsius and displayed as 85.1 deg F (i.e. it thinks 29.5 is deg C and converts it to deg F). Short of re-programming all my sensors to send Celsius values, is there a way to make Domo display the value it receives?
Likewise, the sensor sends a barometer value of 29.74 in-Hg and Domo displays it as 29.74 hPa. Unlike temperature the value, it does no conversion (good). But how do I get the Domoticz page to display different units?
@jkandasa Yep, error log full of the same sets of errors. Example of one error pair:
2015-09-16 11:41:55,150 WARN [Thread-3] [org.mycontroller.standalone.db.dao.SensorDaoImpl:52] Sensor:[org.mycontroller.standalone.db.tables.Sensor@e7f65f[id=<null>,sensorId=0,type=<null>,messageType=38,name=<null>,updateTime=<null>,status=<null>,lastValue=<null>,unit=<null>,node=org.mycontroller.standalone.db.tables.Node@18dbb32[id=4,name=<null>,version=<null>,updateTime=<null>,type=<null>,mySensorsVersion=<null>,batteryLevel=<null>,eraseEEPROM=<null>,firmware=<null>]]], Sensser Id should be in the range of 1~254
2015-09-16 11:41:55,150 ERROR [Thread-3] [org.mycontroller.standalone.mysensors.MessageMonitorThread:68] RawMessage[NodeId:4,ChildSensorId:0,MessageType:1,Ack:0,SubType:38,PayLoad:4.825] throws exception while processing!,
java.lang.NullPointerException: null
at org.mycontroller.standalone.mysensors.ProcessRawMessage.recordData(ProcessRawMessage.java:480) ~[mycontroller-standalone-0.0.2-alpha2-single.jar:na]
at org.mycontroller.standalone.mysensors.ProcessRawMessage.setSubMessageTypeSelector(ProcessRawMessage.java:449) ~[mycontroller-standalone-0.0.2-alpha2-single.jar:na]
at org.mycontroller.standalone.mysensors.ProcessRawMessage.messageTypeSelector(ProcessRawMessage.java:91) ~[mycontroller-standalone-0.0.2-alpha2-single.jar:na]
at org.mycontroller.standalone.mysensors.MessageMonitorThread.processRawMessage(MessageMonitorThread.java:60) [mycontroller-standalone-0.0.2-alpha2-single.jar:na]
at org.mycontroller.standalone.mysensors.MessageMonitorThread.run(MessageMonitorThread.java:82) [mycontroller-standalone-0.0.2-alpha2-single.jar:na]
at java.lang.Thread.run(Unknown Source) [na:1.8.0_60]
The clue appears to be "Sensser Id should be in the range of 1~254"
Nodes with multiple sensors show e.g. sensors 1- 11 but not sensor 0.
@jkandasa very nice work! As for my experience, I had a bit of trouble getting it started. Somehow, I was under the impression that double-clicking start.bat would automatically start the Java app. It was later that I realized I then need to point my browser to localhost:8443 and log in. Your WIKI is well written, but I somehow missed that step. BTW, I'm using the Ethernet gateway and editing settings was a breeze.
Possible bug to report- Sensors with an ID of 0 (zero) are not auto-detected. I have four nodes with sensor ID's of 0 that I know are sending data but they do not show up on Sensors page or on Action Board.