Hi AK,
Can I make an other openLuup / VeraBridge suggestion? Is it possible to start those before any other plugins? This way all devices, local and especially remote will be availble to all others. Several plugins (or actually developers ) assume devices are known before their Lua start up code gets run as this will always be true on a Vera.
Let me describe my scenario why I ask this. I had two Veras bridged since the start so they have low device IDs (6 & 7) and start as one the first devices. One of my plugins (id 105) sets several watches to run some complex automation (Reactor was not yet around), all working just fine. Recently I got a new Plus and bridged that too and this bridge has id 190. Then I moved all devices from one of the first Veras to the Plus and some of my watches stopped working. I could see in the log file the watches got set, no error message nothing, but none of the watches to the new bridge would show in the scheduler watch table (thank you, thank you for those console functions in openLuup). Then I realized the bridge with id 190 was not yet started when my plugin with id 105 would set the watches. I now put in a 30 seconds delay in the plugin startup and that gives bridge 190 time to initialize all devices, but it assumes that is enough time, and increases chances of missing changes due to a reload.
Hence my ask if it is possible to start the VeraBridge plugins before any of the others. And maybe an error message when trying to set a watch on a none existing device id?
Cheers Rene