@stephack I'm just starting to play with the Symfonisk Sound Controller using this driver. It's one of the smoothest dimmers I've used to date when combined with the linked driver and start/stop raising a dimmer.
Using button 4 (turn right) and button 5 (turn left) of the controller, I'm able to jump +/- 3 in volume of my Symfonisk speaker, but I have to turn, stop, turn, stop, etc.
Would smooth volume control, like smooth dimming be possible? Alternately, is it possible to map a virtual dimmer rise/fall to the volume change?
NM. Just found out the start raising and start lowering doesn't work with a virtual dimmer.
Smooth dimming is a function of the driver (changeLevel capability that ties to the zigbee protocol command). It can be mimicked with code but in my experience this has rarely worked right. Look at the issues seen in the ST forum for those who have attempted it. The same goes for recreating doubleTap events for devices that support it. Some have gotten it to work reasonably well when dealing with one specific devices, but when it comes to general device support (like my ABC app) it can wreak havoc. If the driver creator can add button commands that implement a continuous + or - then it will simply work with any BC app.
I will look into adding previous track control to the app..I can't remember why I never added this in the first place.
I figured out how to do this with RM. It’s super hacky, but it works. Six rules, but that’s mostly because I don’t know how to do it with less and I had to use ABC for the actual volume changes (explained below). Someone with RM4 prowess could probably figure it out.
I had to add two additional rules, a virtual button and an extra ABC mapping because I couldn't get RM to adjust the volume of the Sonos, but it works fine from your app.
Here's examples for volume down. Similar was created for volume up.
I'm sure you can see the logic, but for clarity...
In the above examples:
Symfonisk sound controller is turned left, button 5 is pressed
Button 5 pressed turns on the virtual switch Sonos volume level DOWN trigger
Sonos volume level DOWN trigger changing evaluates if it is ON and if it is, then it turns on the virtual switch Sonos volume down, if not then it turns Sonos volume down OFF and exits the rule.
Sonos volume down turning ON triggers the second rule to check if Sonos volume level DOWN trigger is ON. If it is ON then the action turns off the virtual switch Sonos volume down, and then runs the actions of the first rule "Sonos volume down start"
The result is the virtual switch Sonos volume down toggles on and off rapidly. This toggling of presses button 2 on a virtual button each time Sonos volume down turns on. The second mapping in ABC changes the volume by -2 each time virtual button 2 is pressed. As soon as you stop turning the dial, the button press 6 is sent from the Symfonisk sound controller, which turns off the virtual switch Sonos volume level DOWN trigger, thus stopping the switch Sonos volume down from toggling on an off rapidly, and therefor the virtual button is no longer being repeatedly pressed, and the volume stop lowering.
Smooth volume control with one continuous motion of the Symfonisk sound controller
[Update] A warning about the Symfonisk sound controller here. Please read, or you may be pulling your hair out trying to find a mysterious issue that could actually be the result of rogue Zigbee signals from the controller itself.
**Update 11/05/19 ** ABC Child App updated to v0.2.191105
Added Previous Track option for Speakers
PLEASE NOTE: (IF UPDATING FROM v0.2.190210 OR EARLIER) THIS UPDATE CHANGES A SIGNIFICANT SECTION OF THE CODE. YOU WILL NEED TO OPEN EACH CHILD APP AND CLICK DONE.
Some time ago, someone had requested custom commands.
I was wondering if there was a way to do this yet?
In RM, you can create an action for a custom command, then choose actuator. This gives a list of device with the actuator capability, then a list of actions that the selected device can perform.
I truly wish hubitat exposed custom commands in their RM api but as of right now, they do not. I have tried to recreate this functionality, but it required a slight change in the flow of the app. This slight UI change, required a rewrite in many sections of the code. It also required quite a bit of logic to account for the many different command types and variable types (string, numeric, etc). I realized this one feature was making the app unnecessarily complex and bloated and chose not include this functionality in ABC. It's purpose was to simplify the steps needed to setup a button device.
If HE decides to include custom commands in the Rule Machine api, I will gladly try to add this functionality in the future.
@stephack - So clever to figure all this out, awesome.
I was stuck but the act of writing this question was enough to figure out my problem. Still posting in case it helps someone else.
Now I can't get events after changing the battery in the controller ....
Update: had to delete device and driver and rediscover with new name.
Then on rediscovery had to "Not" do double discovery recommend by others. If I do then HE fails to see device events......
I was getting this error, but it was becuase my trigger was trying to virtually "push" the physical button on the controller and not the virtual button which I hadn't created.
Note: This is where I went wrong. I was pointing "Sound volume control buttons" at the physical Symfonisk button and not the virtual button. That was causing the error.
@stephack Thanks for this app. I used it in ST and it was great so great to see that you have it here also.
Was wondering if you planned to implement StartLevelChange and StopLevelChange for dimmers? Right now, I'm using an Inovelli red series zwave plus switch to dim a hue light bulb up/down by holding and releasing the paddle. The switch exposes both a hold event and a release event (after the hold) as buttons. As such, I can get the hold to start dimming up/down (StartLevelChange) and the release to stop dimmer (StopLevelChange). However, because your controller doesn't seem to have those attributes, I had to use RuleMachine to make it work. Would be great if I can consolidate all my buttons in your controller though.
Right now, if I pause the rule for the StopLevelChange event, my hue light bulbs would continue dimming up/down till 100%/1% even if I only hold the paddle for a quick second. To get it to stop dimming when I release the paddle, I have to use the StopLevelChange on the button that corresponds to the "release" event.
Sorry for the late reply.
The ramp up/down in ABC was designed to work with button controllers that aslo support the "released" event. It sounds like your switch has this implemented.
I did not implement the stopLevelChange as a separate option as it should occur automatically on the released event. I'm wondering if this device has the proper HE implementation of the released event.
Are you using a cutom driver..if so, please post a link to it and I will skim the code.
@yototogblo, I skimmed the code for the "Inovelli Switch NZW30/NZW30T w/Scene" driver and I see that it sends pushed and held events but does not send released events. Unfortunately this device won't work with the level change implementation of my ABC app. I may look into adding a stopLevelChange option in the future but it won't be anytime soon as my time for coding is at a minimum these days. I would recommend you use RM if you need to send the stop command separately.
Thanks. The manufacturer posted instructions on how to add the released event to the code and that's what I'm using. It's essentially sent as a separate event from the held event.
Should I post the code here? Since it's 2 separate events (and thus buttons), chances are that it's not based on the proper HE implemention.
I will take a look. Thanks !
