RFXtrx

[spidersprog]

Ah OK

Turns out I was doing everything right except my unit was a little to far away from the trx for the learn function.

Moved it closer paired them up and now I've moved it back to its original location and it woks perfectly

Thanks again

[krambriw]

New version published in the first post.

Best regards, Walter

[mickelin]

Hi, good to hear

"Work with the UPM wind sensor you added to the NetHomeServer plugin last year"

Well, I am not sure, we will see. It works with Oregon I have seen, someone in my area must have such a thing because I get a lot of readings all the time.
Anyway, you still have the NetHomeServer, I have that too , and all are working fine in parallel, all connected to EG

I guess for Nexa, you use the ARC protocol right?

Yes, correct

what about self learning? Is that the AC protocol?

Yes, that's the one

Best regards, Walter

Got it delivered today, totally impressive! It worked right away with Nexa, Koppla, GAO and UPM, range seems very good. Tried your plugin and it worked like a charm! One minor thing is that with the UPM temp sensor WT450 you show 0.1 degree lower than the display. Could be rounding I suppose.

I also tried the UPM wind meter and it shows up in EG as a WT450H, with the windspeed (-50 for no wind) in the temp field and the wind direction in the humidity field. If I recall, that was exactly the same in the NetHomeServer plugin, you could probably just copy/paste the code. I'd be happy to test it!

Great work as always Walter!

Cheers,
Michael

[krambriw]

Hi Mickelin,

Happy to hear you got everything working. Yes it is very impressive. With the latest plugin (I assume you are using the latest) you can try an interesting "stress-test": Send a command from EG at the same time as you press a button on a remote and you will interestingly see that most of the time, there is no collision at all. That's really good (you can enable debug in the plugin to see more details if you are interested)

One minor thing is that with the UPM temp sensor WT450 you show 0.1 degree lower than the display. Could be rounding I suppose.

Funny, I just had a discussion with RFXCOM about this issue. They made a change to the firmware to improve the rounding and it is better in the new version (not released yet).

You could probably just copy/paste the code. I'd be happy to test it!

I will dive into that old code and see how this can be fixed. Are all the data otherwise correctly logged as before, wind speed and direction?

Bets regards, Walter

[mickelin]

Yeah, I noticed the 0.1 diff also in RFXmgr, so clearly their issue. Mine was delivered with firmware 32, whereas the latest on their site is 31, so I guess no fix until 33 at the earliest.

I re-read the old NetHomeServer thread and from my very limited testing last night, it seems the values provided via RFXtrx for windspeed and direction are exactly the same as the ones Jostein mapped out. I will verify this with more structured testing in the weekend.

Cheers,
Michael

[krambriw]

Hi Michael,
When you are testing, first enable debug in the plugin and log some messages from the wind sensor so that I can see how the data looks like when it is coming from a wind sensor.
I think anyway that a new firmware version might be needed because with current implementation it is not possible for me to see the difference between a wind/rain sensor and a temp/hum sensor.
The way to do it is in the firmware to detect house code 10 and device code 2 and 3 which are reserved for wind and rain sensors.

Best regards, Walter

Code: Select all

            /*
             * My current understanding of the UPM data message:
             * The message consists of four bytes.
             *
             * c = House Code (0 - 15)
             * d = Device Code (1 - 4) ?
             * p = Primary value - Temperature/Rain/Wind speed value (low bits)
             * P = Primary value - Temperature/Rain/Wind speed value (high bits)
             * s = Secondary value - Humidity/Wind direction (low bits)
             * S = Secondary value - Humidity/Wind direction (high bits)
             * b = Low battery indication
             * x = ?
             * y = ?
             * z = ?
             * C = Some kind of checksum
             *
             * If HouseCode = 10 and deviceCode = 2, then p and P is Wind speed
             * and h and H is Wind direction
             *
             * If HouseCode = 10 and deviceCode = 3, then p and P is rain
             *
             * ____Byte 0_____  ____Byte 1_____  ____Byte 2_____  ____Byte 3_____  _Nib4__
             * 7 6 5 4 3 2 1 0  7 6 5 4 3 2 1 0  7 6 5 4 3 2 1 0  7 6 5 4 3 2 1 0  3 2 1 0
             * x x x x c c c c  d d y y b S S S  s s s s s P P P  p p p p p p p p  z z C C
             *                                           
             * Temp (C) = RawValue * 0.0625 - 50
             * Rain (total mm) = RawValue * 0,7
             * Wind Speed (mph)= RawValue (* 1/3,6 for km/h)
             * Humidity (%) = RawValue * 0.5
             * Wind direction (deg) = RawValue * 22,5
             *
             */
   

[mickelin]

Can you believe the guys at RFXCOM just sent me an updated firmware 34 with support for the UPM wind sensor without me even asking for it? Totally amazing! Proactive customer support at its best.

[krambriw]

Yes I know, they are really professional
Is it working?

Best regards, Walter

[mickelin]

I'm away on a business trip, won't be able to test until I get home tomorrow night. I'll post feedback and test results then.

[krambriw]

Hi Michael, when you are back and starting the testing, you should use this pre-release version of the plugin. I have added support for UPM/ESIC wind & rain sensors to match with the RFXtrx v34 firmware.

Best regards and good luck!

Walter

__init__.py

(157.17 KiB) Downloaded 332 times

[mickelin]

Just got home and too tired to do much tonight, but had to do a quick test. FW 34 works fine and picks up the wind sensor. So does your test version of the plugin, but I'm not sure about the direction values. I'll verify with a compass tomorrow.

You now show the same temp as the display, but the RFXmngr is still 0.1 below. Do you also see that?

[krambriw]

Have you tried with the latest RFXmngr?
Now go to sleep
BR Walter

[mickelin]

OK, did some testing and while not yet perfect, it looks promising.

I tested the wind direction sensor using a compass for calibration. Both RFXmngr and EG pick it up and display the same values, albeit not the correct one...

Compass RFXmngr EG
-------------------------------------------------------
0 degrees North 675 N 675
90 degrees East 180 S 180
180 degrees South 360 N / 315 NW 315
270 degrees West 495 N 495

Strangely, the south position is sometimes reported as 360, sometimes as 315. I haven't looked at your code, but I expect that you are just using the values that cone from the device, right? So the adjustments need to be made in the firmware. I'll report my findings also to RFXCOM.

The rounding diff still occurs sometimes, but I don't think the sensor is accurate to 0.1 anyway, so no big deal.

I'll figure out a way test the wind speed next.

Cheers,
Michael

[mickelin]

Bert at RFXCOM sent me a new firmware 35 and it shows correct wind direction now, and so does your plugin! Great. It would be nice if you also showed the direction in letters (N, NNE, NE, ENE, E, ESE, SE etc), not just the degrees.

I went to Clas Ohlson and bought the station today, so I will be able to test also the wind speed and the rain guage.

Great work so far!

[krambriw]

Michael,

Could you make some table showing what values you get from the plugin for the various wind directions (best also if you have the debug message there as well for each direction)?

Also as you remember, for the NetHome plugin we did some average calculations that was not handled by the device itself, like average wind speed, average rain levels.

I think that we should actually make a separate plugin for all these number crunching special formatting stuff, in this way keeping the RFXtrx plugin as clean as possible, just delivering the necessary events. Making such a plugin will be very simple.

If you could start thinking of what you need/wish to do with the data, I can start throwing a first version together.

Best regards, Walter