Sensor does not show up

ESPHome
3

Thanks,
yes api is there but it does not show new or there

Enable Home Assistant API

api:

image

4

Looks like api: is specified going on the logs - but the hash (#) symbol is not supported in device ids - if you create an entity with the name “Pit #1” in HA it will give it an id of pit_1. Maybe that is the issue.

5

Well I guess not. I thought it just automagicly showed uo

6

@zoogara
this one works but I will try without #configuration Thanks,
Grey

sensor:

  • platform: max6675
    name: “Meat Probe #2”
    cs_pin: GPIO13
    update_interval: 30s
    accuracy_decimals: 0

filters:

- sliding_window_moving_average:

window_size: 10

send_every: 10

#sensor:
  - platform: max6675
    name: "Meat Probe #1"
    cs_pin: GPIO15
    update_interval: 30s
7

Oh well - was worth a try. :slight_smile:

8

I am prone to make stupid mistakes, but I am not sure what I have done now.

Changed it to Pit 1 , still no findy

[18:52:20][D][max6675:046]: ‘Pit 1’: Got temperature=37.5°C
[18:52:20][D][sensor:124]: ‘Pit 1’: Sending state 37.50000 °C with 0 decimals of accuracy

9

Actually Tom is probably right (as usual) - looks like it’s not connected to HA via the API. Those lines in the log are the ESPhome API.

You should see something like:

[09:06:23][D][api:102]: Accepted 192.168.0.100
[09:06:23][D][api.connection:861]: Home Assistant 2022.7.5 (192.168.0.100): Connected successfully

After the Using noise encryption: NO line but before the sensors start updating. I can’t see that in your log.

10

I have seen what you are referencing in the past. But I do not see it anymore even on these sensors that are working.

I do appreciate your help so much, I really want this to work. What can I do to help you figure it out?\

I did add a new device today with the MQTT prefix home/ In the past everything was homeassitant/ I think. “Think” is bold.

Grey

19:09:29][C][dht:020]: Auto-detected model: DHT11
[19:09:29][C][dht:027]: Update Interval: 60.0s
[19:09:29][C][dht:029]: Temperature ‘Big Room Temperature’
[19:09:29][C][dht:029]: Device Class: ‘temperature’
[19:09:29][C][dht:029]: State Class: ‘measurement’
[19:09:29][C][dht:029]: Unit of Measurement: ‘°C’
[19:09:29][C][dht:029]: Accuracy Decimals: 1
[19:09:29][C][dht:030]: Humidity ‘Big Room Humidity’
[19:09:29][C][dht:030]: Device Class: ‘humidity’
[19:09:29][C][dht:030]: State Class: ‘measurement’
[19:09:29][C][dht:030]: Unit of Measurement: ‘%’
[19:09:29][C][dht:030]: Accuracy Decimals: 0
[19:09:29][C][captive_portal:088]: Captive Portal:
[19:09:29][C][mdns:084]: mDNS:
[19:09:29][C][mdns:085]: Hostname: bigroom
[19:09:29][C][ota:085]: Over-The-Air Updates:
[19:09:29][C][ota:086]: Address: 192.168.1.48:8266
[19:09:29][C][api:138]: API Server:
[19:09:29][C][api:139]: Address: 192.168.1.48:6053
[19:09:29][C][api:143]: Using noise encryption: NO
[19:09:40][D][dht:048]: Got Temperature=25.5°C Humidity=67.0%
[19:09:40][D][sensor:124]: ‘Big Room Temperature’: Sending state 25.50000 °C with 1 decimals of accuracy
[19:09:40][D][sensor:124]: ‘Big Room Humidity’: Sending state 67.00000 % with 0 decimals of accuracy
[19:10:40][D][dht:048]: Got Temperature=25.5°C Humidity=67.0%
[19:10:40][D][sensor:124]: ‘Big Room Temperature’: Sending state 25.50000 °C with 1 decimals of accuracy
[19:10:40][D][sensor:124]: ‘Big Room Humidity’: Sending state 67.00000 % with 0 decimals of accuracy

11

You will only see it in the startup logs. Not if you connect to the device after boot.

12

That is the wrong address for HA it should be 50 not 62?

[19:25:37][C][ota:085]: Over-The-Air Updates:
[19:25:37][C][ota:086]: Address: 192.168.1.62:8266
[19:25:37][C][ota:089]: Using Password.
[19:25:37][C][api:138]: API Server:
[19:25:37][C][api:139]: Address: 192.168.1.62:6053
[19:25:37][C][api:143]: Using noise encryption: NO
[19:25:40][D][max6675:046]: ‘Pit 1’: Got temperature=35.8°C
[19:25:40][D][sensor:124]: ‘Pit 1’: Sending state 35.75000 °C with 0 decimals of accuracy
[19:26:00][D][max6675:046]: ‘Pit 1’: Got temperature=35.8°C
[19:26:00][D][sensor:124]: ‘Pit 1’: Sending state 35.75000 °C with 0 decimals of accuracy
[19:26:20][D][max6675:046]: ‘Pit 1’: Got temperature=35.8°C
[19:26:20][D][sensor:124]: ‘Pit 1’: Sending state 35.75000 °C with 0 decimals of accuracy

13

No that’s just telling you the port the ESPhome API server is running on - on the device.

14

sorry yes, i reinstalled another one that is working and figured that out
What now?
Yes I no longer see the MQTT accepted anywhere.
I appreciate your help soo much
Grey

15

Post the whole config - not just the sensor. Maybe there is something we are missing.

16

you mean in espphome? I think the prob is deeper as I do not see that connect to HA anymore

esphome:
  name: pit2

esp8266:
  board: d1_mini


# Enable logging
logger:

# Enable Home Assistant API
api:

ota:
  password: "c7e9d7fe5d929c8a6e9b17767e228bbb"

wifi:
  ssid: "shop2"
  password: "xxxx"
  fast_connect: true
  manual_ip:
    static_ip: 192.168.1.62
    gateway: 192.168.1.1
    subnet: 255.255.255.0
    dns1: 192.168.1.1

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "M2 Fallback Hotspot"
    password: "mine0313"
    
# Example configuration entry
spi:
  miso_pin: D6
  clk_pin: D5

sensor:

  - platform: max6675
    name: "Pit 1"
    cs_pin: D7
    update_interval: 20s  
    accuracy_decimals: 0
#    filters:
 #     - sliding_window_moving_average:
#          window_size: 10
#          send_every:  10
      


captive_portal:
17

Looks pretty simple.

You are using a manual IP. Is anything else using that IP as well? What happens if you use DHCP? Ignore- ESPhome would have trouble connecting - doh!

Also it isn’t in the disabled device list? On the Devices and Services tab, Devices, top right filter menu.

Apart from that - maybe delete it completely and re-add.

18

Yes , I have already tried readd and it is not showing disabled.

I am going to restore last nights backup before I added the home/ mqtt topic

Grey

Well that did not help.

I am lost

19

aw geeze sorry I wasted so much of your time
thanks again
Grey

image

1 Like
20

Sometimes they show up automatically, you get a notification and then add the device to HA.

Sometimes (or if you are impatient like me) you need to add it manually per your last post.

1 Like
21

thanks for this, I just experienced the same issue, the process to add is :

  1. Copy encryption code or API of the device/node and memorize its ip address>>
  2. Go to Settings >>
  3. Devices and Services >>
  4. Click add integration (bottom of screen) >>
  5. Type “esphome” on the search >>
  6. Click esphome >>
  7. Enter ip address of device >>
  8. Enter port of node (6053 most of the time) >>
  9. A screen will pop up for encryption, paste the encryption obtained from the device
  10. You should now be able to see it
1 Like
22

If it would always be so easy. I am fiddling around to get my sprinkler to work, but the integration in homeassistant recognizes the esp node, I can add it and then I see only the device - but not any entities or sometimes only the entities created by my router fritzbox. If you need more details to help me, you’ll find them here yaml and logs (I just don’t want to make a complete double post).
I deleted esphome addon competely and also the integration in homeassistant and restarted. HA found the nodes immediately and I reconfigured them. Now one node works like a charm and the other with which I am having trouble a long time now only shows up with 1 entity.

Can this be related to the encryption keys?