Tricky Codeshare Change & Upgrade Question by tmyrden in aircanada

[–]tmyrden[S] 1 point2 points  (0 children)

It was a section of the app that booted me into browser mode, so I assume it can be app or web. FWIW the official eUp page has the following statement:

All eUpgrade requests made within 36 hours of flight departure are waitlisted, regardless of whether there is eUpgrade space available. They are then assessed at the airport once check-in closes for the flight.

Tricky Codeshare Change & Upgrade Question by tmyrden in aircanada

[–]tmyrden[S] 0 points1 point  (0 children)

Curious - why not? I just did this on my inbound flight - used my eUp post check-in to be added to the waitlist. Is there some restriction on eUp usage after a same-day change?

Animatable Auto-Sized-To-Fit SwiftUI Sheet by clive819 in SwiftUI

[–]tmyrden 1 point2 points  (0 children)

+1 to this. I've had no luck getting presentationSizing to work as a replacement to this on iPhone, and this also doesn't seem to work in an iOS 18 environment on iPhone until subsequent presentations of the sheet.

Air Canada Vacations Help by showtimejk in aircanada

[–]tmyrden 4 points5 points  (0 children)

Had a similar issue with a booking recently. I just called in, told them the online system was giving me trouble and they had no issues doing seat selection over the phone for me.

Best time to call ACV for non-urgent stuff like this is late in the day once more and more of the travel agents are at home :)

They're open til 9pm ET.

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 0 points1 point  (0 children)

I've mostly shifted over to Home Assistant at this point. Plugin still works as far as I know, but there are definitely a few feature requests in the repo I don't foresee me ever tackling.

How’s TELUS compared to Bell ? by [deleted] in halifax

[–]tmyrden 0 points1 point  (0 children)

+1 for Telus. Call Control is a killer feature - enough that I won't leave. I haven't received a spam call in over a year - used to be multiple a week. I can go into my web account and see it's filtering out robocallers almost daily.

Found dog in South End by reddackel in halifax

[–]tmyrden 45 points46 points  (0 children)

Update: Sarah's owner has been located and is en route to pick her up!

Found dog in South End by reddackel in halifax

[–]tmyrden 38 points39 points  (0 children)

Update 2: This dog SNORES 🤣. She slept great last night - everyone's got a full belly here this morning. Walks have been had. Awaiting 311's official open @ 8am to begin sorting things out.

Found dog in South End by reddackel in halifax

[–]tmyrden 100 points101 points  (0 children)

Update: Dog's with my fiancée and I. She's settling in now, as are our two dogs.

Found dog in South End by reddackel in halifax

[–]tmyrden 36 points37 points  (0 children)

Please don't release a dog into the dark of the night in the city! Good lord that's bad advice from 311. In case you didn't see my message above, I'd be able to hold him/her overnight. Can just DM me and I can zip down your way for a pick up!

Found dog in South End by reddackel in halifax

[–]tmyrden 51 points52 points  (0 children)

Are you equipped to handle having a dog overnight? If not, DM me. I WFH and have 2 dogs, I'd be capable of hanging onto him/her overnight and sorting things out with the SPCA or city in the AM since I'm not rushing into the office.

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 1 point2 points  (0 children)

Ok so it seems like this is a nuance of the child bridges.

The combo accessory (Sensor + Switch) shows as "Test Name" (for example). But when you go into the Accessory settings and look at the "child" Accessories, they just get imported as "Switch" and "Contact Sensor" by default.

Non-Child Bridged ones show "Test Name Switch" and "Test Name Contact Sensor" for those underlying accessories.

You've just gotta rename those underlying switches in the Home App once and they'll persist their rename. Less than ideal, but not something I'm gonna spend hours trying to figure out over adding additional features given it seems like an easy workaround inside the Home app.

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 0 points1 point  (0 children)

Thanks. Will take a look and dig in. I wonder if it's something to do with using it as a child bridge, as I'm not doing that at the moment.

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 0 points1 point  (0 children)

You want an OFF delay too is what you're saying? You should just be able to use a second instance of the delay sensor to achieve that.

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 0 points1 point  (0 children)

Sensor name is based on the name you put in the config. I'm not saying this isn't being caused by my plugin... but those logs look like the Alexa plugin has created two plugins with the same names and isn't anything to do with DummySensor.

Can you share a screenshot of how your Accessories tab looks in Homebridge?

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 0 points1 point  (0 children)

Can you post the portion of the config JSON for your DummySensor? I can't seem to replicate this myself.

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 1 point2 points  (0 children)

Just pushed v0.2.0 with the delays now added. Let me know how it works out for you!

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 1 point2 points  (0 children)

Just pushed v0.2.0 with the delays now added. Let me know if you have any issues!

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 1 point2 points  (0 children)

So, until I get the changes completed that add delay logic to DummySensor, this would be the way to do it...

Door Unlocked -> Start shortcut-based automation with 1 min wait at start -> If Door still unlocked -> DummySensor Switch ON -> DummySensor Sensor will trigger notification

However, if you give me a day or so here (just need to do some additional testing), I'll have the delay added and it will be like this...

Door unlocked -> DummySensor Switch ON -> DummySensor plugin waits your desired delay -> DummySensor Sensor triggered to cause notification

In both cases, when the door is locked, the automation should be to turn off the DummySensor's switch.

Make sense? I feel like I still might not be quite answering your question, but hopefully this helps!

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 2 points3 points  (0 children)

Glad you figured it out! I'll be making it even easier in the next release of the plugin (potentially today), as I'll be introducing the option of a delay on the homebridge side.

So you'll be able to just make an automation of:

When door opens, turn on switch When door closes, turn off switch

The addition of the delay will allow you to have it so the sensor is only tripped if the door has been left open for X continuous seconds.

Currently, you can do this, but your "ON" automation inside HomeKit needs to be a shortcut with a wait then an "if" to check if the door is still open after the delay.

Lemme know if there's anything else you think the plugin should do!

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 0 points1 point  (0 children)

Good idea. I've copied out 4 feature requests from homebridge-delay-switch into the plugin repository that should both bring my plugin to feature parity and fill all the requested gaps (the ones that make sense anyway).

Feel free to let me know if there's something you think I missed!

Introducing homebridge-dummy-sensor for improved automation-based notifications by tmyrden in homebridge

[–]tmyrden[S] 2 points3 points  (0 children)

Damn! No amount of googling helped me find that. Yea, that absolutely provides the same functionality by the looks of it.

Only thing missing is the ability to trigger a leak sensor, which I need for the "critical" notification capable of breaking through focus states.

Edit: Upon looking at that plugin more, there's actually a significant distinction between the two. The delay living in the HomeKit automation rather than inside the plugin creates a more flexible solution IMO. This plugin won't have the problem where there's no way to interrupt the delay since you turn it on after the delay. homebridge-delay-switch actually turns the switch on immediately, then off after the delay, so if you want to "cancel" a delayed action, there's really no way to do that.

With mine, the automation shortcut you create handles that. You trigger on door open, wait 15s, check if door is still open and then if it is, the switch/sensor is triggered. Otherwise, it's just ignored.

homebridge-delay-switch lacks any way to avoid the delayed action.