How to adopt the Olimex POE board without wifi credentials

[Mariusthvdb (Marius)]

@bdraco

Thanks for the py-spys. How did you disable bluetooth?

same for the Bluetooth integration, via the integration panel.

not sure if I understand you correctly, but, the non BT profiles shouldn’t have any ESPhome traffic, as that was completely disabled.
I have the ESPhome add-on uninstalled completely, in both situations, so that couldn’t be it either.

@bdraco

Noticed regex compiles where happening over and over in your templates

I use those a bit yes, but should I be optimizing there? Any specific regex template Id be looking for? I use it in the frontend, and in the backend, so any suggestion you might have to go on would be appreciated.
The switch-off of the BT stuff though was most evident, and that is ofc including all regex templates I have elsewhere

O, btw, should I keep the protobuf-3.20.2-cp310-cp310-linux_x86_64.whl in my /config folder?

[bdraco (J. Nick Koston)]

@Mariusthvdb

not sure if I understand you correctly, but, the non BT profiles shouldn’t have any ESPhome traffic, as that was completely disabled.
I have the ESPhome add-on uninstalled completely, in both situations, so that couldn’t be it either.

There isn’t any esphome traffic in the non-bt ones. Sorry for the confusion. Its just that is was busier which was initially confusing.

[bdraco (J. Nick Koston)]

@Mariusthvdb

O, btw, should I keep the protobuf-3.20.2-cp310-cp310-linux_x86_64.whl in my /config folder?

You can delete this.

[Mariusthvdb (Marius)]

cool, thx.

[bdraco (J. Nick Koston)]

@Mariusthvdb

The switch-off of the BT stuff though was most evident, and that is ofc including all regex templates I have elsewhere

It would be good to get another non-BT profile set as it was likely just bad luck that it got taken at that time.

[Mariusthvdb (Marius)]

this really surprises me because at the time I made those, the processor was at 4-5%, so I believed it to be very calm…
but I asm already setting those up, and disabling the BT parts again, coming up!

[bdraco (J. Nick Koston)]

Maybe there is some confusion since the without bluetooth 300 svg had some aioesphomeapi calls in it

[Mariusthvdb (Marius)]

really odd, because when I search for esphome in the non-bt files 300.svg, I dont get a result, opposed to the BT 300.svg, which does show the purple result:

just to be sure, the NON BT files were taken before the BT files, so we can check that on the timestamp of the files…

[bdraco (J. Nick Koston)]

Looks like some type of problem (caching?) with dropbox. When I download them locally I don’t see the aioesphomeapi flame in the Without BT. Works fine when I copy them out.

[Mariusthvdb (Marius)]

side question: are Hue BT Bulbs supported on the new Bluetooth integration? My current already paired bulbs dont show up, but if yes, I would love test a few new bulbs I still have around!

[bdraco (J. Nick Koston)]

The bluetooth integration is only a framework for integration to build on. It doesn’t support any devices by itself. There isn’t a hue bluetooth integration in core, but I can’t say for sure if there isn’t a custom one.

[Mariusthvdb (Marius)]

right!
so, If I receive my Switchbot and Govee thermometers and VocoLinc door sensor, I first need to install their core bt integrations and then adapt?
good to know, I would have been hammering those buttons…

second No BT files shared. please check if this is what you need

[bdraco (J. Nick Koston)]

As soon as you enable the bluetooth adapters (via the bluetooth integration) or esphome, it enables bluetooth discovery which should trigger the discovery of those integrations.

[Mariusthvdb (Marius)]

and its back being busy, even more than before. Ofc, I now have 2 (…) devices connected, a Door sensor (the one from the release party VS1 by VOCOlinc, and a Switchbot thermometer WoSensorTH. No need to point where I added the integration and devices again:

[bdraco (J. Nick Koston)]

Thanks for the profiles. I’ve got some ideas on how to further improve the performance in 2022.10.x, and started a PR here https://github.com/home-assistant/core/pull/78545

[Mariusthvdb (Marius)]

@bdraco

Just be sure to remove it when home assistant switches over to the cpp version in the future.

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…

[Mariusthvdb (Marius)]

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:

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:

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

[Mariusthvdb (Marius)]

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

[sparkydave (🇦🇺 Dave)]

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…

[Mariusthvdb (Marius)]

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.