M5Stack PoE Camera board configuration #2
-
|
Hiya, and thanks for all your work so far with this! I'm currently looking at how to have this flashed to the M5Stack PoE Camera which uses the W5500 for ethernet. Supporting one of the other devices, such as with an IP101, I would need to add something like this to the ESPHome yaml: Aside from adding what's in the README, is there anything else that needs to go under the ethernet section? Unfortunately I'm just waiting for the flasher to arrive so hoping to get things lined up in advance so when it does I can be ready to go :) |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 15 replies
-
|
Currently not to add more than what's in the readme. It still lacks lot of the features which are provided by the stock ethernet component. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the prompt response there! I'm unsure about how that'll work with this one as they seem to have removed all WiFi. I'll give that a whirl once the flasher unit arrives in a few days. Thankyou again for all your effort with this support library :) |
Beta Was this translation helpful? Give feedback.
-
|
Flasher arrived. Can flash firmware to it by using "Legacy" option in ESPHome. However I'm unsure about generating the configuration? My config is: The only difference is I've got: In my ESPoE32 config and it builds fine. However if I try to specify w5500 here it complains and says that it's not valid: Have I missed something? |
Beta Was this translation helpful? Give feedback.
-
|
At least two things are wrong. For this component you need the component Also this component requires framework esp32:
framework:
type: esp-idfIm not sure about how far backward compatible it is... so maybe you need at least release 4.x.x of esp-idf. An example for this is also in the readme. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for that advice. Made some really good progress! Got it built and flashed: Pinout was slightly different for me, but it was seemingly well enough documented here: Removed the WiFi section given the unit doesn't have it: However when I flashed the unit over the Type-C USB Downloader device, it powered up and immediately said that the Ethernet link was up for two seconds. It was only 5 seconds later that I actually plugged in the ethernet: I had to remove the version-specific stuff because ESPHome got annoyed that I was doing it from x86_64 (instead of ARM?) and wouldn't compile. Newer versions didn't have that issue as soon as the esp-idf version pin was removed. Checked in my routers DHCP logs and nothing from that MAC address, 24:d7:eb:38:ac:17 If you're OK to continue to assist troubleshooting, I'd be most grateful for any further help 😊 |
Beta Was this translation helpful? Give feedback.
-
|
Can you give me the full output and corresponding config yaml (if possible the full without keys and passwords) from the failing compile with the pinned version. |
Beta Was this translation helpful? Give feedback.
-
|
can't reproduce that even without cable. |
Beta Was this translation helpful? Give feedback.
-
|
Definitely soldered correctly, I've pulled the unit apart to check. There's nothing else attached to it, not trying to get external sensor data etc for now, just wanting to get it on to HomeAssistant to begin with. So on a cold boot with JUST the USB Type-C cable attached, with no ethernet at all, this is what I get:
Which is interesting given there's no cable at all... Definitely looks OK solder-wise on the unit to me: All the lights etc for link / activity light up when the cable is plugged in. Tried 3x different cables, on different switch ports too, just in case. The cables work just fine on the 2x PoESP32's units that I have here though. I have a Ubiquiti switch that I can control the link speed so I tried forcing it to 100mbps full duplex, and still no change. Removed the "network:" from the config too, no change. Based on seeing this in the logs though: Is it possible that I've got the Reset or IRQ pings wrong? Could I trouble you to have a look for me herem please, and see if you'd change any of them? |
Beta Was this translation helpful? Give feedback.
-
|
Sure as it is stock connected it will be good. regarding pins... looks good to me except the pin 37 seems to be a button not an interrupt pin. But maybe your board acts differently. In my test it worked or didn't work at all, but had never such strange effects with link up and down. |
Beta Was this translation helpful? Give feedback.
-
|
regarding m5stack example code (https://github.com/m5stack/PoE_CAM/blob/ba350fa86cb3ef9e084145868d813a3137ef598b/src/utility/w5500_image.cpp#L303) it looks like at least SPI part seams to be correct. But couldn't find anything related to the interrupt pin. |
Beta Was this translation helpful? Give feedback.
-
|
Brilliant, at least changing the Unfortunately, nothing still showed up in my DHCP logs, however this was with the network cable plugged in from the outset: Interesting. OK. Alright so back to Are the additional logs from that last failed flash helpful? |
Beta Was this translation helpful? Give feedback.
-
|
36 is definitly wrong... regarding the schematic this is already used on the esp32 chip itself (SENSOR_VP) which is something from the cam. I meant 36 on the W5500 chip... which is not the same. But regarding the schematics this seems to be not connected... |
Beta Was this translation helpful? Give feedback.
-
|
I'm picking this up from here because I have the exact same hardware, and similar need (esphome on a POE camera board). I have the WiFi version FWIW. Using the configuration mentioned above, I'm getting a boot loop. Using the pin 1 for interrupt. Thoughts on how we can test the interrupt-less case? |
Beta Was this translation helpful? Give feedback.
Currently not to add more than what's in the readme. It still lacks lot of the features which are provided by the stock ethernet component.
You can't currently configure anything. It just uses the calculated Mac address of the esp, usually +2 of the wifi address. It currently only works with dhcp for setting the IP address.
And I think I missed to provide the connected state back to esphome. I found some components that only start with a wifi or Ethernet connection don't start. A workaround currently is to "hack" the specific component, or let wifi run in parallel.
As soon I get the time, I will work more on this stuff to get the same feature level as the stock ethernet component. But can…