Yes, I did that, unfortunately no change. The view seems to change in time with the refresh time
It happened to me that all channels disappeared after a refresh time and reappeared after the next one, cyclically. I had to delete the thing, purge links and then recreate it.
I have noticed this behavior myself, all channels disappear and then reappear.
In the meantime, there are âHealth issues (19)â and 19 orphan links âŠ
I have only noticed this behavior since version 4.2
I seem to have been able to solve the problem today.
Apparently you canât just add sensors without rebuilding the weather station!
I deleted all items and things from the weather station and restarted OH. Then I created the weather station thing again. The âleaf moistureâ channel was there immediately. I was also offered the âoutdoor unitâ and âleaf moisture sensorâ things. Both things only with the âsignal strengthâ and âbattery statusâ channels.
I have another question about the wind speeds. The item is created as Number:Lenght. Shouldnât it be Number:Speed? Is the value provided km/h or m/s?
Here is an excerpt from the log file:
2024-07-23 18:14:55.890 [DEBUG] [ry.FineOffsetGatewayDiscoveryService] - Thing discovered 'DiscoveryResult [thingUID=fineoffsetweatherstation:gateway:3965870281, properties={macAddress=XX:XX:XX:XX:00:13, protocol=DEFAULT, port=45000, ip=192.168.137.85}, representationProperty=macAddress, flag=NEW, label=Wetterstation, bridgeUID=null, ttl=-1, timestamp=2024-07-23T16:14:55.886816834Z]'
2024-07-23 18:15:00.888 [DEBUG] [ry.FineOffsetGatewayDiscoveryService] - Thing discovered 'DiscoveryResult [thingUID=fineoffsetweatherstation:gateway:3965870281, properties={macAddress=XX:XX:XX:XX:00:13, protocol=DEFAULT, port=45000, ip=192.168.137.85}, representationProperty=macAddress, flag=NEW, label=Wetterstation, bridgeUID=null, ttl=-1, timestamp=2024-07-23T16:15:00.885870136Z]'
2024-07-23 18:15:16.356 [DEBUG] [nternal.service.FineOffsetDataParser] - unknown sensor (id=-1) for index 49
2024-07-23 18:24:55.891 [DEBUG] [ry.FineOffsetGatewayDiscoveryService] - Thing discovered 'DiscoveryResult [thingUID=fineoffsetweatherstation:gateway:3965870281, properties={macAddress=XX:XX:XX:XX:00:13, protocol=DEFAULT, port=45000, ip=192.168.137.85}, representationProperty=macAddress, flag=NEW, label=Wetterstation, bridgeUID=null, ttl=-1, timestamp=2024-07-23T16:24:55.888287140Z]'
2024-07-23 18:25:00.890 [DEBUG] [ry.FineOffsetGatewayDiscoveryService] - Thing discovered 'DiscoveryResult [thingUID=fineoffsetweatherstation:gateway:3965870281, properties={macAddress=XX:XX:XX:XX:00:13, protocol=DEFAULT, port=45000, ip=192.168.137.85}, representationProperty=macAddress, flag=NEW, label=Wetterstation, bridgeUID=null, ttl=-1, timestamp=2024-07-23T16:25:00.887585972Z]'
2024-07-23 18:30:16.368 [DEBUG] [nternal.service.FineOffsetDataParser] - unknown sensor (id=-1) for index 49
2024-07-23 18:34:55.892 [DEBUG] [ry.FineOffsetGatewayDiscoveryService] - Thing discovered 'DiscoveryResult [thingUID=fineoffsetweatherstation:gateway:3965870281, properties={macAddress=XX:XX:XX:XX:00:13, protocol=DEFAULT, port=45000, ip=192.168.137.85}, representationProperty=macAddress, flag=NEW, label=Wetterstation, bridgeUID=null, ttl=-1, timestamp=2024-07-23T16:34:55.889340751Z]'
2024-07-23 18:35:00.892 [DEBUG] [ry.FineOffsetGatewayDiscoveryService] - Thing discovered 'DiscoveryResult [thingUID=fineoffsetweatherstation:gateway:3965870281, properties={macAddress=XX:XX:XX:XX:00:13, protocol=DEFAULT, port=45000, ip=192.168.137.85}, representationProperty=macAddress, flag=NEW, label=Wetterstation, bridgeUID=null, ttl=-1, timestamp=2024-07-23T16:35:00.889306486Z]'
2024-07-23 18:44:55.893 [DEBUG] [ry.FineOffsetGatewayDiscoveryService] - Thing discovered 'DiscoveryResult [thingUID=fineoffsetweatherstation:gateway:3965870281, properties={macAddress=XX:XX:XX:XX:00:13, protocol=DEFAULT, port=45000, ip=192.168.137.85}, representationProperty=macAddress, flag=NEW, label=Wetterstation, bridgeUID=null, ttl=-1, timestamp=2024-07-23T16:44:55.891199552Z]'
2024-07-23 18:45:00.895 [DEBUG] [ry.FineOffsetGatewayDiscoveryService] - Thing discovered 'DiscoveryResult [thingUID=fineoffsetweatherstation:gateway:3965870281, properties={macAddress=XX:XX:XX:XX:00:13, protocol=DEFAULT, port=45000, ip=192.168.137.85}, representationProperty=macAddress, flag=NEW, label=Wetterstation, bridgeUID=null, ttl=-1, timestamp=2024-07-23T16:45:00.892302784Z]'
2024-07-23 18:45:16.382 [DEBUG] [nternal.service.FineOffsetDataParser] - unknown sensor (id=-1) for index 49
2024-07-23 18:54:55.897 [DEBUG] [ry.FineOffsetGatewayDiscoveryService] - Thing discovered 'DiscoveryResult [thingUID=fineoffsetweatherstation:gateway:3965870281, properties={macAddress=XX:XX:XX:XX:00:13, protocol=DEFAULT, port=45000, ip=192.168.137.85}, representationProperty=macAddress, flag=NEW, label=Wetterstation, bridgeUID=null, ttl=-1, timestamp=2024-07-23T16:54:55.893624752Z]'
2024-07-23 18:55:00.895 [DEBUG] [ry.FineOffsetGatewayDiscoveryService] - Thing discovered 'DiscoveryResult [thingUID=fineoffsetweatherstation:gateway:3965870281, properties={macAddress=XX:XX:XX:XX:00:13, protocol=DEFAULT, port=45000, ip=192.168.137.85}, representationProperty=macAddress, flag=NEW, label=Wetterstation, bridgeUID=null, ttl=-1, timestamp=2024-07-23T16:55:00.892698572Z]'
2024-07-23 19:00:16.395 [DEBUG] [nternal.service.FineOffsetDataParser] - unknown sensor (id=-1) for index 49
Hi,
I have the ELV WiFI-Wetterstation WS980WiFi, working fine with Fine Offset Weather Station Binding in delivering the weather data.
Checking the latest description of the binding, I have seen, that the binding is now supporting HW information batteryLevel, signal, batteryVoltage and lowBattery. I have checked all sensor types supported for a 7-in-1 sensor. The thing is green an working, having all the channels listed above, but shows for all channels the value UNDEF.
Is my weather station unsupported for these channels or what is my supported sensor?
I have a Ecowitt WittBoy - GW2000 and WS90. Almost everything runs fine, except the solar irradiance. If I enable trace debug level I get the following logs.
0xFFFF : header
0x27 : command: CMD_GW1000_LIVEDATA
0x002F : size
0x01 : measurand INTEMP
0x00E2 : TEMPERATURE: 22.6 °C
0x06 : measurand INHUMI
0x29 : PERCENTAGE: 41 %
0x08 : measurand ABSBARO
0x2715 : PRESSURE: 1000.5 hPa
0x09 : measurand RELBARO
0x2715 : PRESSURE: 1000.5 hPa
0x02 : measurand OUTTEMP
0x0020 : TEMPERATURE: 3.2 °C
0x07 : measurand OUTHUMI
0x56 : PERCENTAGE: 86 %
0x0A : measurand WINDDIRECTION
0x0020 : DEGREE: 32 °
0x0B : measurand WINDSPEED
0x0000 : SPEED: 0 m/s
0x0C : measurand GUSTSPEED
0x000F : SPEED: 1.5 m/s
0x15 : measurand LIGHT
0x0000D930: LUX: 5560 lx
0x16 : measurand UV
0x0000 : MILLIWATT_PER_SQUARE_METRE: 0 mW/mÂČ
0x17 : measurand UVI
0x00 : BYTE: 0
0x19 : measurand DAYLWINDMAX
0x002A : SPEED: 4.2 m/s
0x6C : measurand ITEM_HEAP_FREE
0x000240B4: MEMORY: 147636 B
0xB0 : checksum
as you see, the MILLIWATT_PER_SQUARE_METRE is zero.
additionally I enabled mqtt on the ecowitt gateway and in this way I get the correct irradiance value
ecowitt/8813BF4638DF PASSKEY=XXX&stationtype=GW2000A_V3.1.8&runtime=87660&heap=143636&dateutc=2024-12-23%2011%3A03%3A30&tempinf=72.50&humidityin=41&baromrelin=29.542&baromabsin=29.542&tempf=37.76&humidity=85&winddir=25&windspeedmph=4.47&windgustmph=5.82&maxdailygust=9.39&solarradiation=42.07&uv=0&rrain_piezo=0.024&erain_piezo=0.063&hrain_piezo=0.008&drain_piezo=0.020&wrain_piezo=0.268&mrain_piezo=0.327&yrain_piezo=0.327&srain_piezo=1&ws90cap_volt=2.4&ws90_ver=146&wh90batt=3.18&freq=868M&model=GW2000A&interval=0
has anyone an idea
I purchased a new Steinberg weather station (SBS-WS-300) and was hoping that I can easily integrate it the openHAB using the Fine Offset Weather Station Binding.
I updated the display/gateway to the newest available firmware Version: EasyWeatherPro_V5.1.9
Unfortunately the gateway-THING connection is toggling from ONLINE to OFFLINE all the time and is getting read timeouts.
The binding is install and the gateway is configured. Some communication is happening as the THING ready out the modelId, MAC and firmwareVersion correctly and displays it:
* Information
* Ein mit WiFi verbundenes Gateway-GerÀt (WN1900, GW1000, GW1100, WH2680, WH2650) zur Verbindung von Sensoren
* modelId EasyWeatherPro
* macAddress 08:F9:E0:71:44:44
* firmwareVersion 5.1.9
The IP and port is correct and the port 45000 is available on the gateway
Starting Nmap 7.80 ( https://nmap.org ) at 2025-03-13 14:06 CET
Nmap scan report for 10.10.10.10
Host is up (0.020s latency).
Not shown: 58000 closed ports
PORT STATE SERVICE
45000/tcp open asmp
Trace
|18:50:17.167|WARN|org.openhab.core.thing.internal.ThingManagerImpl|Initializing handler for thing 'fineoffsetweatherstation:gateway:150593444' takes more than 5000ms.|
| --- | --- | --- | --- |
|18:53:31.327|TRACE|org.openhab.binding.fineoffsetweatherstation.internal.service.FineOffsetGatewayQueryService|executeCommand(CMD_READ_SENSOR_ID_NEW): send request: FFFF3C033F|
|18:53:36.320|WARN|org.openhab.core.thing.internal.ThingManagerImpl|Initializing handler for thing 'fineoffsetweatherstation:gateway:150593444' takes more than 5000ms.|
|18:53:36.340|TRACE|org.openhab.binding.fineoffsetweatherstation.internal.service.FineOffsetGatewayQueryService|executeCommand(CMD_READ_FIRMWARE_VERSION): send request: FFFF500353|
|18:53:36.358|DEBUG|org.openhab.binding.fineoffsetweatherstation.internal.service.FineOffsetGatewayQueryService|executeCommand(CMD_READ_FIRMWARE_VERSION), invalid response: FFFF501915456173795765617468657250726F5F56352E312E39|
|18:53:36.361|TRACE|org.openhab.binding.fineoffsetweatherstation.internal.service.FineOffsetGatewayQueryService|executeCommand(CMD_READ_SSSS): send request: FFFF300333|
|18:53:41.371|DEBUG|org.openhab.binding.fineoffsetweatherstation.internal.service.FineOffsetGatewayQueryService|Unexpected response to System Info!|
|18:53:41.381|TRACE|org.openhab.binding.fineoffsetweatherstation.internal.service.FineOffsetGatewayQueryService|executeCommand(CMD_READ_SENSOR_ID_NEW): send request: FFFF3C033F|
|18:53:46.399|TRACE|org.openhab.binding.fineoffsetweatherstation.internal.service.FineOffsetGatewayQueryService|executeCommand(CMD_GW1000_LIVEDATA): send request: FFFF27032A|
|18:53:51.415|TRACE|org.openhab.binding.fineoffsetweatherstation.internal.service.FineOffsetGatewayQueryService|executeCommand(CMD_READ_RAIN): send request: FFFF57035A|
Does anybody have an idea why I am getting the âUnexpected response to System Infoâ error?
The âWSView appâ is officially supported by this product and as per @Andy2003 hint in the initial post, I was hoping that this sign is enough to also get the binding connection up and running.
Did anyone find a solution for the rain-hour rate? It still reports â10mmâ
The 3.4.4 binding really is âwonkyâ when adding new devices. Iâm working with two Ecowitt gateways: a GW3000 and a WN1980. Iâve observed frustrating behavior when adding new devices to both gateways, each a proper Thing.
The best way to describe the way the Thing handles the addition of devices is âschizophrenicâ. Existing channels disappear from the All Channels display, formerly working links are reported as â(unknown invalid link)â and channels for new devices appear in different locations (All, Linked, Unlinked).
I think I tried restarting OH to reset the device but that didnât help. The only way to straighten out the Thing was to recreate it.
Suggestions for fancy tricks like âdisable the bindingâ arenât really helpful. One of the gateways is correctly configured and logging production data. The problematic gateway is also logging and being polled by a production app.
Having to recreate the Thing requires temporarily removing channels from logging and modifying production code to ignore temporarily âphantomâ channel values. On top of that Iâm using JDBC logging so thereâs no guarantee about how the table names and numbers will be reassigned once the Thing is rebuilt (although I was pleasantly surprised the last time I had to do this.)
I think this is disruptive enough that it deserves a bug report. I canât find any open bugs for the binding.
Did you find out what caused it?
Iâve had the same or a similar problem since yesterday.
OH 4.3.5
WH2650 FW 1.7.8
A WH51 was put into operation (only the battery inserted).
Since then, the channels associated with the gateway have been jumping back and forth between the weather station and the one sensor.
The only thing that helped was to put the sensor out of operation again.
I have already tried the following:
Restarting the gateway and Openhab
Activating and deactivating the gateway in OA
Any other ideas or anyone who has also experienced this phenomenon and found a solution?
1 Like
When it happened something similar to my installation, some time ago, I uninstalled and reinstalled the things. Donât remember if I also cleaned cache in between.
You could try to set up temporarily a new installation with only that binding
Clean cache or/and restart didnâs help.
Reinstalling the binding solved the problem. Thank you very much.
Unfortunately, the same weather station then appears under a new UID and all channels have to be relinked.
The old UID of the weather station remains online and continues to provide values, but jumps back and forth as described above.
So it seems to me to be a problem with the binding.
Hi @MWerk - Did you ever find the solution to your issue?
My original weather station ended up dying, so replaced it with a TESA WS2980C (fairly commonly for sale in NZ) , which they state is the same as the WS2900. Basically just another fine offset rebadged unit.
Mine also does similar things as yours (However, FYI - This is on OpenHAB 5.0.1):
- Responds ok to port 45000
- Works ok with both WS View & WS View Plus apps
- I did have to manually add the thing for the gateway, as the OpenHAB server and gateway are in different subnets (Firewall separated), which is expected behaviour that discovery would not work
- And then, just like yours, it is continually bouncing between Online & offline, with similar log entries:
2025-10-28 21:51:45.300 [TRACE] [ervice.FineOffsetGatewayQueryService] - executeCommand(CMD_READ_SENSOR_ID_NEW): send request: FFFF3C033F
2025-10-28 21:51:50.297 [WARN ] [core.thing.internal.ThingManagerImpl] - Initializing handler for thing 'fineoffsetweatherstation:gateway:fnlweather' takes more than 5000ms.
2025-10-28 21:51:50.306 [TRACE] [ervice.FineOffsetGatewayQueryService] - executeCommand(CMD_READ_FIRMWARE_VERSION): send request: FFFF500353
2025-10-28 21:51:50.346 [DEBUG] [ervice.FineOffsetGatewayQueryService] - executeCommand(CMD_READ_FIRMWARE_VERSION), invalid response: FFFF501915456173795765617468657250726F5F56352E322E32
2025-10-28 21:51:50.347 [TRACE] [ervice.FineOffsetGatewayQueryService] - executeCommand(CMD_READ_SSSS): send request: FFFF300333
2025-10-28 21:51:55.349 [DEBUG] [ervice.FineOffsetGatewayQueryService] - Unexpected response to System Info!
2025-10-28 21:51:55.354 [TRACE] [ervice.FineOffsetGatewayQueryService] - executeCommand(CMD_READ_SENSOR_ID_NEW): send request: FFFF3C033F
2025-10-28 21:52:00.366 [TRACE] [ervice.FineOffsetGatewayQueryService] - executeCommand(CMD_GW1000_LIVEDATA): send request: FFFF27032A
2025-10-28 21:52:05.377 [TRACE] [ervice.FineOffsetGatewayQueryService] - executeCommand(CMD_READ_RAIN): send request: FFFF57035A
2025-10-28 21:52:26.399 [TRACE] [ervice.FineOffsetGatewayQueryService] - executeCommand(CMD_GW1000_LIVEDATA): send request: FFFF27032A
2025-10-28 21:52:31.417 [TRACE] [ervice.FineOffsetGatewayQueryService] - executeCommand(CMD_READ_RAIN): send request: FFFF57035A
2025-10-28 21:52:52.427 [TRACE] [ervice.FineOffsetGatewayQueryService] - executeCommand(CMD_GW1000_LIVEDATA): send request: FFFF27032A
2025-10-28 21:52:57.439 [TRACE] [ervice.FineOffsetGatewayQueryService] - executeCommand(CMD_READ_RAIN): send request: FFFF57035A
I have fallen back to using the IP Observer binding for now, but had hoped to use the Fine Offset Binding, to get some additional data available in OpenHAB (e.g. Battery Levels etc).
Cheers
Hello @glen_m,
I was not able to resolve the problem and just finally accepted that the specific WS model I picked is not supported. Sorry that I have no better news for you.
Not wanting to barge in this Fine Offset Weather Station Binding thread, but your SBS-WS-300 looks to be the same FineOffset clone as my Froggit WH3000 unit, which I purchased without any receiving station. I directly receive the RF signals from the weather station with a small LilyGo T3 LoRa32 V1.6.1 board running an rtl_433 OpenMQTTGateway firmware - receivable in openHAB through the MQTT binding with auto-discovery in openHAB 4.3.0 or later.
The important issues are to get the correct 433/470 or 868/915 MHz version of the LilyGo to match the weather station, and a placement not too far away from the station to correctly receive the signals, in case you might want to try this alternative for openHAB integration.
Thanks for the reply @MWerk. I have re-read this and other threads in further detail now, and looks like it was a known issue all along (for my scenario anyway) - Gateways with the displays donât seem to work the same, and the proposed solution is to use the GW1100/GW1200 type device in parallel to the existing display.
In hindsight, this is probably a good solution for my needs, as I can then locate the GW1200 in a utility room (no display to look at), and also connect it to an essential (UPS Protected) power circuit to act as the OpenHAB gateway. This has the added bonus of providing Temp/Humidity monitoring for this room.
I can then leave the existing display unit in the Living Areas, but this will be a display-only, and not form any part of the OpenHAB integration.
Have ordered a GW1200 from Aliexpress (433MHz for my corner of the world), and at around USD$40 including shipping and tax, probably the easiest/most-robust approach for usâŠ.
Our weather station/OpenHAB integration includes a slightly âmission criticalâ application - The information is used to limit greenhouse vent opening based on Average Wind Speeds, and Wind Direction, or even completely close them when the gusts exceed pre-set thresholds. A pair of linear motors for my home-brew openers costs about the same as the gateway, as I have found out once before when the thresholds were adjusted too high (Destructive Testing !!), hence my willingness to get the gateway
I will report back here, once I have received & tested the new gateway, with this weather station & OpenHAB.