Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. Cravecode
    3. Posts
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Posts made by Cravecode

    • RE: Does HA ignore repeat sensor values?

      @martinhjelmare, sorry to bring up an old topic. I'm on a version of HA that includes your PR (v.: 0.54.0), however, my motion sensors only update their last_updated property when the motion sensor's state changes. I can see in HA'a log that it is receiving the expected repeated state (1;1;1;0;16;0) every X minutes, but the entity doesn't update the last_updated timestamp unless the motion sensor's state changes. Is there a way I can force the last_updated timestamp for each msg?

      Some context: I'm attempting to write automation rules to create alerts for sensors that have not checked-in within X minutes.

      posted in Home Assistant
      Cravecode
      Cravecode
    • RE: PIR Sensor false trigger every 10 minutes, same time node comes out of sleep.

      @NeverDie said in PIR Sensor false trigger every 10 minutes, same time node comes out of sleep.:

      IIRC, bypassing its LDO may help?

      I've actually already done that, to reduce power consumption.

      I'm running some tests now. It really looks like the 2.2.x version of the MySensors library helps. On my test piece, it has not had a false trigger in over an hour.

      posted in Troubleshooting
      Cravecode
      Cravecode
    • RE: PIR Sensor false trigger every 10 minutes, same time node comes out of sleep.

      @NeverDie I'm using the HC-SR501. Google turns up lots of related info for the HC-SR501 and false triggers. I'll see what others are doing too.

      posted in Troubleshooting
      Cravecode
      Cravecode
    • RE: PIR Sensor false trigger every 10 minutes, same time node comes out of sleep.

      @wallyllama I'm not cutting the power to the PIR sensor. Just putting the Arduino and radio to sleep.

      posted in Troubleshooting
      Cravecode
      Cravecode
    • Using 2.2.x MySensors library in Sloeber (Eclipse Arduino IDE). Build errors. (Solved)

      I wanted to use the 2.2.x development branch in my project. So, I swapped out the code that Sloeber adds when you add the MySensors 2.1.1 release version with the latest code from the Github repo.

      Context: This is for a PIR motion sensor using the NRF24L01+ radio.

      I.e.: Replace: /Applications/sloeber 4.app/Contents/Eclipse/arduinoPlugin/libraries/MySensors/2.1.1 with the contents of git clone https://github.com/mysensors/MySensors.git 2.1.1

      I tried building my project (a PIR node), and got several build errors.

      Example build errors:

      'int16_t' does not name a type MyTransportHAL.h /MotionSensorBattery/libraries/MySensors/hal/transport line 118 C/C++ Problem
      'int16_t' does not name a type MyTransportHAL.h /MotionSensorBattery/libraries/MySensors/hal/transport line 123 C/C++ Problem
      'int16_t' does not name a type MyTransportHAL.h /MotionSensorBattery/libraries/MySensors/hal/transport line 128 C/C++ Problem
      'int16_t' does not name a type MyTransportHAL.h /MotionSensorBattery/libraries/MySensors/hal/transport line 133 C/C++ Problem
      'int16_t' does not name a type MyTransportHAL.h /MotionSensorBattery/libraries/MySensors/hal/transport line 138 C/C++ Problem
      'int16_t' does not name a type MyTransportHAL.h /MotionSensorBattery/libraries/MySensors/hal/transport line 143 C/C++ Problem
      'uint8_t' does not name a type MyTransportHAL.h /MotionSensorBattery/libraries/MySensors/hal/transport line 68 C/C++ Problem
      'uint8_t' does not name a type MyTransportHAL.h /MotionSensorBattery/libraries/MySensors/hal/transport line 72 C/C++ Problem
      'uint8_t' does not name a type MyTransportHAL.h /MotionSensorBattery/libraries/MySensors/hal/transport line 81 C/C++ Problem
      'uint8_t' does not name a type MyTransportHAL.h /MotionSensorBattery/libraries/MySensors/hal/transport line 97 C/C++ Problem
      Function 'NRF5_ESB_getNodeID' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 65 Semantic Error
      Function 'NRF5_ESB_getReceivingRSSI' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 137 Semantic Error
      Function 'NRF5_ESB_getSendingRSSI' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 132 Semantic Error
      Function 'NRF5_ESB_initialize' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 54 Semantic Error
      Function 'NRF5_ESB_isDataAvailable' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 86 Semantic Error
      Function 'NRF5_ESB_powerDown' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 112 Semantic Error
      Function 'NRF5_ESB_powerUp' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 117 Semantic Error
      Function 'NRF5_ESB_readMessage' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 97 Semantic Error
      Function 'NRF5_ESB_sanityCheck' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 91 Semantic Error
      Function 'NRF5_ESB_sendMessage' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 80 Semantic Error
      Function 'NRF5_ESB_setNodeAddress' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 59 Semantic Error
      Function 'NRF5_ESB_sleep' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 122 Semantic Error
      Function 'NRF5_ESB_standBy' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 127 Semantic Error
      Function 'NRF5_ESB_startListening' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 60 Semantic Error
      Function 'NRF5_getTxPowerLevel' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 157 Semantic Error
      Function 'NRF5_getTxPowerPercent' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 152 Semantic Error
      Function 'NRF5_setTxPowerPercent' could not be resolved MyTransportNRF5_ESB.cpp /MotionSensorBattery/libraries/MySensors/hal/transport line 162 Semantic Error
      make: *** [libraries/MySensors/hal/transport/MyTransportRF24.cpp.o] Error 1 MotionSensorBattery C/C++ Problem

      To fix this, I simply excluded the ./hal directory from the build. Everything appears to work fine now.

      I.e.: expand libraries > expand MySensors > right click the ./hal directory > Properties > select C/C++ Build > tick Exclude resource from build.

      Can anyone shed some light on the work being done in the ./hal directory? Am I messing something up by excluding this from my build?

      posted in Development
      Cravecode
      Cravecode
    • RE: PIR Sensor false trigger every 10 minutes, same time node comes out of sleep.

      I tried the 2.2.x development branch of the MySensors library per @Yveaux's suggestion. The development branch appears to have fixed my issue!

      posted in Troubleshooting
      Cravecode
      Cravecode
    • RE: PIR Sensor false trigger every 10 minutes, same time node comes out of sleep.

      Thanks for the replies!
      I'll checkout the 2.2.x dev branch. I tried various sizes for capacitors with no luck.

      posted in Troubleshooting
      Cravecode
      Cravecode
    • PIR Sensor false trigger every 10 minutes, same time node comes out of sleep.

      I'm running the following: (PIR Node, MySensors Library v2.1.1) > (ESP8266 Gateway, MySensors Library v2.1.1) < (Home Assistant, 0.50.2).

      The PIR node is currently on a breadboard powered by my test bench power supply to rule out as many factors as possible.

      In my Home Assistant logbook, I can see the PIR is triggered every 10 minutes, all day long. At the end of my loop(){...}, I have the following code:

      unsigned long SLEEP_TIME = 600000; // (10 minutes), Sleep time between reports (in milliseconds)
      #define DIGITAL_INPUT_SENSOR 3  // The digital input you attached your motion sensor. 
      
      /* ... */
      
      void loop()
      {
      
       // Read digital motion value
        bool tripped = digitalRead(DIGITAL_INPUT_SENSOR) == HIGH;
      
        Serial.println(tripped);
        send(msg.set(tripped?"1":"0"));  // Send tripped value to gw
      
        wait(500);
      
      /**
      defined by Arduino: 
        CHANGE = 1
      **/ 
        sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), CHANGE, SLEEP_TIME);
      }
      

      I have verified that I do not get the false triggers if i disconnect the PIR sensor from the Arduino's pin 3. So, I know it's the actual PIR reacting to the Arduino coming out of sleep.

      Could this be noise on the power rail from the Arduino or the NRF24L01+? If so, what are my options? I currently have a 4.7uf cap bridged across the NRF24L01's power connections. I will try adding a wait(500); before I actually read pin 3's value.

      FYI: I don't have a scope to test power noise 😞

      posted in Troubleshooting
      Cravecode
      Cravecode
    • RE: Does HA ignore repeat sensor values?

      @martinhjelmare I see you PR was merged a while ago. It looks like the force_update property defaults to TRUE. Is this now the default behavior for all MySensors sensors?

      Sorry if this seems obvious, I just want to double check.
      Thanks for your work and time!

      posted in Home Assistant
      Cravecode
      Cravecode
    • RE: ESP8266 Gateway restarts when data is received from node [Solved]

      @CurlyWurly,

      My situation involves 2 devices:

      • Device 1 - Gateway (ESP8266 + NRF24L01)
      • Device 2 - Temp sensor (NRF24L01 + DHT11)

      FYI: I have a 4.7uF capacitor across the GND and VCC pins of the NRF24L01 on both devices.

      This may sound silly, but make sure your ESP8266 is booted into the correct mode:
      GPIO 0 = High
      GPIO 2 = High
      GPIO 15 = Low

      posted in Troubleshooting
      Cravecode
      Cravecode
    • RE: ESP8266 Gateway restarts when data is received from node [Solved]

      @scalz,
      I'm using the DHT11

      posted in Troubleshooting
      Cravecode
      Cravecode
    • Does HA ignore repeat sensor values?

      I'm trying to diagnose some repeater issues. I have a temperature sensor sending data every 10 seconds. Home Assistant will go several minutes before it will show a last updated timestamp for my temperature sensor. I can verify in Netcat that the gateway is getting the values every 10 seconds. By chance, I noticed in the debug output, Home Assistant only fires the Event state_changed when the value actually changes. I guess this makes sense.
      Is this normal behavior for HA? Can this be disabled so every sensor message is logged?

      posted in Home Assistant
      Cravecode
      Cravecode
    • RE: nodeMCU, MY_GATEWAY_ESP8266 and Temp Sensor

      @mysensors-6043,
      The normal setup involves 3 pieces:

      1. The sensor (aka node) emitting data via RF using something like a NRF24L01
      2. A gateway that receives the sensor data via the RF module (NRF24L01) and sends it to a controller over ethernet or wifi.
      3. A controller to manage connected nodes and present data to the user.

      It seems like you're combining the sensor and gateway into one device. If this is the case, I think you can comment out the #define MY_RADIO_RFM69 line as there is no radio connected. I don't know how this plays into the registration process of a sensor. There is no ID getting associated to the sensor because this is a gateway.

      Maybe someone else can chime in who knows whether it's okay to combine the gateway and sensor into one device. If so, how is registration and ID assignment handled?

      @mysensors-6043,
      Post a updated version of your sketch.

      posted in Troubleshooting
      Cravecode
      Cravecode
    • RE: nodeMCU, MY_GATEWAY_ESP8266 and Temp Sensor

      @mysensors-6043,
      The sketch you posted looks like you combined the sensors with the NodeMCU, is this true? Is this NodeMCU acting as a gateway as well?

      posted in Troubleshooting
      Cravecode
      Cravecode
    • RE: nodeMCU, MY_GATEWAY_ESP8266 and Temp Sensor

      @mysensors-6043,
      Have you been able to confirm that you get temperature readings on the sensor? I would try to simplify your sketch to rule things out.

      Here's what I'd do, in the following order:

      • Remove all MySensors related code and just get the sensor reading to the serial monitor.
      • I see you're looping over several temperature sensors on the node, simplify this, only read one for starters.
      • Verify your gateway is on the network by using telnet or netcat. I.e.: nc xxx.xxx.xxx.xxx 5003
      • Try just getting your node to "present" to the gateway. Reading the sensor debug via the serial monitor and watch the gateway via netcat.
      posted in Troubleshooting
      Cravecode
      Cravecode
    • RE: "Node 1 is unknown" requires a restart. 2nd child element never presents

      I'll create a pull request to update the Air Humidity Sensor example (DhtTemperatureAndHumiditySensor.ino) and reference this post.

      posted in Home Assistant
      Cravecode
      Cravecode
    • RE: "Node 1 is unknown" requires a restart. 2nd child element never presents

      @martinhjelmare,
      Updated my sketch, thanks again!

      posted in Home Assistant
      Cravecode
      Cravecode
    • RE: "Node 1 is unknown" requires a restart. 2nd child element never presents

      @martinhjelmare Thanks!!
      I added a 500ms delay between each sensor's present call. I also added a 1000ms delay before the sensor sleeps. That seems to have fixed the issue.

      I also confirmed that both delays, between children presentation and before sleep were required.

      posted in Home Assistant
      Cravecode
      Cravecode
    • RE: "Node 1 is unknown" requires a restart. 2nd child element never presents

      @martinhjelmare

          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      
              Hello, and welcome to Home Assistant!
      
              We'll hope that we can make all your dreams come true.
      
              Here are some resources to get started:
      
               - Configuring Home Assistant:
                 https://home-assistant.io/getting-started/configuration/
      
               - Available components:
                 https://home-assistant.io/components/
      
               - Troubleshooting your configuration:
                 https://home-assistant.io/getting-started/troubleshooting-configuration/
      
               - Getting help:
                 https://home-assistant.io/help/
      
              This message is generated by the introduction component. You can
              disable it in configuration.yaml.
      
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      
      INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=introduction>
      INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=recorder>
      WARNING:mysensors.mysensors:File does not exist or is not readable: /Users/cravecode/.homeassistant/mysensors/esp8266-gateway.json
      WARNING:mysensors.mysensors:Trying backup file: /Users/cravecode/.homeassistant/mysensors/esp8266-gateway.json.bak
      WARNING:mysensors.mysensors:File does not exist or is not readable: /Users/cravecode/.homeassistant/mysensors/esp8266-gateway.json.bak
      WARNING:mysensors.mysensors:Failed to load sensors from file: /Users/cravecode/.homeassistant/mysensors/esp8266-gateway.json
      INFO:mysensors.mysensors:Trying to connect to ('192.168.3.103', 5003)
      INFO:mysensors.mysensors:Connected to ('192.168.3.103', 5003)
      DEBUG:mysensors.mysensors:Received 0;255;3;0;14;Gateway startup complete.
      
      DEBUG:mysensors.mysensors:Received 1;1;1;0;0;71.6
      
      WARNING:mysensors.mysensors:Node 1 is unknown
      INFO:mysensors.mysensors:Requesting new presentation for node 1
      DEBUG:mysensors.mysensors:Sending 1;255;3;0;19;
      
      DEBUG:mysensors.mysensors:Received 1;0;1;0;1;53.0
      
      WARNING:mysensors.mysensors:Node 1 is unknown
      INFO:mysensors.mysensors:Requesting new presentation for node 1
      DEBUG:mysensors.mysensors:Sending 1;255;3;0;19;
      
      DEBUG:mysensors.mysensors:Received 1;1;1;0;0;71.6
      
      WARNING:mysensors.mysensors:Node 1 is unknown
      INFO:mysensors.mysensors:Requesting new presentation for node 1
      DEBUG:mysensors.mysensors:Sending 1;255;3;0;19;
      
      DEBUG:mysensors.mysensors:Received 1;0;1;0;1;53.0
      
      WARNING:mysensors.mysensors:Node 1 is unknown
      INFO:mysensors.mysensors:Requesting new presentation for node 1
      DEBUG:mysensors.mysensors:Sending 1;255;3;0;19;
      
      DEBUG:mysensors.mysensors:Received 1;1;1;0;0;71.6
      
      WARNING:mysensors.mysensors:Node 1 is unknown
      INFO:mysensors.mysensors:Requesting new presentation for node 1
      DEBUG:mysensors.mysensors:Sending 1;255;3;0;19;
      
      DEBUG:mysensors.mysensors:Received 1;0;1;0;1;53.0
      
      WARNING:mysensors.mysensors:Node 1 is unknown
      INFO:mysensors.mysensors:Requesting new presentation for node 1
      DEBUG:mysensors.mysensors:Sending 1;255;3;0;19;
      
      DEBUG:mysensors.mysensors:Received 1;255;0;0;17;2.0.1-beta
      
      >>>>> @martinhjelmare, Below is where I restart the sensor to get it to present.
      
      DEBUG:homeassistant.components.mysensors:Update sensor_update: node 1
      INFO:homeassistant.components.mysensors:No sketch_name: node 1
      INFO:homeassistant.components.mysensors:No sketch_name: node 1
      INFO:homeassistant.components.mysensors:No sketch_name: node 1
      INFO:homeassistant.components.mysensors:No sketch_name: node 1
      DEBUG:mysensors.mysensors:Received 1;255;3;0;6;0
      
      DEBUG:mysensors.mysensors:Sending 1;255;3;0;6;I
      
      DEBUG:mysensors.mysensors:Received 1;255;3;0;11;TemperatureAndHumidity
      
      DEBUG:homeassistant.components.mysensors:Update sensor_update: node 1
      DEBUG:mysensors.mysensors:Received 1;255;3;0;12;1.4
      
      DEBUG:homeassistant.components.mysensors:Update sensor_update: node 1
      DEBUG:mysensors.mysensors:Received 1;0;0;0;7;
      
      DEBUG:homeassistant.components.mysensors:Update sensor_update: node 1
      DEBUG:mysensors.mysensors:Received 1;1;1;0;0;71.6
      
      WARNING:mysensors.mysensors:Child 1 is unknown
      INFO:mysensors.mysensors:Requesting new presentation for node 1
      DEBUG:mysensors.mysensors:Sending 1;255;3;0;19;
      
      DEBUG:mysensors.mysensors:Received 1;0;1;0;1;53.0
      
      DEBUG:homeassistant.components.mysensors:Update sensor_update: node 1
      INFO:homeassistant.components.mysensors:Adding new devices: <Entity TemperatureAndHumidity 1 0: None>
      DEBUG:homeassistant.components.mysensors:TemperatureAndHumidity 1 0: value_type 1, value = 53.0
      DEBUG:mysensors.mysensors:Received 1;1;1;0;0;71.6
      
      WARNING:mysensors.mysensors:Child 1 is unknown
      INFO:mysensors.mysensors:Requesting new presentation for node 1
      DEBUG:mysensors.mysensors:Sending 1;255;3;0;19;
      
      DEBUG:mysensors.mysensors:Received 1;0;1;0;1;52.0
      
      DEBUG:homeassistant.components.mysensors:Update sensor_update: node 1
      DEBUG:homeassistant.components.mysensors:TemperatureAndHumidity 1 0: value_type 1, value = 52.0
      DEBUG:mysensors.mysensors:Received 1;1;1;0;0;71.6
      
      WARNING:mysensors.mysensors:Child 1 is unknown
      INFO:mysensors.mysensors:Requesting new presentation for node 1
      DEBUG:mysensors.mysensors:Sending 1;255;3;0;19;
      
      DEBUG:mysensors.mysensors:Received 1;0;1;0;1;53.0
      
      DEBUG:homeassistant.components.mysensors:Update sensor_update: node 1
      DEBUG:homeassistant.components.mysensors:TemperatureAndHumidity 1 0: value_type 1, value = 53.0
      DEBUG:mysensors.mysensors:Received 1;1;1;0;0;71.6
      
      posted in Home Assistant
      Cravecode
      Cravecode
    • RE: "Node 1 is unknown" requires a restart. 2nd child element never presents

      @martinhjelmare, thanks for the quick reply. I'll post the logs when I get home tonight.

      posted in Home Assistant
      Cravecode
      Cravecode
    • "Node 1 is unknown" requires a restart. 2nd child element never presents

      I'm attempting to use the TemperatureAndHumidity example sketch.
      Gateway and Node are running 2.0

      When I start up the node, gateway and HA, I get repeat errors Node 1 is unknown in the HA log. To fix this, I restart the temperature sensor and the first child (child ID 0) presents and displays in HA correctly and continues to update. However, the second child (ID 1) never presents leaving HA to constantly logging:

      WARNING:mysensors.mysensors:Child 1 is unknown
      INFO:mysensors.mysensors:Requesting new presentation for node 1
      

      I also tried using the dev branch of Home Assistant with the same results.

      I should also mention I tried configuring the sensor to only run with one child. That worked regardless of whether I was sending Temperature or Humidity sensor info. It seems like it is an issue with 2 or more child elements.

      Temp sensor log:
      Contains initial startup and the first restart to get it working with HA.

      MCO:BGN:INIT NODE,CP=RNNNA--,VER=2.0.1-beta
      TSM:INIT
      TSM:INIT:TSP OK
      TSF:ASID:OK,ID=1
      TSM:FPAR
      TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
      TSF:MSG:READ,0-0-1,s=255,c=3,t=8,pt=1,l=1,sg=0:0
      TSF:MSG:FPAR RES,ID=0,D=0
      TSF:MSG:FPAR OK,ID=0,D=1
      TSM:FPAR:OK
      TSM:ID
      TSM:ID:OK,ID=1
      TSM:UPL
      TSF:PING:SEND,TO=0
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
      TSF:MSG:READ,0-0-1,s=255,c=3,t=25,pt=1,l=1,sg=0:1
      TSF:MSG:PONG RECV,HP=1
      TSF:CHKUPL:OK
      TSM:UPL:OK
      TSM:READY
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
      TSF:MSG:SEND,1-1-0-0,s=255,c=0,t=17,pt=0,l=10,sg=0,ft=0,st=OK:2.0.1-beta
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=OK:0
      TSF:MSG:READ,0-0-1,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=11,pt=0,l=22,sg=0,ft=0,st=OK:TemperatureAndHumidity
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=OK:1.4
      TSF:MSG:SEND,1-1-0-0,s=0,c=0,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      TSF:MSG:SEND,1-1-0-0,s=1,c=0,t=6,pt=0,l=0,sg=0,ft=0,st=OK:
      MCO:REG:REQ
      !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=NACK:2
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=26,pt=1,l=1,sg=0,ft=1,st=OK:2
      TSF:MSG:READ,0-0-1,s=255,c=3,t=27,pt=1,l=1,sg=0:1
      MCO:PIM:NODE REG=1
      MCO:BGN:STP
      MCO:SLP:MS=1000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      MCO:BGN:INIT OK,ID=1,PAR=0,DIS=1,REG=1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:BGN:INIT NODE,CP=RNNNA--,VER=2.0.1-beta
      TSM:INIT
      TSM:INIT:TSP OK
      TSF:ASID:OK,ID=1
      TSM:FPAR
      TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
      TSF:MSG:READ,0-0-1,s=255,c=3,t=8,pt=1,l=1,sg=0:0
      TSF:MSG:FPAR RES,ID=0,D=0
      TSF:MSG:FPAR OK,ID=0,D=1
      TSM:FPAR:OK
      TSM:ID
      TSM:ID:OK,ID=1
      TSM:UPL
      TSF:PING:SEND,TO=0
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
      TSF:MSG:READ,0-0-1,s=255,c=3,t=25,pt=1,l=1,sg=0:1
      TSF:MSG:PONG RECV,HP=1
      TSF:CHKUPL:OK
      TSM:UPL:OK
      TSM:READY
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
      TSF:MSG:SEND,1-1-0-0,s=255,c=0,t=17,pt=0,l=10,sg=0,ft=0,st=OK:2.0.1-beta
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=OK:0
      TSF:MSG:READ,0-0-1,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
      TSF:MSG:READ,0-0-1,s=255,c=3,t=6,pt=0,l=1,sg=0:I
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=11,pt=0,l=22,sg=0,ft=0,st=OK:TemperatureAndHumidity
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=OK:1.4
      TSF:MSG:SEND,1-1-0-0,s=0,c=0,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      !TSF:MSG:SEND,1-1-0-0,s=1,c=0,t=6,pt=0,l=0,sg=0,ft=0,st=NACK:
      MCO:REG:REQ
      TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=26,pt=1,l=1,sg=0,ft=1,st=OK:2
      TSF:MSG:READ,0-0-1,s=255,c=3,t=27,pt=1,l=1,sg=0:1
      MCO:PIM:NODE REG=1
      MCO:BGN:STP
      MCO:SLP:MS=1000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      MCO:BGN:INIT OK,ID=1,PAR=0,DIS=1,REG=1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40 
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      MCO:SLP:WUP=-1
      TSF:MSG:SEND,1-1-0-0,s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=OK:73.4
      T: 73.40
      TSF:MSG:SEND,1-1-0-0,s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=OK:56.0
      H: 56.00
      MCO:SLP:MS=10000,SMS=0,I1=255,M1=255,I2=255,M2=255
      MCO:SLP:TPD
      

      Netcat log of gateway:
      This is after the first restart to get the Node actually presented to HA.

      1;255;3;0;11;TemperatureAndHumidity
      1;255;3;0;12;1.4
      1;0;0;0;7;
      1;1;1;0;0;73.4
      1;0;1;0;1;56.0
      1;1;1;0;0;73.4
      1;0;1;0;1;56.0
      1;1;1;0;0;73.4
      1;0;1;0;1;56.0
      

      I've tried everything I can think of. I really hope someone can shed some light on why the second child never presents.

      posted in Home Assistant
      Cravecode
      Cravecode
    • RE: ESP8266 Gateway restarts when data is received from node [Solved]

      After giving on up finding a possible solution for the ESP8266 gateway, I decided to focus on potential issues with the sensors. I added a 4.7uF capacitor to the radios on the gateway and sensor as the troubleshooting thread suggested and it fixed my gateway issues.

      posted in Troubleshooting
      Cravecode
      Cravecode
    • RE: ESP8266 Gateway restarts when data is received from node [Solved]

      Made sure to use ESP8266 board version 2.3.0. I tried the latest from development and master branches of the MySensors repo with no luck. It still crashes shortly after data is sent to it.

      0;255;3;0;9;No registration required
      0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1
      pm open,type:2 0
      0;255;3;0;9;TSP:MSG:READ 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
      0;255;3;0;9;TSP:MSG:BC
      0;255;3;0;9;TSP:MSG:FPAR REQ (sender=1)
      0;255;3;0;9;TSP:CHKUPL:OK
      0;255;3;0;9;TSP:MSG:GWL OK
      0;255;3;0;9;TSP:MSG:SEND 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=ok:0
      0;255;3;0;9;TSP:MSG:READ 1-1-0 s=255,c=3,t=24,pt=1,l=1,sg=0:1
      0;255;3;0;9;TSP:MSG:PINGED (ID=1, hops=1)
      
      Soft WDT reset
      
      ctx: cont 
      sp: 3ffef610 end: 3ffef980 offset: 01b0
      
      >>>stack>>>
      3ffef7c0:  40107050 00000000 3ffefc48 4020495b  
      3ffef7d0:  00000000 3ffefc48 00000000 40202316  
      3ffef7e0:  001e8480 3ffe0001 3ffef9df 40202376  
      3ffef7f0:  00000000 0000000e 00000000 00000001  
      3ffef800:  00000000 00000000 00000001 00000001  
      3ffef810:  00000030 0000000e 000012bf 40202411  
      3ffef820:  00000001 3ffef9d8 00000001 4020250e  
      3ffef830:  00000008 00000030 00000010 00000027  
      3ffef840:  00000001 00000001 3ffef9d8 40202f54  
      3ffef850:  40107050 3ffef8b1 3ffefc48 00000061  
      3ffef860:  3ffef8b0 3ffefc48 3ffef8b0 40202376  
      3ffef870:  001e8480 3ffe0001 3ffefc48 00000030  
      3ffef880:  00000000 00000000 3ffefa00 00000001  
      3ffef890:  3ffefa1a 00000001 00000004 00000001  
      3ffef8a0:  000000ff 3ffef9d8 00000001 4020271d  
      3ffef8b0:  00000001 00000001 00000001 00000001  
      3ffef8c0:  000000ff 3ffef9d8 00000001 40203099  
      3ffef8d0:  3ffefa1a 00000001 3ffef9f9 402040ee  
      3ffef8e0:  00000018 00000001 00000001 00000000  
      3ffef8f0:  3ffef9a4 00000001 3ffefb30 40203a1a  
      3ffef900:  00000003 00000018 00000023 000000ff  
      3ffef910:  00000000 00000004 3ffefa1e 3ffee958  
      3ffef920:  3fffdad0 00000000 00000006 3ffee958  
      3ffef930:  3fffdad0 00000000 00000005 40204258  
      3ffef940:  3fffdad0 00000000 3ffee950 40204274  
      3ffef950:  00000000 00000000 3ffee950 40203b74  
      3ffef960:  3fffdad0 00000000 3ffee950 40204550  
      3ffef970:  feefeffe feefeffe 3ffee960 40100114  
      <<<stack<<<
      
      posted in Troubleshooting
      Cravecode
      Cravecode
    • RE: ESP8266 Gateway restarts when data is received from node [Solved]

      Looks like it may be related to ESP8266 MySensors Gateway Crashes when Node Connects. I'll try different ESP8266 board versions and post my results.

      posted in Troubleshooting
      Cravecode
      Cravecode
    • ESP8266 Gateway restarts when data is received from node [Solved]

      I'm using the latest example for a ESP8266 Gateway and the Humidity example.

      When the gateway receives data from the sensor, the gateway crashes and restarts. Is anyone having similar issues?

      I have 3.3v power line coming from a DC adapter.

      0;255;3;0;9;TSP:MSG:GWL OK
      0;255;3;0;9;TSP:MSG:SEND 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=ok:0
      0;255;3;0;9;TSP:MSG:READ 1-1-0 s=255,c=3,t=24,pt=1,l=1,sg=0:1
      0;255;3;0;9;TSP:MSG:PINGED (ID=1, hops=1)
      0;255;3;0;9;!TSP:MSG:SEND 0-0-1-1 s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=fail:1
      0;255;3;0;9;TSP:SANCHK:OK
      0;255;3;0;9;TSP:MSG:READ 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
      0;255;3;0;9;TSP:MSG:BC
      0;255;3;0;9;TSP:MSG:FPAR REQ (sender=1)
      0;255;3;0;9;TSP:CHKUPL:OK (FLDCTRL)
      0;255;3;0;9;TSP:MSG:GWL OK
      0;255;3;0;9;TSP:MSG:SEND 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=ok:0
      0;255;3;0;9;TSP:MSG:READ 1-1-0 s=255,c=3,t=24,pt=1,l=1,sg=0:1
      0;255;3;0;9;TSP:MSG:PINGED (ID=1, hops=1)
      
      Soft WDT reset
      
      ctx: cont 
      sp: 3ffef600 end: 3ffef980 offset: 01b0
      
      >>>stack>>>
      3ffef7b0:  00000000 3ffefc48 3ffefc48 4020495b  
      3ffef7c0:  40107050 00000000 3ffefc48 4020495b  
      3ffef7d0:  00000000 3ffefc48 00000000 40202376  
      3ffef7e0:  001e8480 3ffe0001 3ffef9df 40202376  
      3ffef7f0:  00000000 0000000e 00000000 00000001  
      3ffef800:  00000000 00000000 00000001 00000001  
      3ffef810:  00000030 0000000e 00000013 40202411  
      3ffef820:  00000001 3ffef9d8 00000001 4020250e  
      3ffef830:  00000008 3fffc6fc 00000001 00000027  
      3ffef840:  00000001 00000001 3ffef9d8 40202f54  
      3ffef850:  40107050 3ffef8b1 3ffefc48 00000061  
      3ffef860:  3ffef8b0 3ffefc48 3ffef8b0 40202376  
      3ffef870:  001e8480 3ffe0001 3ffefc48 00000000  
      3ffef880:  00000000 00000000 3ffefa00 00000001  
      3ffef890:  3ffefa1a 00000001 00000004 00000001  
      3ffef8a0:  000000ff 3ffef9d8 00000001 4020271d  
      3ffef8b0:  00000001 00000001 00000001 00000001  
      3ffef8c0:  000000ff 3ffef9d8 00000001 40203099  
      3ffef8d0:  3ffefa1a 00000001 3ffef9f9 402040ee  
      3ffef8e0:  00000018 00000001 00000001 00000000  
      3ffef8f0:  3ffef9a4 00000001 3ffefb30 40203a1a  
      3ffef900:  00000003 00000018 00000023 000000ff  
      3ffef910:  00000000 00000001 00000001 3ffee958  
      3ffef920:  3fffdad0 00000000 00000006 3ffee958  
      3ffef930:  3fffdad0 00000000 00000005 40204258  
      3ffef940:  3fffdad0 00000000 3ffee950 40204274  
      3ffef950:  00000000 00000000 3ffee950 40203b74  
      3ffef960:  3fffdad0 00000000 3ffee950 40204550  
      3ffef970:  feefeffe feefeffe 3ffee960 40100114  
      <<<stack<<<
      c_�rS�f�0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0)
      0;255;3;0;9;TSM:INIT
      0;255;3;0;9;TSM:RADIO:OK
      0;255;3;0;9;TSM:GW MODE
      

      Any feedback would be appreciated.

      Update 1

      I should also mention this happens within minutes of powering everything up.

      posted in Troubleshooting
      Cravecode
      Cravecode