esphome run file.yaml --device 192.168.x.yMe too, I have several esp32-S2lolin in remote internet address but ota and even api (initial version now I moved to MQTT ) and all working fine!
I'm not saying it's rocket science. Many people do NOT have the problems I had.
IIRC @Sleeper85 or @MrPablo said that logging on the webserver is quite resource intensive and it would be enough to crash the ESP32.
esphome:
name: ${name}
platformio_options:
build_flags:
- -DCONFIG_ARDUINO_LOOP_STACK_SIZE=32768It just dawned on me, May I ask what framework is everyone using? We recommend the esp-idf framework due to its stability.
I also said the same. Basically, new users should use DEBUG logging initially to debug UART or CAN pin issues. Once, everything is up and running they should return to a reasonable and lower log value.
It could be logging being set to DEBUG causing the esphome to crash.
esphome logs XXX.yamlminicom --device /dev/ttyUSB0 -C my-log-name.txtpu addcarreturn YesWell you can say it's "my problem", fair enough. It doesn't really help.
There were several posts of GitHub issue tracker of ESPHome as well as some Home Assistant Forum Posts.
, your network configuration is unnecessarily complicated.
This seems to be router dependant and how well or how badly its firmware is programmed, in the UK the BT Smarthub router just cannot handle a SSID shared between frequencies and the first job on receipt of the router is to separate into 2 SSID's. The Smarthub is in its 5th Generation and still not fixed.
As I said I know it's not optimalIt's true that it doesn't help
An OPNsense router, several Rock 5Bs also acting as router and AP, it's complex and not how to build a good network (I work in this field).
You can create a multi-LAN network including a WiFi AP (with hostapd) with a single mini-PC server equipped with a WiFi card and two LAN ports.
You install Proxmox VE on the mini-PC, a dedicated Ethernet port for the WAN, a bridge for the LAN with an Ethernet Port and the WiFi card.
Then you install an OPNsense VM, OPNsense should be your only router, the ISP router is bridged to the OPNsense WAN port.
Then if you want to create VLANs you pass it through the uplink between the OPNsense LAN port and your switch supporting VLANs. No need to play with static routes OPNsense knows the different networks and takes care of routing the traffic.
This is how a corporate network is created (except for the mini-PC and the WiFi AP part of course), there is never more than a single router-firewall through which all traffic passes.
. . Sometimes I wish I would have chosen IT and not Electrical Engineering as my Profession .auto vmbr0
iface vmbr0 inet static
address 192.168.2.13/20
gateway 192.168.1.1
bridge-ports enp9s0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094iface vmbr0 inet static
address 192.168.2.13/20
gateway 192.168.1.1
bridge-ports enp9s0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 1 150-159 160-169 ...
net1: virtio=XX:XX:XX:XX:XX:XX,bridge=vmbr0,firewall=1,tag=1,trunks=2-4094Are we saying the Atom Lite S3 might not work with a 5G network as this is what the current ESP32 dev chips are using?It's true that it doesn't help
An OPNsense router, several Rock 5Bs also acting as router and AP, it's complex and not how to build a good network (I work in this field).
You can create a multi-LAN network including a WiFi AP (with hostapd) with a single mini-PC server equipped with a WiFi card and two LAN ports.
You install Proxmox VE on the mini-PC, a dedicated Ethernet port for the WAN, a bridge for the LAN with an Ethernet Port and the WiFi card.
Then you install an OPNsense VM, OPNsense should be your only router, the ISP router is bridged to the OPNsense WAN port.
Then if you want to create VLANs you pass it through the uplink between the OPNsense LAN port and your switch supporting VLANs. No need to play with static routes OPNsense knows the different networks and takes care of routing the traffic.
This is how a corporate network is created (except for the mini-PC and the WiFi AP part of course), there is never more than a single router-firewall through which all traffic passes.
And Amen to that - @silverstone looks like somebody who likes complexity... I was following his setup - at some point, he completely lost me.It's true that it doesn't help
An OPNsense router, several Rock 5Bs also acting as router and AP, it's complex and not how to build a good network (I work in this field).
You can create a multi-LAN network including a WiFi AP (with hostapd) with a single mini-PC server equipped with a WiFi card and two LAN ports.
You install Proxmox VE on the mini-PC, a dedicated Ethernet port for the WAN, a bridge for the LAN with an Ethernet Port and the WiFi card.
Then you install an OPNsense VM, OPNsense should be your only router, the ISP router is bridged to the OPNsense WAN port.
Then if you want to create VLANs you pass it through the uplink between the OPNsense LAN port and your switch supporting VLANs. No need to play with static routes OPNsense knows the different networks and takes care of routing the traffic.
This is how a corporate network is created (except for the mini-PC and the WiFi AP part of course), there is never more than a single router-firewall through which all traffic passes.
The Static Route is more of a "Hack" since I'm not using VLANs.
Wrong. The system works. The MONITORING is just not accessible in real time if something is down. And OTA was broken.And Amen to that - @silverstone looks like somebody who likes complexity... I was following his setup - at some point, he completely lost me.
it just seems there are a lot of dependencies for his Solar system to function and if one component breaks the system is down.
I like to keep the system as simple and as independent as possible - so that a few years down the line after taking a long break from the project I won't have too much to re-learn when management is required or when the system needs attention...
ThanksThe Static Route is more of a "Hack" since I'm not using VLANs.
Why do you have 2 routers in your case ?
The best ? Depends if you want isolation/firewall/access control/NAT/etc between the devices or not.
The easiest would probably be to have a single router 192.168.0.0/22 which would be 192.168.0.0-192.168.3.254
IP Calculator / IP Subnetting
jodies.de
As @Sleeper85 said Static Routes are NOT the proper way. it's more of a stop-gap measure until I fix everything VLAN related (needs setup on software level, switch configuration, managed switches, etc).
In your case, if the routers have 1 extra wired interface available, you could use ONE extra port on each where the "WAN" side of Router 1 is connected to the "LAN" side of Router 2 and viceversa.
So for Device 1 it would look:
192.168.1.x Device 1 -> 192.168.1.1 Router [LAN] -> 192.168.0.100 [WAN] -> 192.168.0.1 [LAN] -> 192.168.0.x Device 2
And for Device 2 it would look:
192.168.0.x Device 2 -> 192.168.0.1 Router [LAN] -> 192.168.1.100 [WAN] -> 192.168.1.1 [LAN] -> 192.168.1.x Device 1
WAN and LAN are just some labels. In this specific case they should rather be "LAN1" and "LAN2" but you get the idea.
So in one direction Router 1 is the Gateway of Router 2. In the other direction Router 2 is the Gateway of Router 1.
Make sure you understand the differences between and the different aspects of networking:
