[Solved] Strange Values for LaCrosse Sensor

jeelink
lacrosse
Tags: #<Tag:0x00007f015a2f4588> #<Tag:0x00007f015a2f4448>

(Christian) #1

Hi all,

I am running OH 2.3.0.005 on a synology ds 918+. and I finally got a Jeelink V3 working and added 3 LaCrosse Temp Sensors. Those are included in my sitemap and seemed to work quite well.
But I just noticed that the value displayed for the outdoor sensor switches between correct value and the value of the living room sensor every 20-30 seconds.
When I look at the Control in Paper UI it shows two values, the one created automatically through Paper UI (Temperature)and the one I’ve defined in my items file (Außen). The system generated item stays on the correct value while the one from the items file alternates between correct value and value from the living room sensor.
Any ideas what is happening here?

Thanks,

Christian

grafik
grafik

Number:Temperature Temperatur_OD "Außen [%.1f %unit%]" <temperature> (Temp) {channel="jeelink:lacrosse:33:temperature"}

(Jonas Neumann) #2

I don’t think it’s the case but might it be possible that the “Außen” Sensor has the same ID as the Indoor sensor?


(Christian) #3

Hi Jonas,

I already checked the IDs and channels, everything correct. If the sensor would have the same ID I would also expect issues with the indoor sensor.

However, the living room sensor was there first and I added the outdoor sensor by copying the lines in the items file and updating the names. I forgot to update the channel initially and changed that later, when I realized it was showing the wrong values.
Maybe theres is a kind of an old instance of the item still active somewhere in the background.
I’ll restart openHAB when I am back home and see if that changes anything.

Regards,

Christian


(Christian) #4

Ok, restarted openHAB on the diskstation and the problem seems to be gone.:frowning:
“Have you tried turning it off and on again?” … should have tried that earlier. Anyway, maybe the description of the issue is usefull for someone. :grinning:


(CM6.5 H102) #5

Yep, sometimes you may need to clean the cache and tmp files to rid the system of old instances. In your case a simple restart did the trick.:+1:

If you would, please mark the post solved by clicking the square box (lower right corner) on the post that contains the solution. Also edit the title to add [Solved] at the start, this will help others with a similar issue find a quick solution.

Thanks