Z-Wave Popp Thermostatic Valves, Raszberry 2 - beginner's question on odd behavior

Dear all,
I am new to openHAB and, as a first small project, trying to control

  • eight new Popp Wireless Thermostatic Valve TRV.

For that purpose I have yesterday set up

  • a Raspberry Pi 4 with
  • a Razberry 2 Z-Wave board
    and installed
  • OpenHAB2 (initially going for the demo config)
    resulting in

Release = Raspbian GNU/Linux 10 (buster)
Kernel = Linux 5.4.51-v7l+
Platform = Raspberry Pi 4 Model B Rev 1.1
Uptime = 0 day(s). 8:10:46
CPU Usage = 1.75% avg over 4 cpu(s) (4 core(s) x 1 socket(s))
CPU Load = 1m: 0.00, 5m: 0.01, 15m: 0.00
Memory = Free: 2.99GB (79%), Used: 0.79GB (21%), Total: 3.78GB
Swap = Free: 2.58GB (100%), Used: 0.00GB (0%), Total: 2.58GB
Root = Free: 8.88GB (64%), Used: 4.83GB (36%), Total: 14.32GB
Updates = 0 apt updates available.
Sessions = 0 session(s)
Processes = 118 running processes of 32768 maximum processes

openHAB 2.5.8-1 (Release Build)

After configuring the Razberry 2 with the native zwave binding, I was able to add the Popp Thermostatic Valves as Things.

So far so good, here comes what I find odd:

  • In the PaperUI control section, I can see information for the Thermostatic Valves, but only very rarely/exceptionally the real values (temperature etc.) are shown - usually for all values, -NaN is shown:
  • When I edit the configuration of the Thermostatic Valves in PaperUI things (e.g. the name, location etc.) those changes seem to be initially accepted / taken over, but when coming back a couple of minutes later, the values might have been reset to the previous values.

I cannot imagine that this is normal - does anybody have an idea why it happens?

From my layman’s view I find it strange that in the thing properties I can read that

zwave_lastwakeup 2020-08-26T22:10:19Z

although now it’s 2020-08-27T07:41 and I have tried to set the wakeup interval to 900 sec for all Thermostats…

So far, I have not set up any items, sitemaps etc. as I want to clarify the issues described above first.

Have a great day everyone!

1 Like

Here is how the control section typically looks like for a Thermostat:

… and very rarely, the real values from the thermostat are displayed:

Welcome

I do not know the answer but the Paper UI is only used for administration of OpenHAB, not fir daily monitoring. Set up a sitemap and use the Basic UI fir that. The Paper UI is gone from the new upcoming OH3.

1 Like

I’ve some of these devices up and running since two years. Quite the same config and they are doing their job flawlessly.

I think your devices are not fully discovered yet. This is a common problem with battery driven devices and people (like me :wink: ) being impatient. Try to press the “wakeup button” (middle, below display) several times of one of the devices shown NaN.
If nothing changes after a while, remove the device/thing from paperui an rediscover it. Press “wakeup” several times. Wait an other while for real values to show up.

EDIT: Raspbian is 64bit? Otherwise 8GB mem might be a problem.

2 Likes

Thanks @yab, I am trying out your tips at the moment.
The openHABian I installed yesterday was 1.5, which, according to https://github.com/openhab/openhabian/releases/tag/v1.5 supports the RPi 4 - I am assuming that this is 64 bit.

I see mention of issues in the 8GB version mentioned in the alpha version here.

EDIT: I adjusted the thread tags to attract more information about this.

Thanks @Bruce_Osborne, I quickly defined basic items and a sitemap and looked at the graphical representation in the SimpleUI. The result is corresponding to the PaperUI Control section - for the Items where PaperUI shows -NaN, Simple UI shows a hyphen:


(sorry, as a newbee I am only allowed to post one screenshot here)

BTW, the RPi 4 in use here has 4GB RAM.

1 Like

4GB is fine with obenHABian 1.5.

Whereever you look at: it should show the same as paperui at the end.

I’m still quite sure you are facing a discovery issue.

PS: when you post your config next time, you’d better write “openHABian 1.5” - not “Raspbian blablabla”. You might even have installed raspbian / Raspberry Pi OS and openHAB on top of that one otherwise.

1 Like

@yab & @Bruce_Osborne - thank you! - Your combined advice helped me to overcome the issue. I must say I could hardly believe that this would work, but indeed, every time I pressed the button on one of the Popp Thermostatic valves again, more discovery related entries were added to the log:

2020-08-27 18:30:11.699 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:Razberry2:node9' to inbox.
2020-08-27 18:30:11.700 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:Razberry2:node9' has been added.
2020-08-27 18:30:22.370 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:Razberry2:node9' has been removed.
2020-08-27 18:30:22.391 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from UNINITIALIZED to INITIALIZING
2020-08-27 18:30:22.425 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2020-08-27 18:30:22.436 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to UNINITIALIZED
2020-08-27 18:30:22.481 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2020-08-27 18:30:22.528 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2020-08-27 18:30:22.553 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2020-08-27 18:30:22.557 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2020-08-27 18:30:22.573 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:30:22.582 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:30:22.591 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:30:22.600 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:30:22.605 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:30:22.611 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_Razberry2_node9_sensor_temperature-zwave:device:Razberry2:node9:sensor_temperature' has been added.
2020-08-27 18:30:22.619 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_Razberry2_node9_thermostat_setpoint_heating-zwave:device:Razberry2:node9:thermostat_setpoint_heating' has been added.
2020-08-27 18:30:22.625 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_Razberry2_node9_battery_level-zwave:device:Razberry2:node9:battery-level' has been added.
2020-08-27 18:30:22.638 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_Razberry2_node9_time_offset-zwave:device:Razberry2:node9:time_offset' has been added.
2020-08-27 18:31:57.302 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.

2020-08-27 18:32:00.849 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from ONLINE to ONLINE: Node initialising: ENDPOINTS
2020-08-27 18:32:00.855 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from ONLINE: Node initialising: ENDPOINTS to ONLINE: Node initialising: UPDATE_DATABASE
2020-08-27 18:32:00.864 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from ONLINE: Node initialising: UPDATE_DATABASE to ONLINE: Node initialising: STATIC_VALUES
2020-08-27 18:32:05.415 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:32:14.177 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:32:29.941 [.ItemChannelLinkAddedEvent] - Link 'Buero_Temp_HK-zwave:device:Razberry2:node9:sensor_temperature' has been added.
2020-08-27 18:32:29.943 [.ItemChannelLinkAddedEvent] - Link 'Buero_HK_Thermostat_Batt-zwave:device:Razberry2:node9:battery-level' has been added.
2020-08-27 18:32:29.945 [.ItemChannelLinkAddedEvent] - Link 'Buero_HK_ZielT-zwave:device:Razberry2:node9:thermostat_setpoint_heating' has been added.
2020-08-27 18:34:20.716 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:35:24.984 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:35:30.283 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from ONLINE: Node initialising: STATIC_VALUES to ONLINE: Node initialising: ASSOCIATIONS
2020-08-27 18:35:30.286 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from ONLINE: Node initialising: ASSOCIATIONS to ONLINE: Node initialising: SET_WAKEUP
2020-08-27 18:35:51.868 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:35:57.909 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:35:57.919 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from ONLINE: Node initialising: SET_WAKEUP to ONLINE: Node initialising: SET_ASSOCIATION
2020-08-27 18:35:57.922 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from ONLINE: Node initialising: SET_ASSOCIATION to ONLINE: Node initialising: SET_LIFELINE
2020-08-27 18:35:57.925 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node9' changed from ONLINE: Node initialising: SET_LIFELINE to ONLINE: Node initialising: GET_CONFIGURATION
2020-08-27 18:36:06.755 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.
2020-08-27 18:36:14.332 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node9' has been updated.

Here is the result:

Thanks again and have a nice evening!

1 Like

Fine. :slight_smile:

Keep this in mind an remember when you are going to discover the next battery powered device.

1 Like