Speaker Volume Piston

[joelw135]

1) Give a description of the problem
(Trying to create a piston to maintain volume of my Samsung Radius R! speakers, but it doesn’t seem to change the volume in the IOS app. I have included two pistons which is better.)

2) What is the expected behavior?
(Volume changes to 50% Value in a range of 0>100)

3) What is happening/not happening?
(Volume value remains the same in IOS App)

4) Post a Green Snapshot of the piston
(

)

5) Attach any logs (From ST IDE and by turning logging level to Full)
`

REMOVE BELOW AFTER READING
If a solution is found for your question then please mark the post as the solution.

Will this Piston work better and cover all bases, up or down?

[joelw135]

Can Anyone help getting this to trigger?

[Robin]

Looks like it’s being triggered (based on the first piston have the green bar next to the condition)…

You need to test the action command is working so create a blank piston with a single action in it, no IF.

execute
with music player 5
set level to 50
end with

Then save and hit the test button, see if the volume changes.

[joelw135]

Then save and hit the test button, see if the volume changes.

I created the Piston:

![50 PM|690x66]

[Robin]

And? What happens when you click test?

[bobbles]

Is this thread the same as what you was trying to achieve yesterday?
I put a trigger in to make it work.

[joelw135]

Is this thread the same as what you was trying to achieve yesterday?

I put a trigger in to make it work.

Yes Bob but it seems to be triggering late, so it adjusts the speaker after the sound is sent.

[bobbles]

OK. That’s how it was built.
The one I wrote needs a trigger first, Music player status change, to know that it is on and therefore change the volume level.
The only other way I suppose is have the one above AND another one that runs, say every 15 minutes to set the level.
That might suit your needs.

[joelw135]

OK. That’s how it was built.

The one I wrote needs a trigger first, Music player status change, to know that it is on and therefore change the volume level.

The only other way I suppose is have the one above AND another one that runs, say every 15 minutes to set the level.

That might suit your needs.

Yes I am using yours, the one above was a test. How do I add a trigger to run every few minutes during certain hours? Should I use a virtual device in Time Mode?

[bobbles]

You could use a Timer to run every few minutes between certain times.

[joelw135]

You could use a Timer to run every few minutes between certain times.

Not to sound stupid, I looked in the If for a timer function and couldn’t find it. How about a hint where it is?

[bobbles]

First you need to ensure advanced statements is ticked.

Click on add a new statement.

The TIMER option should now be available.
Now choose what you want to do.

[joelw135]

First you need to ensure advanced statements is ticked.

Click on add a new statement.

The TIMER option should now be available.

Now choose what you want to do.

I hope I have this correct. Is this in the correct place?

[bobbles]

The every 15 minutes part is correct but you haven’t put anything in the DO part.
Put in there
WITH
Music Player
DO
Set level to 45%

[joelw135]

The every 15 minutes part is correct but you haven’t put anything in the DO part.

Put in there

WITH

Music Player

DO

Set level to 45%

Thank you Bob, you have helped and taught me a huge amount. No to implement what I have been taught will be a task for me.

[bobbles]

As the speaker is not actually on, i don’t know if it will actually change/set the level or not.
Not something I need to use.

[joelw135]

As the speaker is not actually on, i don’t know if it will actually change/set the level or not.

Not something I need to use.

I wish ST would fix their DTH as it is becoming a pain in the butt. Maybe it will act like a refresh, not sure.

[joelw135]

The volume control with timer works better, but getting this in logs, is there a way to fix this?

[Robin]

That’s not an error, it’s normal.

Though webCoRE can be synchronous, ST is inherently asynchronous. Two processes cannot happen at exactly the same moment so one inevitably has to wait, in this case for 268ms (0.2 seconds).

[joelw135]

That’s not an error, it’s normal.

Though webCoRE can be synchronous, ST is inherently asynchronous. Two processes cannot happen at exactly the same moment so one inevitably has to wait, in this case for 268ms (0.2 seconds).

OK, as long as it won’t cause problems.