04-19-2017, 05:04 PM
(This post was last modified: 04-19-2017, 05:07 PM by Christopher Wansing.)
(03-02-2017, 10:25 PM)vbs Wrote: I have the normal messages now working reliably in FHEM, thats fine
But it seems I was wrong about the other message type: In fact it is not only sent once on bootup but it is sent regularly (even quite often):
Can you tell something more about the Fhem integration? I have a 433Mhz Cul and want to do the same thing you did. I am new to Fhem but already looked at quite a lot things and integrated some Intertechno(Pollin) outlets and a lot of Max! Heating thermostats. But I am totally new to integrating custom RF devices, which are not regulary supported by Fhem, despite I am really eager to learn it, because there are quite a few devices I could use this for.
For example I also have cheap 433Mhz Lightswitches from Aliexpress throughout my apartement and want to get Fhem to recognize those, too. The current solution with a cheap RF Receiver and an RCSwitch based Python RFSniffer is quite unreliable, when I am using an emitter at the same time. Seems they are booth using the WiringPi library and that there are some cross complications(At least thats what I found on the internet till now)
What I already know is how to record the raw pulses using an RTL-SDR and some basic knowledge about setting the CUL to a verbose mode 5 and that there are some codes to get the CUL sending raw messages to Fhem.
What I dont know is how I am able to react on those or how I can write a script to process the data. Do I have to leave the Raw message state and verbose 5 or am I able to write a custom module, so that in the end fhem supports the device more natively? Because the I dont really want all the messages this generates in regular running mode.
Would be very glad about at least some hints in the right direction, for getting this to work
