Eurotronic Spirit Zwave Plus thermostats not being initialized


(Daniel Hazelzet) #1
  • Platform information:
    • Hardware: RBPi 3 Plus
    • OS: Openhabian 1.13.0 snapshot or 2.4 stable
    • Java Common 0.58 Runtime Environment:and nodejs 8.11.3-1nodesource1
  • Issue: Eurotronic Spirit Zwave Plus thermostats not being initialized, Openhab2 reporting the Zwave thermostats as unknown. The database lists an entry “Spirit Thermostatic valve”.

    However I am not able to get the “Unknown” issue fixed.
    I tried two USB Zwave controllers, but the final result is the same.
    Here’s the relevant excerpt of the log file:
    2018-07-20 16:14:08.421 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
    2018-07-20 16:14:08.469 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node10’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
    2018-07-20 16:14:08.478 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node10’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
    2018-07-20 16:14:08.480 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node10’ has been updated.
    2018-07-20 16:14:24.057 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node2’ has been updated.
    2018-07-20 16:14:24.063 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
    2018-07-20 16:14:24.099 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node2’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
    2018-07-20 16:14:24.113 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node2’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
    2018-07-20 16:14:24.117 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node2’ has been updated.
    2018-07-20 16:14:39.826 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node3’ has been updated.
    2018-07-20 16:14:39.832 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
    2018-07-20 16:14:39.875 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node3’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
    2018-07-20 16:14:39.880 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node3’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
    2018-07-20 16:14:39.887 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node3’ has been updated.
    2018-07-20 16:14:54.119 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node4’ has been updated.
    2018-07-20 16:14:54.123 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
    2018-07-20 16:14:54.176 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node4’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
    2018-07-20 16:14:54.183 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node4’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
    2018-07-20 16:14:54.189 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node4’ has been updated.
    2018-07-20 16:15:07.180 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node5’ has been updated.
    2018-07-20 16:15:07.185 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
    2018-07-20 16:15:07.236 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node5’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
    2018-07-20 16:15:07.241 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node5’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
    2018-07-20 16:15:07.245 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node5’ has been updated.
    2018-07-20 16:15:22.695 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node6’ has been updated.
    2018-07-20 16:15:22.701 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
    2018-07-20 16:15:22.759 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node6’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
    2018-07-20 16:15:22.762 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node6’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
    2018-07-20 16:15:22.765 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node6’ has been updated.
    2018-07-20 16:15:33.528 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node7’ has been updated.
    2018-07-20 16:15:33.535 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
    2018-07-20 16:15:33.568 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node7’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
    2018-07-20 16:15:33.572 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node7’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
    2018-07-20 16:15:33.585 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node7’ has been updated.
    2018-07-20 16:15:45.552 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node8’ has been updated.
    2018-07-20 16:15:45.556 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
    2018-07-20 16:15:45.651 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node8’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
    2018-07-20 16:15:45.663 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node8’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
    2018-07-20 16:15:45.670 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node8’ has been updated.
    2018-07-20 16:15:58.796 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node9’ has been updated.
    2018-07-20 16:15:58.799 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
    2018-07-20 16:15:58.913 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node9’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
    2018-07-20 16:15:58.917 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node9’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
    2018-07-20 16:15:58.925 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node9’ has been updated.
    2018-07-20 16:16:36.836 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
    2018-07-20 16:16:36.869 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
    2018-07-20 16:16:36.891 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
    2018-07-20 16:16:36.908 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
    2018-07-20 16:16:36.916 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
    2018-07-20 16:16:36.925 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
    2018-07-20 16:16:36.933 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
    2018-07-20 16:16:36.941 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
    2018-07-20 16:16:36.949 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
    2018-07-20 16:16:36.975 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@1f50209
    2018-07-20 16:16:36.982 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_ack changed from 126 to 127
    2018-07-20 16:16:36.985 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_sof changed from 203 to 204
    2018-07-20 16:17:06.816 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_ack changed from 127 to 128
    2018-07-20 16:17:06.968 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_sof changed from 204 to 205
    2018-07-20 16:17:06.973 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@f79c53

I did browse both this and the Eutronics forums, but can’t resolve this issue so far.
My ultimate goal is to control the installed 9 Spirit Zwave Plus thermostats with my RBPi 3 plus.
Additionally, I hope to achieve a connection with my OTGW, and from there to/from my Remaha unit using opentherm .

Thanks!


(SiHui) #2

Check this

and please use code fences:


(Daniel Hazelzet) #3

Hey Sihui,

Thanks for the quick response.

I’m having trouble to understand your replies.

  About the bindings, I only have my serial zwave stick listed there.

  I disabled all Openhab 1.3 bindings, so I am using the latest 2.4 snapshot for Zwave.

I did browse the two links you gave me earlier and once again.

  I guess, my problem is that those links don't indicate in detail what the practical steps are.

  I have two Zwave sticks, but both of them give me the same "unknown device" upon initializing my 9 Spirit Zwave plus thermostats in the end.

I’d appreciate any more detailed help.

  Thanks

(SiHui) #4

The answer is in the first sentence of the first link:

Please use the latest binding, and check the debug logs during the binding initialisation to see if there are any errors during the thing handler initialisation.

If you already are using the latest snapshot, try waking up your thermostats. Take a look at the manual on how to do that.

The code fences were meant for your logs, not for your replies.

It is easer to read:

2018-07-20 16:14:08.421 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
2018-07-20 16:14:08.469 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node10’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2018-07-20 16:14:08.478 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node10’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2018-07-20 16:14:08.480 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node10’ has been updated.
2018-07-20 16:14:24.057 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node2’ has been updated.
2018-07-20 16:14:24.063 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
2018-07-20 16:14:24.099 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node2’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2018-07-20 16:14:24.113 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node2’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2018-07-20 16:14:24.117 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node2’ has been updated.
2018-07-20 16:14:39.826 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node3’ has been updated.

(Daniel Hazelzet) #5

Hi Sihui,
Once again, I’m not understanding your suggestions.
I need you to give me a step by step instruction.

The latest binding as confirmed earlier is with Openhab V2.4.0 build #1313
Still unsure what you mean with code fences, r u referring to the log?

I tried removing a zwave sensor and adding it according to the manual. I see no difference. Please see the log excerpt.

Cheers, Daniel

2018-07-23 19:08:05.855 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node2’ changed from ONLINE to REMOVING
2018-07-23 19:08:05.864 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node2’ changed from REMOVING to REMOVED
2018-07-23 19:08:05.897 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node2’ changed from REMOVED to UNINITIALIZED
2018-07-23 19:08:06.060 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node2’ changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)

==> /var/log/openhab2/openhab.log <==
2018-07-23 19:08:28.311 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-07-23 19:08:28.338 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:4d6d4e4e:node2’ to inbox.

==> /var/log/openhab2/events.log <==
2018-07-23 19:08:28.345 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:4d6d4e4e:node2’ has been added.

==> /var/log/openhab2/openhab.log <==
2018-07-23 19:08:28.358 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-07-23 19:08:28.376 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-07-23 19:08:28.394 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-07-23 19:08:28.409 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-07-23 19:08:28.419 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-07-23 19:08:28.428 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-07-23 19:08:28.437 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-07-23 19:08:28.446 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0

==> /var/log/openhab2/events.log <==
2018-07-23 19:08:28.460 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_ack changed from 142 to 143
2018-07-23 19:08:28.462 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@1657979
2018-07-23 19:08:28.465 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_sof changed from 245 to 246
2018-07-23 19:08:53.900 [me.event.InboxRemovedEvent] - Discovery Result with UID ‘zwave:device:4d6d4e4e:node2’ has been removed.
12018-07-23 19:08:53.933 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node2’ changed from UNINITIALIZED to INITIALIZING
12018-07-23 19:08:53.936 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node2’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
112018-07-23 19:08:53.946 [hingStatusInfoChangedEvent] - ‘zwave:device:4d6d4e4e:node2’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2018-07-23 19:08:53.950 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node2’ has been updated.
2018-07-23 19:08:53.959 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4d6d4e4e:node2’ has been updated.
2018-07-23 19:08:58.312 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_ack changed from 143 to 144
2018-07-23 19:08:58.462 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_sof changed from 246 to 247
2018-07-23 19:08:58.469 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@44dfbd
2018-07-23 19:11:35.405 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_ack changed from 144 to 145
2018-07-23 19:11:35.412 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_sof changed from 247 to 248
2018-07-23 19:11:38.881 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_sof changed from 248 to 249
2018-07-23 19:11:38.908 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_ack changed from 145 to 146
2018-07-23 19:11:38.915 [vent.ItemStateChangedEvent] - zwave_serial_zstick_4d6d4e4e_serial_sof changed from 249 to 250


(SiHui) #6

Yes.

Without code fences:

2018-07-23 19:08:28.311 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-07-23 19:08:28.338 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:4d6d4e4e:node2’ to inbox.

With code fences:

2018-07-23 19:08:28.311 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-07-23 19:08:28.338 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:4d6d4e4e:node2’ to inbox.

Which one is easier to read???

This means your thermostat did not finish initialization. Either it is too far away from the controller or you did not wake up the device.
So please again: wake it up. That does not mean remove the Thing and readd it, that means read the manual and look for “Wake Up Signal” or “Node Information Frame”. Normally you have to push a button, sometimes once, sometimes a couple of times. I don’t have any Eurotronic devices, so you need to find out (in your manual) how to wake it up.


(Daniel Hazelzet) #7

OK, got it. The Eurotronic manual didn’t state a wake up, but I found it.

Thanks for your patience :wink:


(SiHui) #8

Now it would be a good idea to check the database information about inclusion if those are correct:

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/710

Start Inclusion mode of your primary Z-Wave Controller. Press the Boost-Button. Spirit Z-Wave Plus will show the assigned NodeID.


(Daniel Hazelzet) #9

Yup, got that. I’ve seen most of the values locally as listed in the Jackson DB.

  Earlier,  I had a few thermostats re-initialized, and showing up well. So I tried to add them to the HABpanel, which was successful, listing current temp, thermostat mode, etc.

  Right now, I can't get that to work again. I am now struggling to establish that for all 9 thermostats.

  If I set the Lifeline to the Zwave serial controller within any Zwave node, it's not activated somehow.

  <img src="//community-openhab-org.s3-eu-central-1.amazonaws.com/original/3X/5/5/556e9ee60431ca519d72115ffa398ed3f52759d2.png" alt="">

  What am i missing here?

Thanks again, will get back later.