Occupancy for Ecobee Sensor not being displayed

[jcat2]

The problem

I have a home with two Ecobee Thermostats (first and second floor) with each having their own remote sensors (Office and Master Bedroom respectively). I was able to get my Ecobee account set up on Home Assistant but only the Temperature for my Master Bedroom remote sensor shows up in the entries and there is no occupancy. When I go to the remote sensor it is also missing the occupancy sensor. When I log in to my Ecobee account on Ecobee I can see the sensor and the occupancy as well as temperature status. Any ideas as to why the occupancy status isn't showing up for this one remote sensor?

What version of Home Assistant Core has the issue?

core-2023.11.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Ecobee

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ecobee

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @marthoc, @marcolivierarsenault, mind taking a look at this issue as it has been labeled with an integration (ecobee) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `ecobee` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign ecobee` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

ecobee documentation ecobee source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[pfeezzy]

I have this issue too. I have 6 remote sensors but only four of them are showing the occupancy entity but all 6 show the temperature. Browsing my all my entities I notice two entities (binary_sensor.occupancy and binary_sensor.occupancy_2) that are greyed out. When I open the entities and click the gear icon, it says they don't have a unique ID. When I click on the vertical ellipsis>related, it shows it is related to ecobee. As of this posting, I am running all the latest versions of HA.

Core 2024.3.0

Supervisor 2024.03.0

Operating System 12.1

Frontend 20240306.0

[altz06]

I have the same issue, in a scenario involving 3 remote sensors + the main thermostat. One of the (3) remote sensors sends temperature data to Home Assistant, but not occupancy status. Within the Ecobee iOS mobile app though, the one sensor in question does properly display occupancy status.

Core 2024.3.0

Supervisor 2024.03.0

Operating System 12.0

Frontend 20240306.0

[bjpetit]

I haven't seen this on my setup. But doing some quick code inspection of the binary_sensor code, the use of rstrip() in init is going to be problematic. If rstrip acts on a string, later checks against the source string will fail, causing the sensor to not show up.

self.sensor_name = sensor_name.rstrip()

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.