-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated to latest version and now switch-multi's don't turn off automatically. #350
Comments
use a syntax like this
|
Hi... This previous configuration worked with noticeable change in volume
The volume up and volume down is sending a few times so that volume noticeable in- decreases. The new configuration just slightly chances the volume almost not noticeable.
The same with
Any Idea what I am doing wrong? Thanks in advance. |
I got mine to work with this: { |
@jat80 You used the "type":"switch-repeat" again which is no longer supported in the future. That was the point changing to "type": "switch". With switch-repeat I haven't had a problem at all. |
@DJay-X this was the only way I could get it to work with the current update. Not sure how it will be going forward but it works for now. |
Looks like there have been a lot of changes with the terms for accessory types and this latest update in general.
I previously had a switch multi type my config which WAS working fine and looked like this but now it won't turn off automatically:
{
"name":"Volume Up",
"type":"switch-repeat",
"sendCount":4,
"interval":0.3,
"data":"hex code here"
},
With the update I've tried adding this format:
{
"name":"Volume Up",
"type":"switch",
"enableAutoOff": true,
"onDuration": 2.5,
"data": [
{
"data": "VOLUME_UP_HEX...",
"sendCount": 4,
"interval": 0.3
}
]
},
everything accepts in the config but it won't actually fire the hex code. The home app button turns on then off as expected but IR signal is not sent. (no light on rm mini either). I've tried adding the auto off line in the original code but that doesn't work.
Any tips?
The text was updated successfully, but these errors were encountered: