Entities not available after update?!

[phillie05 (Phillip)]

Anyone having an issue with the latest update with Home Assistant? I updated and suddenly a couple of enitites are no longer available.

[WarLion]

@phillie05

nyone having an issue with the latest update with Home Assistant? I updated and suddenly a couple of enitites are no longer availa

like what entities ?

[phillie05 (Phillip)]

Not sure what happened here?! It was working perfectly before the update.

[WarLion]

is your esphome avalible ?

try to log your esphome device with esphome builder

[phillie05 (Phillip)]

It’s logging weight so it’s working there…
I put a 20lb test weight on it.

[WarLion]

go to
http://homeassistant.local:8123/config/integrations/integration/esphome

and check the keg scale one

in some point did you change the entity name?

[phillie05 (Phillip)]

Not that I recall.
Should this be “keg-scale-one” instead of “Keg Scale One”?

[WarLion]

what happend if you access you device , dont change the name just go inside

like this

[phillie05 (Phillip)]

Looks like this…

[WarLion]

ok delete the device and it will be auto discover again

if is not auto discover add it manually with the ip from the log i believe it was 192.168.1.154

[phillie05 (Phillip)]

Okay; deleted and added back…

[WarLion]

did you get your entities back?

[phillie05 (Phillip)]

All but the Keg Level are working now.

[WarLion]

on esphome builder validate your device to check if the upgrade cause something

also are those devices unavailable sensors need data to show information?

[phillie05 (Phillip)]

It validates fine. My template.yaml file looks like this…

That seems to validate fine as well. My config file looks like this…

Typically in web coding like php a !include would mean not to include that file not sure if the same holds true in yaml though and I didn’t edit this file it was working fine pior to the update.

[WarLion]

can you share you esphome code to see maybe theres something there that its not reading your template devices

[phillie05 (Phillip)]

esphome:
  name: keg-scale-one
  friendly_name: Keg Scale One
  on_boot:
    then:
    - switch.turn_off: keg_scale_one_low
    - switch.turn_off: keg_scale_one_medium
    - switch.turn_off: keg_scale_one_high
  

esp8266:
  board: d1_mini
  framework:
    version: dev

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: "IpnZwQ+EDjvMflgGvRR8ZDUWQ5r9MYgmsgl89r3qBrU="

ota:
  - platform: esphome
    password: "08233bd6ce2722e8191d95d09e175278"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  manual_ip:
   static_ip: 192.168.1.154
   gateway: 192.168.1.1
   subnet: 255.255.255.0

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Keg-Scale-One Fallback Hotspot"
    password: "uzxu1W9crhpg"

captive_portal:
    
sensor:
  - platform: hx711
    name: "HX711 Value"
    dout_pin: D3
    clk_pin: D2
    gain: 128
    update_interval: 5s
    filters:
      - calibrate_linear:
         - 98303 -> 0
         - -108545 -> 20
    unit_of_measurement: lb

switch:
  - platform: gpio
    name: "Low"
    id: keg_scale_one_low
    pin: D5
    inverted: true

    
  - platform: gpio
    name: "Medium"
    id: keg_scale_one_medium
    pin: D6
    inverted: true

    
  - platform: gpio
    name: "High"
    id: keg_scale_one_high
    pin: D7
    inverted: true

[phillie05 (Phillip)]

Here’s a question; would the ip address of a similar device be different? I’m trying to setup another scale and I’m getting this error on logs…

[tom_l]

@phillie05

with the latest update with Home Assistant?

Core or OS update?

And “latest” isn’t a version. Please be specific and provide the version number.

[tom_l]

@phillie05

would the ip address of a similar device be different?

Each device has to have a unique IP address. If you copied the config and did not change this then you are going to have a bad time. You will need to do use the “use_address” option to correct this.

https://esphome.io/components/wifi.html#configuration-variables