RFXtrx

[Mastiff]

One funny thing, though: After the plugin is reset, it still has red text in the tree (Plugin:RFXtrx).

[Mastiff]

There may have been a print statement you have forgotten. Every minute I see this:

Code: Select all

15:00:01   Interface mode:  ['0d', '01', '00', '01', '02', '53', '53', '04', '00', '06', '00', '00', '00', '00']
15:00:01   RFXtrx Firmware Version: 83
15:00:01   RFXtrx receiver/transceiver type: 433.92MHz transceiver
15:00:01   You have a RFXtrx Type 1
15:00:01   Interface mode:  ['0d', '01', '00', '01', '02', '53', '53', '04', '00', '06', '00', '00', '00', '00']
15:00:01   RFXtrx Firmware Version: 83
15:00:01   RFXtrx receiver/transceiver type: 433.92MHz transceiver
15:00:01   You have a RFXtrx Type 1

[krambriw]

One funny thing, though: After the plugin is reset, it still has red text in the tree (Plugin:RFXtrx).

This is a behaviour of EG itself, after a while I think it goes away from red to black

There may have been a print statement you have forgotten. Every minute I see this:

I think the problem is that I have a flag that is not correctly reset after the check has been performed, I will see how to improve. Maybe a restart of EG is needed for the moment

[Mastiff]

A restart of the program fixed both. So I guess instead of using a reset of the plug-in I should hook the disconnect-message to a restart command (EG App Control).

[krambriw]

I found the problem with the flag, it was what you can call a "tankevurpa" in Swedish

Updated version is uploaded..

[Mastiff]

I think the English version of that would be "brainfart"! I'll download and test. If you don't hear back within ten minutes, consider it fixed! Thanks!

[Jacco]

Hello, I am using the RFXtrx, and if I start the RFXmngr I can see the information from the Oregon BWR102.
But when I try it Eventghost I don't see it.

Can someone tell me what I'am doing wrong.

Regards,
Jacco

[krambriw]

You are not doing anything wrong, it is because I have not implemented support for it

[krambriw]

@Mastiff,

PS How is your test under VM working out?

[Mastiff]

No problems so far. I haven't had a dropout except for the ones I have created myself to test, but from the tests I think it should work on a real dropout too!

[krambriw]

Very good!
Thanks

[Mastiff]

I should thank you! This is a very nice safeguard to have.

[Mastiff]

Morning, dude! I had a mail last night at 03.28 saying that there had been a reset of the plug-in (remember I said I wanted to connet a mail action to it so I could know if something happened). I saw it this morning and thought: "Great, this works nicely!" Then, while I was brushing my teeth (yeah, I'm a late riser - married to an early bird, which can be annoying at times...) another one came in. And it seems like there are some false alarms here. Check this out, this is from the log that came then:

Code: Select all

09:21:10            Sensor: Stue  Tidspunkt og dato:  Kl. 09:21, den 14.02. 
09:21:10            
09:21:10   RFXtrx.Lost connection with the RFXtrx
09:21:10            Stopping and disconnecting the RFXtrx device...please wait
09:21:10            Date & Time thread ended
09:21:10            Keep Alive thread ended
09:21:11            Receiving thread is stopped...
09:21:11            Cleaning up monitoring tasks...
09:21:12            Plugin successfully stopped
09:21:14            Interface mode:  ['0d', '01', '00', '01', '02', '53', '53', '04', '00', '06', '00', '00', '00', '00']
09:21:14            RFXtrx Firmware Version: 83
09:21:14            RFXtrx receiver/transceiver type: 433.92MHz transceiver
09:21:14            You have a RFXtrx Type 1
09:21:14            Copyright RFXCOM. A genuine RFXtrx is detected and started
09:21:22   RFXtrx.Type: Viking 02811 id: 43008 ' temperature: +22.6 deg C signal: 5 battery: 9'
09:21:22            WC.: Temperatur: 22.6, termostatmodus: 1, termostattemperatur: 22, tidspunkt: Kl. 09:21, den 14.02.
09:21:22            
09:21:22            Sensor: WC  Tidspunkt og dato:  Kl. 09:21, den 14.02. 
09:21:22            

There are no error messages in the log, and there isn't even a second between the last event coming in and the "lost contact" mesage. And then around 12 seconds later the plugin's running again. Doesn't seem right to me.

[krambriw]

Is this the PC that is running EG under VM?

Doesn't seem right to me

I'm not so convinced, I think it looks ok to me. There was obviously a problem detected since the restart happened. The code in the plugin is trying to 'talk' to the RFXtrx every minute and is expecting a correct answer. If this is not happening, the event is triggered. The question is if there is any harm with the current implementation, I do not retry if the first answer is incorrect. Did you already implement a counter in your script?

[Mastiff]

You're probably right. I haven't yet implemented that, no. But it sounds like a very good idea (another one of yours!) to give it a second try if it doesn't get the right answer at first.