How to adopt the Olimex POE board without wifi credentials

ESPHome
41

will this be announced? I just noticed upon updating to 2022.8.5 that HA rebuilt the wheel.Would be good to know when this will be merged into core HA.

This error originated from a custom integration.

Logger: custom_components.fast_protobuf
Source: custom_components/fast_protobuf/__init__.py:35 
Integration: Fast protobuf 
First occurred: 07:53:48 (1 occurrences) 
Last logged: 07:53:48

Building protobuf 3.20.2 cpp version in the background, this will be cpu intensive

and shortly after that auto restarted:

This error originated from a custom integration.

Logger: custom_components.fast_protobuf
Source: custom_components/fast_protobuf/__init__.py:100 
Integration: Fast protobuf 
First occurred: 08:03:30 (1 occurrences) 
Last logged: 08:03:30

Restart Home Assistant to use the new wheel

hadnā€™t even noticed tbhā€¦

42

to update this on the original request:

Ive once more installed afresh. deleted the yaml files, and also the files in .storage, so it wouldnā€™t read those from that.

Esphome add-on installed and fired up, that immediately ā€˜discoversā€™ my 2 Olimex boards:

Schermafbeelding 2022-09-20 om 15.02.44
Schermafbeelding 2022-09-20 om 15.02.442032Ɨ534 41.6 KB

doing nothing in the UI, but uploading the (supposedly) correct yaml files for those, both with a static IP address in the ethernet: key, that panel changes to:

Schermafbeelding 2022-09-20 om 15.21.19
Schermafbeelding 2022-09-20 om 15.21.191968Ɨ528 37.1 KB

Ill leave out at that for now, because anything I do in the UI next will lead to the previously displayed panels above.

43

new issue in ESPHome: Can not adopt Olimex POE BT proxy in ESPhome Ā· Issue #320 Ā· esphome/dashboard Ā· GitHub

44

I am trying to get one of these boards (Olimex PoE) configured and canā€™t seem to get even a base config flashed to it. (trying to flash with ESPhome-flasher)

Code:

esphome:
  name: retic-controller-poe

esp32:
  board: esp32-poe-iso
  framework:
    type: arduino

logger:

web_server:
  port: 80

api:

ota:
  password: !secret ota_password

ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO17_OUT
  phy_addr: 0
  power_pin: GPIO12

Error:
Unexpected error: The firmware binary is invalid (magic byte=FF, should be E9)

Iā€™m sure Iā€™ve had this error in the past and got around it with using a different board type in the config, but Iā€™ve tried everything I can find on the net for this board and none want to work.

Any tips?

EDIT: I tried flashing it by connection directly to my HA server rather than my laptop and that workedā€¦

45

I finally worked it out tbh, though the initial flashing from ESPHome Bluetooth Proxy worked ok, connected to the usb of my Mac running Chrome.

after that, a device will be registered in the Esphome integration under its default name. And then the trouble started in my settingā€¦ renaming the device to something nicer and trying to adopt it in the Add-on Esphome dashboard was a nightmare.

Until I found out that after renaming the device (in Dashboard), we have to delete the device in the integration panel, to have it rediscovered under its new name.

And then they start working ok, also with the active Bt connection now.

all a bit unintuitive really, and hope they will sort that.