RFXtrx

[krambriw]

I do not have the old protocol and I am really not too much interested in digging into it either if you understand, it would be rather time consuming to add support for those devices.

I tried to find the setup of the xPL Monkey in my machines but I only have it installed in one of my PC's.

And yes, I believe the string will most likely change as you suspect if the signal changes. Also it might change if the battery level changes and I believe there is also a message sequence number in there.

One way could be to try to generate a couple of same events with different signal levels and compare and see if you can detect a difference. Then, if you reach that far, you can do a better parsing of the string to extract exactly the information you need.

Best, Walter

[dannehalle]

I have an Oregon temperature gauge that I receive and try to send with Broadcaster UDP.
I tried to make a script, but it did not go well. I tried with this script to send temperatur ...

RFXtrx.Type: THGN122/123, THGN132, THGR122/228/238/268 id: 26625

p = eg.event.payload
p = p.split(' ')
outtemp26625 = p[2]
eg.globals.outtemp26625 = outtemp26625
#print outtemp26625

And then send outtemp26625 with broadcaster but the result was (outtemp26625)

print outtemp26625 works but how do I send this value?

[krambriw]

Try this (just change the port number so it fits your receiving end

Code: Select all

p = eg.event.payload
p = p.split(' ')
outtemp26625 = p[2]
eg.plugins.BroadcastListener.Broadcast(u'test', str(outtemp26625), 33330)

[dannehalle]

It worked very well, thank you very much. I just switched to the correct port number and the (test) to buttonname ^. Now I can see the temperatures in Touch Control app

[krambriw]

[krambriw]

New version supporting FW 68 published in first post

[krambriw]

New version supporting FW 69 published in first post

[haklis]

Hello,
First thank you for making this plugin!
I regularly loose my communication to the rfxtrx433. Seemes like the com port interface hangs. A PC restart is needed to solve this. Eventghost restart is not sufficient, then an "cant open com port" is showed when the plugin starts. Any ideas?
See this error message:

14:02:03 Error in Action: "RFXtrx: send_AC: Varme Mads ON"
14:02:03 Traceback (most recent call last) (1640):
14:02:03 File "C:\Program Files\EventGhost\eg\Classes\ActionBase.py", line 170, in CallWrapper
14:02:03 return self(*args)
14:02:03 File "C:\Program Files\EventGhost\plugins\RFXtrx\__init__.py", line 5691, in __call__
14:02:03 self.plugin.WriteMsg(msg, w_msg, w_key)
14:02:03 File "C:\Program Files\EventGhost\plugins\RFXtrx\__init__.py", line 856, in WriteMsg
14:02:03 self.serial.write(str(data))
14:02:03 File "C:\Program Files\EventGhost\eg\WinApi\serial\serialwin32.py", line 234, in write
14:02:03 err, n = win32file.WriteFile(self.hComPort, s, self._overlappedWrite)
14:02:03 error: (5, 'WriteFile', 'Ingen tilgang.')

An intermediate solution could be to issue a PC restart when this error message shows, but how can I do that? Is the error message stored in a variable?
Regards Hakon

[krambriw]

The plugin is in use by many users so if there would be some similar or generic problem with it we would have heard it.
I think instead you should start look for conflicts in Windows of some kind, maybe you have another softwaretrying to use the same port??

[b_weijenberg]

Hakon, it seems the FTDI driver becomes frozen. This problem has been reported a very few times and was solved connecting the RFXtrx433 to a powered USB hub.

[krambriw]

...and please report back if it helped...

[krambriw]

New version supporting the new FW release version 433_70 published in the first post. I have changed the configuration view as below. Use RFXmngr to enable/disable selected protocols.

[Mastiff]

Thanks! Got it.

Btw do you have any idea why I'm getting a line saying

Code: Select all

10:22:22         Persistent values: {}

when I start EventGhost? It has an exclamation mark in a yellow triangle, so I'm guessing it's a warning sign about something.

[krambriw]

Hi,
It is not coming from the RFXtrx plugin itself, it must be something else, maybe another plugin...
Try to disable plugins, one at a time, and see if/when the message comes back when you enable them one by one again...

BestR Walter

[Mastiff]

Will do, thanks!