Again. zWave is broken. I’ve never had so much trouble with software.
Running the latest cut of openhab 2.4 (I’m continually installing the latest in an effort to at least try and find 1 version that’s even partially capable of working - yeah, chasing my tail on endless betas. You can put that on my tombstone but the ‘stable’ versions have proven to be anything but for me in the past).
After a power cut back in August (I was away at a funeral) it’s just never worked properly. Random devices dropped out, and although some came back after restarting openhab. Unfortunately a couple were just never able to be switched. Although they still appear in the zWave network.
Last night I took the step of shutting down openhab, removing all the xml files from /var/lib/openhab2/zwave and restarting. As
It initially looks promising. New files of the form network_id__node_nodeid.xml were created. But it was exceedingly slow. After 2 hours I had about 15 of them and went to bed with the PaperUI showing all my zWave devices as uninitialised.
This morning, not a lot has changed. All the xml’s are timestamped with around 0200 (Which is about the time my openhab restarts due to incessant memory leaks). and PaperUI says nothing has initialised.
Restarting does nothing except a few random errors telling me that openhab zWave is unable to load some files that IT HAS CEATED ITSELF due to the data being invalid. e.g.
018-10-02 07:23:53.441 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 12: Restore from config: Error. Data invalid, ignoring config.
2018-10-02 07:23:53.479 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 11: Not initialized (ie node unknown), ignoring message.
2018-10-02 07:23:53.458 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 3: Restore from config: Error. Data invalid, ignoring config.
2018-10-02 07:23:53.453 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 28: Restore from config: Error. Data invalid, ignoring config.
2018-10-02 07:23:53.482 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 8: Restore from config: Error. Data invalid, ignoring config.
Needless to say nothing works. No stats are being updated, even though if I enable debugging and watch the logs, plenty of updates are coming in from the devices.
2018-10-02 07:41:27.700 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 14 00 04 00 09 0E 32 02 21 34 00 00 06 B3 00 00 00 00 00 00 78
2018-10-02 07:41:27.728 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 0E 32 02 21 34 00 00 06 B3 00 00 00 00 00 00
2018-10-02 07:41:27.733 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 0E 32 02 21 34 00 00 06 B3 00 00 00 00 00 00
2018-10-02 07:41:27.735 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 237: [WAIT_REQUEST] priority=Poll, requiresResponse=true, callback: 185
2018-10-02 07:41:27.736 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Application Command Request (ALIVE:DONE)
2018-10-02 07:41:27.738 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: resetResendCount initComplete=true isDead=false
2018-10-02 07:41:27.739 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Incoming command class COMMAND_CLASS_METER, endpoint 0
2018-10-02 07:41:27.741 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: SECURITY NOT required on COMMAND_CLASS_METER
2018-10-02 07:41:27.742 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 9: Received COMMAND_CLASS_METER V3 METER_REPORT
2018-10-02 07:41:27.744 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 9: Meter: Type=Electric(1), Scale=W(2), Value=171.5
2018-10-02 07:41:27.745 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Commands processed 1.
2018-10-02 07:41:27.746 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@3859f7.
2018-10-02 07:41:27.748 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2018-10-02 07:41:27.749 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
\
The device discovery just seems to be stuck and the wave stack refuses to do anything with it.
Winter is coming, and I’d rather not rip all this out and replace it (The controls for my boiler are on this).