It seems as if it is possible to modify it with an external antenna.
Here is an article on how to modify the Razberry2 EU:
Modify Razberry2 (translated)
Is is in Swedish, hopefully the translated text is understandable. 
In short you cut away the built-in antenna and solder on an antenna connector for the external antenna. You of course need an antenna for the frequency in your country, the article is for 868 MHz (EU).
//ArcherS
Checked with v20.7.14 and the "sl_CentralScene" variable is updated with the key pressed.
Thanks again for the update!
Thank's for a really quick reply! That indeed did the trick, I knew it was something easy I missed.
Now I just need to go through my Reactors and re-map my z-way devices. Not too much work.
//ArcherS
One solution that I can think of is to use MySensors. https://www.mysensors.org/
This is a DIY community platform for making sensors etc. It is supported by Vera and OpenLuup, @akbooer is using it if I am not wrong.
I found someone that had made a water pressure sensor that you perhaps could have a look at for inspiration: https://forum.mysensors.org/topic/8731/water-pressure-sensor/1?_=1590472756396&lang=en-US
In short with MySensors you set up a gateway and then the sensors you want. Each node is an Arduino or similar. I used an USB connected gateway with my Vera, but an Ethernet connected gateway is needed for OpenLuup.
I set it up a number of years ago on my VeraLite and it actually worked really well. I used it mainly for simple temperature sensors. I stopped using it because of that each time the Vera rebooted the gateway was lost, and I had to re-discover it on the Vera USB port. Quite a bit of hazzle since the Vera had a tendency to reboot quite a lot.
If I get some time I may have a go at restarting MySensors now that I am using OpenLuup since it would be a good way to add dirt-cheap sensors to the system.
I included a ZRC90 remote to Z-way. The inclusion was without problems, and in Z-way you can see what button is pressed.
In OpenLuup I get the same variables as Catman has listed above. I tested and the two variables "zway_61-0-91-DS" and "zway_61-0-91-DS_LastUpdate" on the remote device are updated on key presses.
Depending on what you press "zway_61-0-91-DS" get the following values:
Btn 1 single press: 10
Btn 2 single press: 20
...
Btn 8 single press: 80
Btn 1 double press: 13
Btn 2 double press: 23
...
Btn 8 double press: 83
Btn 1 press&hold: 11
Btn 2 press&hold: 21
...
Btn 8 press&hold: 81
Each time a button is pressed zway_61-0-91-DS_LastUpdate is also updated with a new time.
So far so good, the above two parameters gives the possibility to capture the various key presses on the ZRC90.
What does not work is that I get the same problem as I did for the Zwave.me wall controller, i.e. that the two variable are not updated in Reactor on key presses.
@akbooer is this something that can be fixed?
I am running OL 20.7.4b and Z-way plugin 20.5.12.
(The key presses on the Zwave.me wall controller are still working.)
//ArcherS
@akbooer Yes a scene or a Reactor could of course work. This is what I did on the Vera in a Reactor and it worked quite ok. I will give it a go again in OpenLuup. The on/off switches on the controller in the GUI do not really matter that much I think.
Regards
//ArcherS
One option would be to use MySensors. This is a cheap way of adding various Arduino sensors to OpenLuup. You set up an Ethernet gateway and then each sensor is connected to the gateway wirelessly. There is a MySensors plugin that works in OpenLuup.
This looks like an interesting project, that you perhaps can get inspiration from: Round water tank level sensor
Good luck!
I updated to v20.7.12 and it works partially!
"LastSceneTime" is updated every time you press a key, so that one works.
"sl_CentralSceneUpdates" however stays "null" all the time.
On the ZRC90 that I still have on the Vera there is a variable called "sl_CentralScene" but no variable called "sl_CentralSceneUpdates". I do not know if this could be the reason.
As a side note the variables "zway_61-0-91-DS" and "zway_61-0-91-DS_LastUpdate" are now updated instantly in Reactor.
So a functional workaround could be to use the "zway_61-0-91-DS" and "LastSceneTime" variables for capturing keys pressed in e.g. Reactor. I did a quick test and it seems to work.
@akbooer sorry, no I do not have a complete list of the variables created in Vera. I forgot to check that before excluding.
By the looks of the controller I am quite sure it is the one in this old Vesternet guide APNT-44
In fact if I remember it correctly that guide is what I used on my VeraLite on UI5 many years ago.
On the UI7 Vera I however used "sl_SceneActivated".
I also think that "LastSceneTime" was present on it. (These represent the "zway_Remote_16-0-1-B" and "zway_Remote_16-0-1-B_LastUpdate" at present I assume.)
You are correct that all I would need are those two variables as triggers, because then I can use the on/off as one trigger and the time as a trigger as well. I think I may need the time to capture e.g. if you press the "off" button and the controller already was "off". I tested this and the time is updated.
Thank you very much for your time and effort.
//ArcherS
Now it works!
I created a Reactor that uses the two variables "zway_Remote_16-0-1-B" (for on/off) and "zway_Remote_16-0-1-B_LastUpdate" (for the time the wall controller is pressed).
The Reactor has two conditions for triggering "on" and two for triggering "off". This is to handle the case that the wall controller e.g. could be in "off" when I want to turn the Aeotech Switch off (e.g. when I have turned it on from HomeWave directly).
To make this work I created two expressions "TimeAtOn" and "TimeAtOff" in which I store the time when the controller state changes from on->off and vice versa.
Just as a note, I also checked the variable "LastSceneTime" and it also gets updated with the time stamp. The variable "sl_SceneActivated" however always remains "null" for some reason. I do not know if this is intentional or not.
Thank you very much for your time and patience!
//ArcherS
@dest You connect the constant 12/24V power supply + to P and - to GND on the Fibaro. Also connect + on the PSU to + on the LED strip.
Then you connect the OUTnn to the corresponding pins on the RBG LED strip.
If you do not want any switches INnn on the Fibaro should unconnected.
My three (not four as I wrote above, sorry) set of LEDs in the kitchen are connected according to this diagram, perhaps it can be of some use. Note that the LED strip in my case is a white one that only requires one "OUT" connection to the Fibaro.
Also note that on the older Fibaro version that I have "OUTnn" were named R, G, B and W.
The diagram is in Swedish, but I hope it makes sense anyway.
//ArcherS
@dest I have two of the older version "RGBW Controller".
One is driving a white LED strip on one of the channels and a set of 12V lights on the other channel.
The second unit is driving one white LED strip on one of the channels and three sets of LED spots on the other three channels.
In other words no RGB(W) strips on any of them.
To be honest these two Fibaro units have caused the most headache of all my units. Strange behaviour activating/deactivating other zwave devices a few times, not reporting status etc. I have had to unpair them a few times over the years. They seem a bit better on Zway, but not faultless there either.
Fibaro devices seem have problems with compatibility, because of this I have decided not to buy any more.
//ArcherS
Has anyone looked at Zigbee2Tasmota? It is supposed to work with the Sonoff ZBBrigde which looks ok and is quite cheap. The bridge seems to be easy to flash with Tasmota.
I have been playing a bit with Tasmota on ESP8266 lately for sensors and is quite impressed. It seems quite capable and stable.
I have so far avoided zigbee due to the lack of easy integration into my system except a few Hue light on a Hue hub and AltHue.
The upside of zigbee as I see it is that there are a few rather nice sensors such as Aqara that could be interesting to use.
//ArcherS
@perh Take a look at Homewave if you are on iOS. It works with Vera, both UI5 and UI7 and it also works for OpenLuup. You can have multiple controllers mapped seamlessly at the same time.
For Veras it works with cellular access, for OpenLuup you need a vpn to access the system when being off-site.
//ArcherS
It seems as if it is possible to modify it with an external antenna.
Here is an article on how to modify the Razberry2 EU:
Modify Razberry2 (translated)
Is is in Swedish, hopefully the translated text is understandable.
In short you cut away the built-in antenna and solder on an antenna connector for the external antenna. You of course need an antenna for the frequency in your country, the article is for 868 MHz (EU).
//ArcherS
@akbooer Indeed. I had Firefox in the old PC set as English US, and the new as Swedish. I changed it and now it works.
Thank's for the assistance!
//ArcherS
@akbooer Yes it seems as if they differ.
Found another old thread with some more clues.
If I add "&lang=en#" to the end of the AltUI url it works.
When looking in "Localizations" on the old PC it says:
browser query: userlanguage: language:en-US
and on the new PC:
browser query:en userlanguage: language:sv-SE
@akbooer Yes, I checked and it seems to be enabled:
When I try to access OpenLuup via AltUI from a new PC on my local network that I have not used for OpenLuup/AltUI before I get "Waiting Initial Data" and then it just gets stuck.
It works when I access the OpenLuup console from the new PC however. It also works via AltUI from my other PC that I have been using before. I am using Firefox on both PCs.
I am probably missing something obvoius, any idea what the problem could be?
Edit: I get the same problem i Chrome. I found an old thread with some info. Looked in the Chrome Console and it says:
//ArcherS
Checked with v20.7.14 and the "sl_CentralScene" variable is updated with the key pressed.
Thanks again for the update!