Planned Workouts in ORM

[DXCanas]

Hey all,

I see that the docs mention planned workouts via MQTT; is this the only way to set up a workout? Thinking something like stroke rate/power/HR targets, etc.

I understand that many/most use a third party app for this. But seeing as ORM seems to support it in some way or another, I thought I’d ask.

Thanks!

[JaapvanEkris]

I see that the docs mention planned workouts via MQTT; is this the only way to set up a workout?

You can also use ErgZone and similar apps in BLE PM5 mode.

Thinking something like stroke rate/power/HR targets, etc.

Not yet, as I haven't figured out how to display it in the GUI (the GUI is designed in an obscure lightweight framework, and I haven't figured out how to make it work, or move to a much better framework).

I understand that many/most use a third party app for this. But seeing as ORM seems to support it in some way or another, I thought I’d ask.

It is on our backlog, but first I want to expose setting up workouts to the GUI

[Abasz]

But it's a pretty huge project, and setting it as a prereq for some relatively small QoL things like presenting the current workout segment ORM is already able to handle might ultimately mean delayed "small things" for the sake of a sturdier "big thing" that is maybe more complex than we can even properly engineer for without having tried to do some of those small things first.

That is a fair point :)

Also actually I went into Lit documentation and I see that they now offer data management layer via context and experimental signals : https://lit.dev/docs/data/context/

It seems though that they mix typescript and js in the examples (not that I have anything against typescript, its far better than vanilla js in terms of maintainability).

I see that Lit implements signals as well though experimental currently (based on high level review its very close to angular signals).

Actually this is a very very helpful thing! we can inject the state via context and we can have separate service to manage state! This would allow to have unit tests as well.

I will look into this a bit more. I agree that there is no rush this would not make it to the next (0.9.7) release any way.

[DXCanas]

Key issue is that their way of specifying workouts often is in percentage FTP or HR Zones and not absolute values (like we use internally)

I think we should double check this. My experience is limited to Garmin, but I have synced a few different workout types there from intervals; based on what happened there, I think the "write" side (icu) can use zone percentages, absolute values, or ranges… but the resulting workout file (?) uses absolute-value based ranges every time.

Clever on their part, and useful because it means you only have to keep your icu ranges up to date across however many products you're "writing" to.

Initially, my workaround for ORM not supporting workouts was going to be to try using Garmin workout alerts in tandem with the PM5 ANT interface. Didn't even get to try it though, realizing how big a PITA it is to look down at your wrist during an intense session.

Perhaps start with the possibility to set a target distance and split from the GUI and see where it goes from there. Or being able to view the workout plan from the GUI.

I initially thought I misunderstood what ORM was capable of, as you mentioned needing to display targets. But I'm now seeing what you mean — distance doesn't have a "range" of acceptable bounds. Just a "remaining distance" 🤦 .

Do you think this would be a smaller step than drawing something up for the initial convo?

Not yet, as I haven't figured out how to display it in the GUI

If getting the data for "ranged" targets into the clientside is a simple enough job, I think a simple GUI displaying "out of range" vs "in range" is doable. Maybe just colors for now, and perhaps an icon to indicate whether you're too high/low? But I have not delved deep into the docs either of you linked yet.

[Abasz]

but the resulting workout file (?) uses absolute-value based ranges every time.

Technically garmin fit SDK allows % on HR and Power as well as absolute values.

Initially, my workaround for ORM not supporting workouts was going to be to try using Garmin workout alerts in tandem with the PM5 ANT interface. Didn't even get to try it though, realising how big a PITA it is to look down at your wrist during an intense session.

Not sure what you mean. But if you are saying that you program Garmin with the workout and you want that to be picked up that will not work. ANT is unidirectional meaning that ORM broadcasts and that is it. If you mean that you follow the workout on your garmin that works (this is what I do, I dont use ORM workout features at all).

If getting the data for "ranged" targets into the clientside is a simple enough job, I think a simple GUI displaying "out of range" vs "in range" is doable. Maybe just colors for now, and perhaps an icon to indicate whether you're too high/low? But I have not delved deep into the docs either of you linked yet.

I agree that a simple indication should be ok. I think we should color the tile (green/red or whatever) which has the target. I mean this would lie on the assumption that a target is set for which tile is visible :D So the additional data is simply the type of target and the range.

[DXCanas]

If you mean that you follow the workout on your garmin that works (this is what I do, I dont use ORM workout features at all).

This is what I mean! And is probably what I'll do for the meantime.

I think we should color the tile (green/red or whatever) which has the target.

Yeah, I was leaning green bg while in target, then maybe no BG with flashing partial border if off target; bottom flashing red if you're below the "floor" and top flashing if above the "cieling" 🤷

this would lie on the assumption that a target is set for which tile is visible

I think this is an acceptable amount of reliance on user for a first pass 🤪

[JaapvanEkris]

Yeah, I was leaning green bg while in target, then maybe no BG with flashing partial border if off target; bottom flashing red if you're below the "floor" and top flashing if above the "cieling" 🤷

Or simply change the color of the tile to indicate an issue. Often that is enough (that is what C2 does with HR targets. EXR has a slightly different approach: they have a dial and a green zone you have to stay in.