All entities unavailable

[chemicalandy]

What happened?
I removed the HACS integration and installed the official version. However there are only 6 entities in this version and it would have been a lot of work to change my automations. I removed the official integration and re-downloaded the HACS version. The device was created correctly but all entities show as unavailable. (Some do have a history with readings after the re-installation)

To Reproduce
Repeated installation of the core integration. The entities in this were also unavailable (I don't know if this was the case the first time). Re-installed the HACS version and re-started Home Assistant, but all entities remain unavailble. Tried re-loading the integration several times.

Log Output
No logs that indicate a problem. There are several entries similar to this:
2025-01-29 14:53:59.130 DEBUG (MainThread) [homeassistant.components.ohme.coordinator] Finished fetching Ohme Charge Sessions data in 0.337 seconds (success: True)
2025-01-29 14:53:59.251 DEBUG (MainThread) [homeassistant.components.ohme.coordinator] Finished fetching Ohme Advanced Settings data in 0.627 seconds (success: True)

Home Assistant Version
2025.1.4

Integration Version
1.1.1

Update
Restored a backup to get it working again. Now back to version 1.1.0.

[wralb]

Don't know whether this experience is the same as for chemicalandy, however I thought I would share.

I also moved to the 'official' version then reverted to the HACS version pending Dan re-adding some features I use. I had had 1.1.1 prior to moving to 'official'.

I also found entities were unavailable on my dashboard and my automations didn't work after reverting from official to 1.1.1. The issue here was that the entity names retained the new format on reversion: e.g. where '...ohme...' is replaced with "...ohme_home_pro...". Updating the entity names in automations and dashboards allowed me to have 1.1.1 working again.

[dan-r]

This behaviour is likely to do with some changes that I made around 6 months ago. As @wralb mentioned, entity names now include the name of the charger rather than just ohme_, but if you'd configured the installation before that, you'd still have the old format.

I'd recommend giving the official release a go with 2025.2.0 when it comes out (or the beta is out now if you're feeling risky). The missing entites as of this version are:

• Sensors/Binary Sensors related to charge slots, although this information is available through a service call.
• Voltage reading - never really saw the point in this one
• Solar boost
• Preconditioning - working on this
• Price cap

I appreciate that this is disruptive and really appreciate your patience with this migration. If any of these are important to you, I'd appreciate raising an issue/feature request on the home-assistant/core repo, gives me something to work against.

[wralb]

Thanks @dan-r,

Appreciate all the effort on this integration and am happy to be patient as the migration takes place. I've adopted all the new entity names so swapping between the addon and core versions should be relatively quick now. I will try 2025.2 when released and look how the features matches; I'll needs and raise anything as appropriate. For info:

• Charge slot information is key to me and may be enough to allow me to stay on the core version
• Knowing what OHME believes the SOC of my Ariya to be is important as it can be compared with other sources of that information (e.g. your Nissan integration) to catch when one or the other feeds is not functioning correctly (as often happens).
• My charger is 200 ft from the house. It has an external WAP next to it and I use automations to lock and unlock the charger display and buttons according to whether my phone is associated to that WAP; so the ability to switch those features is a 'very nice to have' functionality in the core-version re-write.

[Gary-Manuel]

Hi Dan. Great work. Your efforts are appreciated.

Above you have posted a list of missing entities and in closed issue #105, you said that feature parity would eventually be reached. I have noticed that a number of controls are missing from the official integration but do not appear on your list of missing entities.

Could you confirm whether these controls are in the official integration but for some reason I have not migrated them properly, or whether they will be added later? The specific control I am looking for is “pause charge”.

Edit. I’ve managed to resolve this. I didn’t fully delete the addon before enabling the integration, which prevented full migration. I’ve now followed the migration instructions and it works ok. The method of charge pause has changed as pause is now a state of the charge mode entity, but I (and others) should be able to work it out. Query edited rather than deleted in case other have similar issue.

[dan-r]

@Gary-Manuel thanks for your comment, glad you've figured that out.

Also make sure you keep your home assistant updated, as there should be some new stuff in the next monthly release. (Sounds like you're already on 2025.2.x though so fine for now!)

[murkle]

@dan-r I'm trying to update to the new version, thanks for your efforts!

Is the new "energy" sensor the same as the old "session_energy" sensor?

sensor.ohme_session_energy -> sensor.ohme_home_pro_energy

Also will these keep the same names for use with PredBat (obviously with "ohme" changed to "ohme_home_pro")? (They don't seem to be available in the current version, right? I've got Home Assistant Core 2025.2.4)

binary_sensor.ohme_car_charging

binary_sensor.ohme_slot_active

[dan-r]

@murkle yup energy sensor is the same. All the binary sensors (charging, connected, online. No charge slot one yet) have been collapsed into one 'Status' sensor in the core version.

I intend to contribute proper support for this integration into predbat when I get the change, rather than the previous approach of emulating the Octopus integration. The slot info is already available through a service call, just not a sensor currently.

[springfall2008]

@murkle yup energy sensor is the same. All the binary sensors (charging, connected, online. No charge slot one yet) have been collapsed into one 'Status' sensor in the core version.

I intend to contribute proper support for this integration into predbat when I get the change, rather than the previous approach of emulating the Octopus integration. The slot info is already available through a service call, just not a sensor currently.

I'd like to support this in Predbat but as I don't have an Ohme I have no way to test/debug it, if you could keep the same format as the Octopus data in a sensor then everything will continue to work with Predbat. Or if someone can give me the exact service call needed and the exact data that is returned then I can try to add the support.

[Gary-Manuel]

@murkle yup energy sensor is the same. All the binary sensors (charging, connected, online. No charge slot one yet) have been collapsed into one 'Status' sensor in the core version.
I intend to contribute proper support for this integration into predbat when I get the change, rather than the previous approach of emulating the Octopus integration. The slot info is already available through a service call, just not a sensor currently.

I'd like to support this in Predbat but as I don't have an Ohme I have no way to test/debug it, if you could keep the same format as the Octopus data in a sensor then everything will continue to work with Predbat. Or if someone can give me the exact service call needed and the exact data that is returned then I can try to add the support.

Hi Trefor. Here are the available options for the sensor.ohme_home_pro_status and select.ohme_home_pro_charge_mode entities if this helps. There is nothing unusual about reading the sensor values or setting the select options.

Edit. Note that charge_mode returns unavailable until the charger is plugged in to the car.

[dan-r]

@springfall2008 thanks for your message. I believe the Home Assistant Core team are opposed to adding attributes etc the way its been done in the custom Ohme integration and the Octopus one.

@Gary-Manuel has given a good summary. The _status sensor effectively replaces all of the binary sensors from before as the values are mutually exclusive.

The service call list_charge_slots gives a list with the following items for each slot:
start: datetime.datetime
end: datetime.datetime
energy: float

I can add to these if you need any more data but I believe its all the same as before with attributes.

Its also hard for me to contribute - I've got the Ohme but no battery storage/solar, so I'd be relying on some of the users (I know @deanjesper was one of the initial users of Ohme/Predbat)