Ethernet gateway with Homeassistant
-
I read a lot about Ethernet gateway problem with home assistant but i can't catch the reason for my problem as i get a different logs from both gateway and home-assistant i want to establish a connection between gateway and home-assistant using default Ethernet sketch and below configuration in home-assistant:
mysensors:
gateways:
- device: '192.168.1.10'
tcp_port: 5003
persistence_file: '/home/homeassistant/.homeassistant/mysensors.json'
persistence: true
optimistic: false
below are the logs from home-assistant:
2018-11-29 21:12:39 ERROR (MainThread) [mysensors.gateway_tcp] Failed to connect to socket at ('192.168.1.10', 5003)
2018-11-29 21:12:52 ERROR (MainThread) [mysensors.gateway_tcp] Failed to connect to socket at ('192.168.1.10', 5003)
2018-11-29 21:13:05 ERROR (MainThread) [mysensors.gateway_tcp] Failed to connect to socket at ('192.168.1.10', 5003)
2018-11-29 21:13:19 ERROR (MainThread) [mysensors.gateway_tcp] Failed to connect to socket at ('192.168.1.10', 5003)
2018-11-29 21:13:32 ERROR (MainThread) [mysensors.gateway_tcp] Failed to connect to socket at ('192.168.1.10', 5003)
also some times i get connection to socket time out.below are the logs from serial monitor which there are some of them unknown in Log Parser:
0 MCO:BGN:INIT GW,CP=RNNGA---,VER=2.3.0
3 TSM:INIT
4 TSF:WUR:MS=0
10 !TSM:INIT:TSP FAIL
12 TSM:FAIL:CNT=1
14 TSM:FAIL:DIS
15 TSF:TDI:TSL
10018 TSM:FAIL:RE-INIT
10020 TSM:INIT
10027 !TSM:INIT:TSP FAIL
10030 TSM:FAIL:CNT=2
10031 TSM:FAIL:DIS
10033 TSF:TDI:TSL
20036 TSM:FAIL:RE-INIT
20038 TSM:INIT
-
Welcome to the forum @ahmed-amin
10 !TSM:INIT:TSP FAIL
means that the gateway is unable to initialize the transport/radio. You're using the nrf24l01+ radio? Triple-check the wiring and post photos if you can't find any problem. A new pair of eyes is often necessary.
-
Thanks @mfalkvidd i'll check but i also wonder if i can establish and initialize a connection between controller and Ethernet gateway first then attach the sensors and actuators as from home-assistant logs it seems that the connection couldn't establish is it because what you mention.
very thanks again for your support.
-
@ahmed-amin the gateway will only start responding to incoming ethernet connections after it has successfully initialized the radio.
So either fix the problem, or disable the radio by commenting the line that selects the radio and upload the modified sketch.
-
@mfalkvidd below is modified sketch as you mentioned :
/**- The MySensors Arduino library handles the wireless radio link and protocol
- between your home built sensors/actuators and HA controller of choice.
- The sensors forms a self healing radio network with optional repeaters. Each
- repeater and gateway builds a routing tables in EEPROM which keeps track of the
- network topology allowing messages to be routed to nodes.
- Created by Henrik Ekblad henrik.ekblad@mysensors.org
- Copyright (C) 2013-2015 Sensnology AB
- Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
- Documentation: http://www.mysensors.org
- Support Forum: http://forum.mysensors.org
- This program is free software; you can redistribute it and/or
- modify it under the terms of the GNU General Public License
- version 2 as published by the Free Software Foundation.
- REVISION HISTORY
- Version 1.0 - Henrik EKblad
- Contribution by a-lurker and Anticimex,
- Contribution by Norbert Truchsess norbert.truchsess@t-online.de
- Contribution by Tomas Hozza thozza@gmail.com
- DESCRIPTION
- The EthernetGateway sends data received from sensors to the ethernet link.
- The gateway also accepts input on ethernet interface, which is then sent out to the radio network.
- The GW code is designed for Arduino 328p / 16MHz. ATmega168 does not have enough memory to run this program.
- LED purposes:
-
- To use the feature, uncomment MY_DEFAULT_xxx_LED_PIN in the sketch below
-
- RX (green) - blink fast on radio message received. In inclusion mode will blink fast only on presentation received
-
- TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly
-
- ERR (red) - fast blink on error during transmission error or receive crc error
- See http://www.mysensors.org/build/ethernet_gateway for wiring instructions.
*/
// Enable debug prints to serial monitor
#define MY_DEBUG// Enable and select radio type attached
//#define MY_RADIO_NRF24
//#define MY_RADIO_NRF5_ESB
//#define MY_RADIO_RFM69
//#define MY_RADIO_RFM95// Enable gateway ethernet module type
#define MY_GATEWAY_W5100// W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
//#define MY_W5100_SPI_EN 4// Enable Soft SPI for NRF radio (note different radio wiring is required)
// The W5100 ethernet module seems to have a hard time co-operate with
// radio on the same spi bus.
//#if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
//#define MY_SOFTSPI
//#define MY_SOFT_SPI_SCK_PIN 14
//#define MY_SOFT_SPI_MISO_PIN 16
//#define MY_SOFT_SPI_MOSI_PIN 15
//#endif// When W5100 is connected we have to move CE/CSN pins for NRF radio
//#ifndef MY_RF24_CE_PIN
//#define MY_RF24_CE_PIN 5
//#endif
//#ifndef MY_RF24_CS_PIN
//#define MY_RF24_CS_PIN 6
//#endif// Enable UDP communication
//#define MY_USE_UDP // If using UDP you need to set MY_CONTROLLER_IP_ADDRESS below// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
#define MY_IP_ADDRESS 192,168,1,10// If using static ip you can define Gateway and Subnet address as well
#define MY_IP_GATEWAY_ADDRESS 192,168,1,1
#define MY_IP_SUBNET_ADDRESS 255,255,255,0// Renewal period if using DHCP
//#define MY_IP_RENEWAL_INTERVAL 60000// 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,1,6// 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 Arduino 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// 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 7 // Error led pin
//#define MY_DEFAULT_RX_LED_PIN 8 // Receive led pin
//#define MY_DEFAULT_TX_LED_PIN 9 // Transmit led pin#if defined(MY_USE_UDP)
#include <EthernetUdp.h>
#endif
#include <Ethernet.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
}and next are the logs from serial monitor :
0 MCO:BGN:INIT GW,CP=R-NGA---,VER=2.3.0
0 MCO:BGN:INIT GW,CP=R-NGA---,VER=2.3.0
564 GWT:TIN:IP=192.168.1.10
1568 !GWT:TIN:ETH FAIL
1570 MCO:BGN:STP
1572 MCO:REG:NOT NEEDED
1574 MCO:BGN:INIT OK,TSP=NA
1579 !GWT:TSA:ETH FAIL
1584 !GWT:TSA:ETH FAIL
1589 !GWT:TSA:ETH FAIL
1593 !GWT:TSA:ETH FAIL
1598 !GWT:TSA:ETH FAIL
1603 !GWT:TSA:ETH FAIL
1608 !GWT:TSA:ETH FAIL (this keep repeating)actually now i can ping to the gateway but still get this from home-assistant logs:
Dec 01 15:33:09 raspberrypi hass[291]: 2018-12-01 15:33:09 INFO (MainThread) [mysensors.gateway_tcp] Waiting 10.0 secs before trying to connect again
Dec 01 15:33:19 raspberrypi hass[291]: 2018-12-01 15:33:19 INFO (MainThread) [mysensors.gateway_tcp] Trying to connect to ('192.168.1.10', 5003)
Dec 01 15:33:29 raspberrypi hass[291]: 2018-12-01 15:33:29 ERROR (MainThread) [mysensors.gateway_tcp] Connecting to socket timed out for ('192.168.1.10', 5003)
Dec 01 15:33:29 raspberrypi hass[291]: 2018-12-01 15:33:29 INFO (MainThread) [mysensors.gateway_tcp] Waiting 10.0 secs before trying to connect again
Dec 01 15:33:39 raspberrypi hass[291]: 2018-12-01 15:33:39 INFO (MainThread) [mysensors.gateway_tcp] Trying to connect to ('192.168.1.10', 5003)
Dec 01 15:33:49 raspberrypi hass[291]: 2018-12-01 15:33:49 ERROR (MainThread) [mysensors.gateway_tcp] Connecting to socket timed out for ('192.168.1.10', 5003)
Dec 01 15:33:49 raspberrypi hass[291]: 2018-12-01 15:33:49 INFO (MainThread) [mysensors.gateway_tcp] Waiting 10.0 secs before trying to connect again
Dec 01 15:33:59 raspberrypi hass[291]: 2018-12-01 15:33:59 INFO (MainThread) [mysensors.gateway_tcp] Trying to connect to ('192.168.1.10', 5003)
Dec 01 15:34:09 raspberrypi hass[291]: 2018-12-01 15:34:09 ERROR (MainThread) [mysensors.gateway_tcp] Connecting to socket timed out for ('192.168.1.10', 5003)
Dec 01 15:34:09 raspberrypi hass[291]: 2018-12-01 15:34:09 INFO (MainThread) [mysensors.gateway_tcp] Waiting 10.0 secs before trying to connect again
Dec 01 15:34:19 raspberrypi hass[291]: 2018-12-01 15:34:19 INFO (MainThread) [mysensors.gateway_tcp] Trying to connect to ('192.168.1.10', 5003)
Dec 01 15:34:29 raspberrypi hass[291]: 2018-12-01 15:34:29 ERROR (MainThread) [mysensors.gateway_tcp] Connecting to socket timed out for ('192.168.1.10', 5003)
Dec 01 15:34:29 raspberrypi hass[291]: 2018-12-01 15:34:29 INFO (MainThread) [mysensors.gateway_tcp] Waiting 10.0 secs before trying to connect againi also checked the tcp port and found:
tcp 0 1 192.168.1.6:55916 192.168.1.10:5003 SYN_SENT 291/python3
which seems that it waits a respond from gateway in order to establish a connection
-
solved i just comment below line of my code:
//#define MY_CONTROLLER_IP_ADDRESS 192,168,1,6
//#define MY_MAC_ADDRESS 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED
and delete mysensors.pickle1 file .
thanks @mfalkvidd for your trial to support me.