Verabridge imported my garage opener device, but in the process, did not import the correct device_json file (though the correct device_json file is in the openLuup “files” folder). Attached shows my Vera attributes, and then the openLuup attributes. You can see that openLuup has the default on/off json file, while vera shows the correct open/close json file.
As well, when i try to change the device json file in ALTUI, I get a message saying the the attribute has been successfully changed, but upon a luup reload, the original on/off json file returns. This occurs even after waiting several minutes to do a reload.
Are you using a Raspberry PI? I had issues with a SD card, was working fine until I tried to change the settings of a plugin and after rebooting the settings where gone. Drove me crazy until I found out that I could read from the card but it most times it failed to write to it.
Yeah, using an OrangePi and I suspect that SD card trouble is partly what is happening with problems saving data. I moved the logs to a USB stick to minimize writes.
I found that bigger cards 32g+ and cards from major companies last longer. I am using a Raspberry PI 3 and boot off a usb drive that should be better for longevity.
I dug into this a bit more and found that, in your code, for the most part, you’re bringing data straight across from the target Vera. Which led me to look at my two veras and how they are communicating through the vera bridge. Lo and behold, there seems to be a bug in Vera’s implementation of THEIR bridge between two Veras. The bridged device_Json file name (on my primary vera) does not match the host vera’s device_Json file name (secondary Vera). I deleted the bridge between the veras and reformed the bridge just to make sure there wasn’t an error in the original link up. But after doing so, the error remained.
When I configure the openLuup Verabridge, I’m bridging to my primary Vera, which in turn bridges one way to my secondary vera. The garage device is enrolled on my secondary Vera. So openLuup Verabridge is only seeing configuration data from my primary Vera, thus the noted error.
It’s hard to believe that after all these years there is a bug in a basic part of the Vera OS, but I can’t think of any other reason to explain this behavior. What in your opinion is the best way to bring this to MCV’s attention??
Edit sent a trouble ticket to MCV but have not heard back.
Are you sure that the json file you want actually exists on your ‘primary’ Vera?
My advice would be to drop the bridging between the Veras and just run two VeraBridge plugins, one to each Vera, on openLuup. You can always mirror back any interesting variables required for remaining logic on the Veras, if necessary.
Typically 0.5 seconds, unless either of the systems is busy.
What do I need to do on the vera side?
Nothing, except arrange your logic to use the relevant variables. Although you may choose to create a virtual device to hold your mirrored variables.
If you describe a scenario where you need this, I can show you how to achieve it. You could try it out on your current system before deciding if you want to unbridge your Veras.
Best Home Automation shopping experience. Shop at Ezlo!