Plugin Switchboard : Virtual Switch in VeraPlus not shown in Openluup

[Edwin1972]

@toggledbits On my veraplus I try to use the plugin switchboard. On my veraplus I use a virtual window covering which can also be used in google home with tts. Now I also use openluup. The virtual window covering is not visible in openluup. Is this correct? I also use reactor in openluup. If this virtual window covering is not visible in openluup, I cannot use it in reactor either

[toggledbits]

You have to install the device type files on openLuup. Once the device type is recognized, Switchboard will let you create a device for it.

[Edwin1972]

@toggledbits I just installed the switsboard plugin on my veraplus because vera can communicate with google home via tts visa versa. This works well with the virtual window covering created by switchboard on vera. Openluup does not have a google home plugin and cannot communicate with google home via tts. I had hoped that the virtual window covering through the verabridge would be visible in openluup so that I can program it with reactor in openluup.

[toggledbits]

@akbooer, since I'm not a VeraBridge user, can you provide additional guidance? I've forgotten where the magic tool is...

[akbooer]

You have two options to get plugin/device files that you may need:

1. pull them all down from Vera using the VeraBridge action GetVeraFiles (no need for any Files parameter)
2. install the plugin whose files you need from Alt App Store (Switchboard is there)

In the case of #2, it will install a copy of the plugin, which you may not need (so can delete.)

Hope I've understood the question correctly.

[toggledbits]

@akbooer said in Plugin Switchboard : Virtual Switch in VeraPlus not shown in Openluup:

install the plugin whose files you need from Alt App Store (Switchboard is there)

I think he already has it under openLuup. The issue is that he has no device file for the window covering, option 1 is what I was trying to remember.

[akbooer]

In which case, #1 above should do it.

[Edwin1972]

@akbooer This is not what I mean. i try to explain it again.
On my vera I created a virtual device by using switchboard. The device is a window covering device with id # 1149
In openluup I don't see this device but I can call him with luacode (device id #11149)

luup.call_action("urn:upnp-org:serviceId:Dimming1", "SetLoadLevelTarget", {["newLoadlevelTarget"] = "50"},11149)

If the device is not visible in openluup I cannot use it in reactor

[akbooer]

Are you sure it’s not there? Different room? ... the one named after the linked Vera?

Have you restarted openLuup so that the bridge picks up the change?

[Edwin1972]

Thanks for quick respons
You're right. They are in a different room. I have a lot of divices so it was hard to find them but I found them in the MIOS room.

[Edwin1972]

@akbooer I did point 1 but now all my icons are no longer visible. Only the zwave icon is still visible. How can I fix this?

[akbooer]

What openLuup version are you running? There was an earlier error in downloading icons that was fixed fairly recently.

Alternatively, you can simply download the icon manually and put it in openLuup’s icon/ folder.

[Edwin1972]

Version 20.5.22.
Where can I download the icons? it's been a while since i installed openluup

[akbooer]

Try to update openLuup to the latest version by typing development into the Update box against openLuup on the Plugins page and clicking the update button. Then try #1 above, again.

[Edwin1972]

Thanks! It works

[Edwin1972]

@akbooer I've been using version 21.3.2 for a few days now, but the connection drops frequently. http: // IP: 3480 / cannot be called, so reactor doesn't work either and the lights and other things don't turn on / off automatically. Node Red can be called so my RP4 is well connected to wifi. Is it possible to go back to the old version; 20.5.22?

[akbooer]

It would be really helpful if I could get a log file from you which might highlight the problem. I've not come across this difficulty myself, nor (yet) had any other reports. Has anything else changed in your system?

Does the system remain up sufficiently long for you to get the logs and also revert? You can revert to any version manually by retrieving the files in the openLuup folder from the openLuup project in GitHub:

History for openLuup - akbooer/openLuup

a pure-Lua open-source emulation of the Vera Luup environment - History for openLuup - akbooer/openLuup

I've fallen out of the habit of tagging releases, so there's not a sufficiently recent one that you can revert to automatically.

I really would like to get to the root of this problem, though, rather than just trying to avoid it.

[akbooer]

Correction: the master branch is the version you were running, so simply updating from the Plugins page to that branch will do what you want. (It would still be good to understand what's going wrong for you in the latest.)

Edit: this release is now also tagged as v20.5.22 so you can always return to it easily by typing that into the Plugin Update box.

[Edwin1972]

@akbooer I can't remember changing anything except installing a new version at your request. Now I am back to 20.5.22 I still have the problem. I will send a log file.

• Which log file do you want?
• Do you want the log file after I can access openluup again?
• How will I send it to you?

[akbooer]

Both the startup and the main log showing, hopefully, some sort of error?

Email to openLuup @ icloud . com

Edit: maybe the latest and the .1 versions.