No LAN connection ESP8266 gateway
-
@Bramz see section #1:1 in https://forum.mysensors.org/topic/666/read-this-first-it-could-save-you-a-lot-of-time on how to enable debug logging. After that, please post the serial output here.
@mfalkvidd Thanks for your suggestion. I was under the impression that the com port could only be used for one thing at a time: either flashing or monitoring, but apparently this combination is possible. Anyway, I followed the instruction but unfortunately the serial monitor remains completely blank.
-
@mfalkvidd I am not entirely sure what is meant by an ESP framework, but if it refers to the URL which is given in the <Preferences> section of the Arduino IDE under <More Board manager URL's> than this might be the problem.
I am now using https://arduino.esp8266.com/stable/package_esp8266com_index.json which leads to a version 3.0.2.
What URL should I use for a version 2.6.2 ? Than I will give that a try. -
@mfalkvidd I am not entirely sure what is meant by an ESP framework, but if it refers to the URL which is given in the <Preferences> section of the Arduino IDE under <More Board manager URL's> than this might be the problem.
I am now using https://arduino.esp8266.com/stable/package_esp8266com_index.json which leads to a version 3.0.2.
What URL should I use for a version 2.6.2 ? Than I will give that a try. -
@mfalkvidd @electrik Yes! This did the trick for me. Thanks for your guidance.
Probably the instruction to use a version not higher than 2.6.2 has been given somewhere/sometime and I have overlooked it.
The serial monitor remained blank during upload, but when I select 9600 baud and press the reset-button it gives what I think is a healthy response:⸮⸮5R⸮⸮64 MCO:BGN:INIT GW,CP=RNNGE---,FQ=80,REL=255,VER=2.3.2 121 TSF:LRT:OK 137 TSM:INIT 151 TSF:WUR:MS=0 174 TSM:INIT:TSP OK scandone state: 0 -> 2 (b0) state: 2 -> 3 (0) state: 3 -> 5 (10) add 0 aid 3 cnt connected with XXX, channel 6 dhcp client start... ip:192.168.178.46,mask:255.255.255.0,gw:192.168.178.1 403 TSM:INIT:GW MODE 426 TSM:READY:ID=0,PAR=0,DIS=0 458 MCO:REG:NOT NEEDED ip:192.168.178.4,mask:255.255.255.0,gw:192.168.178.1 1544 GWT:TIN:CONNECTING... 2573 GWT:TIN:CONNECTING... scandone 3601 GWT:TIN:CONNECTING... 3629 GWT:TIN:IP: 192.168.178.4 3662 MCO:BGN:STP 3680 MCO:BGN:INIT OK,TSP=1 3708 TSM:READY:NWD REQ 3735 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: pm open,type:2 0And sure enough, the LAN has detected an ESP device at 192.168.178.4 now.
Secretly, I was hoping that connection to Domoticz would now also work but unfortunately I keep on getting the persistent message:
2022-11-25 11:54:58.598 Error: MySensorsGateway: Can not connect to: 192.168.178.4:5003However, that probably needs to be adressed in a different topic.
-
@Bramz I'm fairly new to MySensors. As it is supported by volunteers, like you and me and @mfalkvidd, some code doesn't get updated when there's a version change, the code update often happens when someone notices that the code needs to be updated. I suspect that this is the case here.
I'd be glad to help out, but not knowing the in's and out's of things, I can pretty much only verify code for which I have hardware.
OSD
@OldSurferDude Hope this worked for you too.
-
When I saw 2.6.2 I was thinking the MySensors Library (2.3.2)! It never occurred to me it was the board manager.
So, yes! it works for me. :)
I just checked to see if Domoticz has an MQTT interface and it appears that it does. @Bramz, look into that. Once you have that, then it may be easy to connect other devices, like Tasmota devices, to Domoticz. MQTT requires an always-on computer connected to your network.
I have a headless (needs dummy monitor plug or 3x 75Ω resistors to boot), refurbished computer on which I run Linux OS, then both MQTT and Home Assistant running in Virtual Box.
Thanks everyone!
OSD
-
When I saw 2.6.2 I was thinking the MySensors Library (2.3.2)! It never occurred to me it was the board manager.
So, yes! it works for me. :)
I just checked to see if Domoticz has an MQTT interface and it appears that it does. @Bramz, look into that. Once you have that, then it may be easy to connect other devices, like Tasmota devices, to Domoticz. MQTT requires an always-on computer connected to your network.
I have a headless (needs dummy monitor plug or 3x 75Ω resistors to boot), refurbished computer on which I run Linux OS, then both MQTT and Home Assistant running in Virtual Box.
Thanks everyone!
OSD
Still, there seems to be 'someting rotten in the state of Network' where my LAN is concerned. Although the Arduino serial monitor says:
13:03:55.821 -> connected with XXX, channel 6 13:03:55.868 -> ip:192.168.178.4,mask:255.255.255.0,gw:192.168.178.1 13:03:55.915 -> ip:192.168.178.4,mask:255.255.255.0,gw:192.168.178.1 13:04:04.826 -> pm open,type:2 0when I ping the IP-address I get:
Pinging 192.168.178.4 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.178.4: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),When I use the tool 'Wireless Network Watcher' I do see that a device is connected at 192.168.178.4 with the correct MAC address.
However, when I look at the management page of my FritzBox 7490 modem/router no device is mentioned at 192.168.178.4.I remain at a loss here.
