I’m sorry, I completely missed responding to your post initially… it’s been a hectic week at Casa Rigpapa.
On Vera Luup, the startup and scene Lua run in a separate environment from the plugins, and each plugin runs in its own environment. It is therefore not possible for globals defined in one environment to be visible to another, and I don’t see that changing. It’s actually a Very Good Thing in terms of both security and system stability (and I can make the argument that it really doesn’t go far enough, but it’s a good start).
The previously recommended approach for this is to move your startup Lua code to a Lua module, and
require that Lua module in your startup Lua and scene Lua as needed, so you can then call its functions as module members. Likewise, you can
require the module in your ReactorSensor’s “Run Lua” actions. This gives you re-use of the code. It will not give you re-use of globals, however, this is probably a Good Thing as well, as passing data around in globals is generally considered to be a poor programming practice and to be reserved only for very limited circumstances.