[quote=“Jim McGhee, post:23, topic:200515”][quote=“a-lurker, post:10, topic:200515”]
I can, but it will be for Vera only at this time. Does that work for you?
Does that mean it will not work with openLuup and / or AltUI?
Also GitHub changed a few things with their own security so some of the older Veras now can’t engage with the Alt Store, so that’s a separate problem in itself.
All up, no big deal.[/quote]
This may be what is happening to me, although, I hardly think of my VeraPlus as an ‘older device’. When I click on the ‘Alt’ button on the Alt Store, it just turns red and changes to ‘Failure’ Same on my VeraLite. I installed it manually OK but would really like to install it from the Alt Store instead. Any idea how to fix this??[/quote]
No idea, and I’m not in a position to troubleshoot it; I don’t use ALTUI/AltAppStore on any of my Vera systems. It works under openLuup, so I’m assuming it’s a platform-specific issue.
Edit: let me add to this. IMPORTANT INFO FOR ALTUI/ALTAPPSTORE USERS ON GENUINE VERA SYSTEMS (this info does not apply to openLuup ALTUI/AltAppStore users). Installing this particular plugin using the AltAppStore to a Vera system is actually something you should not do–again, with this particular plugin. There are certain device and service files that exist on Vera that the plugin requires, that do not exist on openLuup. For this reason, the Vera install (via Vera Plugin Marketplace) and openLuup install (via AltAppStore) are different–the openLuup install has to include those missing files as extra installed resources. There is no way that I’m aware of in the AltAppStore to set different file/resource sets for Vera targets vs openLuup targets, so any install using the AltAppStore is assumed to be an openLuup target and will install those extra files. So if you use the AltAppStore on Vera to install this plugin, you will get the additional files intended only for openLuup that will thus duplicate existing Vera system files and may override the Vera versions of those files. That might be bad. It might change all of your binary switch UI behaviors system-wide. It might mask future changes Vera makes to their files. You don’t want any of that, so don’t do that.
If you are installing this plugin to Vera, use only the Vera Plugin Marketplace, or a manual install (and omit the files in the openLuup subdirectory). If you are installing to openLuup, use the AltAppStore, or manual install (and in this case include the files in the openLuup subdirectory). Don’t cross the streams.
While I'm on the subject..
It would be nice if there were a checkbox I could click that would make a switch be 'state agnostic'. By that I mean if the switch is off and you turn if off again it will still fire it's off trigger anyway.
If I have a switch that triggers an 'All Lights On' scene when turned on and an 'All Lights Off' scene when turned off I might want to turn the switch/trigger off and a few hours later turn it off again to turn off any lights that have been turned on in the interim.
Sound interesting? Do-able?
And BTW, thanks for the plugin. I'm finding it very useful.
Done. Install the stable branch version, direct link to it here: GitHub - toggledbits/Switchboard-Vera at stable
I know you already installed yours manually (so you know how), but for the benefit of others reading: to update an existing install, click the green “Clone or download” button at the above-linked page, and choose “Download ZIP”. Then unzip the contents of the file, and upload the files to Vera using the uploader at Apps > Develop apps > Luup files (better to turn off the “Restart Luup after upload” checkbox until you get to the last file). Do a full browser refresh with cache flush as well.