I would like to have a variable in Openhab that shows the current outside light value. Kind of like seeing the outside temperature.
I found a checkbox in VelbusLink for a VMBPIRO that automatically sends the current light value on the bus. In the logging I can see a “light request”
FYI Address 16 is a VMBPIRO, absolutely no ID if “Light value request (AA)” is of any use.
I would like to use this value to make a rule: when I wake up I press a button in Habpanel, my Yamaha AV receiver turns on, my roller shutter goes up, and depending on the outside light value I want some lights to turn on or not turn on.
Easier than pressing 4 buttons
No, velserv is a TCP/IP gateway so you can access your Velbus over te network.
My code does the same as the OpenHAB Velbus module. It’s a 2-way gateway between OpenHAB en Velbus so OpenHAB knows that happens on the bus and can send commands to the Velbus modules.
Since I never used the Velbus binding I don’t know if what you ask is possible.
Okay, now I’m confused.
I do have the velserv running on a RPi, I can program my Velbus over the network (which is much better than using a USB cable and being stuck to 1 place), and I use OpenHAB. Mainly HABpanel that is.
But are you saying we don’t need the Velbus binding by Cédric?
As for the light value, @Stef_Coene, could you explain (or give me a URL where I can find) how to use this?
@MDAR I’m not familiar with NodeRed, but I know you use it a lot. Maybe I’ll have a look. And also, if the light value is already integrated in velserv, I don’t need NodeRed.
VelServer is Stef’s script based solution for grabbing Velbus packets and passing them to platforms like openHAB2.
VelServ is Jerome’s TCP server that converts Velbus USB / Serial interface data into TCP packets, for anything to access, like VelbusLink, OpenRemote, openHAB2, NodeRed Velbus node (TCP is in development)
The following version of the Velbus binding should add an extra “LIGHT” channel to the VMBPIRO containing the current light value. I haven’t a VMBPIRO for testing, so let me know if it works (or if it doesn’t):
You will probably have to delete your VMBPIRO things in OpenHab and re-detect them through a search on the Inbox before the new “LIGHT” channel appears.
In Velbuslink the value used is definately not in lux, as they use 0 for light and 1023 for dark.
I’m not sure it’s working ok, current Velbuslink value is 20, and the Openhab-control shows 512, which is the same value as @MDAR’s paste of the Openhab-control…
I have managesd to get some time to test Cedric’s latest binding version now and I have updated the update-velbus-jar-dev.sh script’s resource so that it pulls down this new version - 126.96.36.199002151409
I’ve tried version 188.8.131.52003141938 which is currently the latest one on Cedric’s github. Still 512 lx
Then I’ve tried the version you mention, again, 512 lx.
Each time removed the VMBPIRO and added it again.
The only thing difference I see is that I still use Openhab 2.5.1
Maybe that’s a reason?
Just want to mention in your readings, the difference between 37520 lx and 1536 lx is pretty huge, no? But maybe you’re right if the one is in direct sunlight and the other is under an eve.
Also, I don’t know if you remember, but i had a lot of problems with my RPi, I’ve made another post about that. It’s still a 2B. I do have a 4B laying around here, waiting to be installed. I’m thinking of doing everything text-based, not through Paper UI. But I haven’t found the time yet
Maybe in the coming days/weeks, 'cause I think we’ll be spending more time at home than we’d like due to the COVID-19 stuff…
It sounds like there is something else at play here, if you’re getting identical readings from both versions of the binding.
Which firmware do you have in your PIR ? I’ve got 1817
I think that is more to do with the fact that the PIR isn’t really using Lux / Lumen values, it’s a Velbus only value for using with the light dependent motion sensing.
You might be able to find a correlation…
… Um… I remember a lot of people having issues with Raspbery PIs, but that doesn’t seem to stop people buying the…
When you do…
Take a look at the generic template that I’ve put together, it should have everything you need for every type of module that Cedric’s binding supports and there is a velbusNetworkBridge.thing file in there too, so that the IDs for each module will be the same when you import them into PaperUI, even if you have to completely rebuild a system