2.0 Release Update

Hi Jim,
Not to bump this, but ran into your suggestion here, which I thought isn’t correct 100%.

this would need the service: notify.ios_notifier, which is indeed using the group notification platform, combining multiple notify platforms into a single service.

for each platform after the notify. you would need a configured platform and name in your config.

notify.notify doesn’t need this, and simply sends the message to all devices with the HA app. It’s a broadcast service in the broadest sense :wink:

it does so without the need for configuring anything.

Hi there - thank you for the great work .

Three questions around the 2.0 app:

  • when do we expect it to be uploaded onto the app store (not test flight)? I’m anxious to get my other family members on it !
  • I noticed many new sensors created from the integration (i.e., sensor.distance). however, i think they may want to be prefaced with the device name (i.e., sensor.andrew_ios_distance) to avoid confusion when multiple 2.0 apps are integrated with the same server
  • I did not see a sensor for bluetooth connection. That would be super helpful in terms of identifying when someone is connected to the car. For example, I could turn the heat on the house when I begin my drive home from work. Not sure if possible but wanted to share the idea!

Thank you again - amazing work on this project.

With regards to the Bluetooth thing, you can already do that: crate an input boolean and expose it to HomeKit as a switch. Next, Setup a shortcut in iOS that toggles the Switch in HomeKit based on the BT device you’re connected to.

To be honest. I don’t think we will get app via the App Store. It was already submitted mid of the year but somehow declined by Apple.

Incorrect. See state of the Union by Balloob last week. They believe apple approval and release this week.

Having a prefix for these sensors would indeed be nice.

Just updated to the new 69 release. Has anyone managed to get their Siri shortcuts working with this release? I know there is a change with this release but cannot seem to get anything to work.

I’ve got a shortcut set up to disarm my security when I get home. Seems to work.
For call service actions, make sure you’re entering the data in the form of {“entity_id”:“switch.your_entity”}

Render template ones are formated exactly like you would with templates in yaml.

I use automations to trigger IR commands on my sat box to change channels, I used to be able to trigger these from the previous beta but I cannot find a way to get them to trigger with the new update.

Do you mean the ones you set up under Siri in the app before? It’s setup in Shortcuts app now, or at least that’s how I did it.
Create a shortcut, use Home Assistant --> call service as the action. Use automation.trigger as the call service and enter your automation id in data using {“entity_id”:“automation.your_entity”}

Trying to do that but not having much success at this time. Will keep trying.

Is it failing when running it, or at some other point?

I get this

Bingo! Got it working now using what you suggested. Had to correct the " from “ in your reply but it’s working on my test shortcut. Just need to fix all the rest before I update my phone. Testing using my iPad currently.

Cheers for your help.

Sorry, didn’t realise I’d entered in the wrong ". So used to having them work automatically that I didn’t check.

I spotted it as soon as it failed when trying to run it.

Phone now updated and working as before :grinning:

11 Likes

Out soon.

4 Likes

Available very soon in an App Store near you! Check out the beautiful new documentation site at https://companion.home-assistant.io too. It will answer many of your burning questions.

I’m locking this thread now. Feel free to create new ones!

23 Likes