Z-wave broken with 0.66

Just upgraded to 0.66, and no z-wave device is working. I think it has something to do with entity id’s but I haven’t figured out what I need to do to fix it yet.

I have encountered som issues aswell with 0,66

A removal of the following solved it for me.
new_entity_ids: true
network_key: 0xEE, 0x7E, 0x67, 0x55, 0x00, 0x61, 0xB0, 0x25, 0x9C, 0xCD, 0xF3, 0xA6, 0x83, 0x3B, 0x77, 0x54

And a reboot of the Pi

2 Likes

Removing the line with “new_entity_ids” fixed my problem

1 Like

Yup, that was highlighted in the breaking changes section of the release as well.

2 Likes

It was but I did not find anything outside of the community mentioning the removal of new_entity_ids from configuration.yaml.

They didn’t say it directly other than the option was deprecated - which I’ve now learned means “remove the entry otherwise stuff will break” (I assumed it would ignore the entry but I guess that’s why they call it “breaking changes”)

Hi Guys,

I do not have the “new_entity_ids” in my configuration.yaml but I still have above issue. Anyone know what could be wrong? I can’t see any Zwave devices.

PS: I even updated to version 0.66.1 thinking it would have fixed the issue.

Thanks in advance.

Have you checked your Home Assistant logs, and OZW_Log.txt, for any errors relating to Z-Wave?

Hi @Tinkerer,

Apologies for the delay in reply, I get below error in the log file.

2018-04-01 00:00:04.409 Info, Node006, Sending (Command) message (Callback ID=0xaf, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=6): 0x01, 0x05, 0x00, 0x48, 0x06, 0xaf, 0x1b
2018-04-01 00:00:05.409 Error, Node006, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-04-01 00:00:05.409 Detail, Node006, Removing current message
2018-04-01 00:00:05.409 Detail, Node006, Notification: Notification - TimeOut
2018-04-01 00:00:05.411 Detail, Notification: ControllerCommand - Error - Failed
2018-04-01 00:00:05.411 Info, Requesting Neighbor Update for node 7
2018-04-01 00:00:05.411 Detail, Node007, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=7): 0x01, 0x05, 0x00, 0x48, 0x07, 0xb0, 0x05
2018-04-01 00:00:05.411 Detail, Notification: ControllerCommand - Starting
2018-04-01 00:00:05.411 Error, Node007, ERROR: Dropping command because node is presumed dead
2018-04-01 00:00:05.411 Detail, Node007, Removing current message
2018-04-01 00:00:05.411 Detail, Notification: ControllerCommand - Error - Failed
2018-04-01 12:13:42.101 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xc9f7c88e
2018-04-01 12:13:43.103 Info, mgr,     Driver for controller /dev/ttyACM0 pending removal
2018-04-01 12:13:43.104 Detail, Notification: DriverRemoved
2018-04-01 12:13:43.104 Always, ***************************************************************************
2018-04-01 12:13:43.104 Always, *********************  Cumulative Network Statistics  *********************
2018-04-01 12:13:43.104 Always, *** General
2018-04-01 12:13:43.104 Always, Driver run time: . .  . 2 days, 23 hours, 28 minutes
2018-04-01 12:13:43.104 Always, Frames processed: . . . . . . . . . . . . . . . . . . . . 1382
2018-04-01 12:13:43.104 Always, Total messages successfully received: . . . . . . . . . . 1382
2018-04-01 12:13:43.104 Always, Total Messages successfully sent: . . . . . . . . . . . . 179
2018-04-01 12:13:43.104 Always, ACKs received from controller:  . . . . . . . . . . . . . 162
2018-04-01 12:13:43.104 Always, *** Errors
2018-04-01 12:13:43.104 Always, Unsolicited messages received while waiting for ACK:  . . 3
2018-04-01 12:13:43.104 Always, Reads aborted due to timeouts:  . . . . . . . . . . . . . 0
2018-04-01 12:13:43.104 Always, Bad checksum errors:  . . . . . . . . . . . . . . . . . . 0
2018-04-01 12:13:43.104 Always, CANs received from controller:  . . . . . . . . . . . . . 3
2018-04-01 12:13:43.104 Always, NAKs received from controller:  . . . . . . . . . . . . . 0
2018-04-01 12:13:43.104 Always, Out of frame data flow errors:  . . . . . . . . . . . . . 0
2018-04-01 12:13:43.104 Always, Messages retransmitted: . . . . . . . . . . . . . . . . . 3
2018-04-01 12:13:43.104 Always, Messages dropped and not delivered: . . . . . . . . . . . 27
2018-04-01 12:13:43.104 Always, ***************************************************************************
2018-04-01 12:13:43.104 Detail, WriteMsg Wait Timeout m_currentMsg=00000000
2018-04-01 12:13:45.137 Info, mgr,     Driver for controller /dev/ttyACM0 removed
2018-04-01 12:13:46.139 Error, mgr,     Manager::GetDriver failed - Home ID 0xc9f7c88e is unknown
2018-04-01 12:13:46.139 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2018-04-01 12:13:46.139 Info, mgr,     GetSendQueueCount() failed - _homeId -906508146 not found

Looks like a problem communicating with your Z-Wave controller. Have you verified that it’s (still) on /dev/ttyACM0?

I have the same issue and have checked that I don’t have the above mentioned entry ‘new_entity_ids: true’.

I also cannot load up the OZW Log, the node values or config parameters from the Z-Wave gui.

I am on version 0.67

If you SSH on, what shows in OZW_Log.txt. What is the error in the Home Assistant log?

I have the same problem, since update to 0.67 I cannot load the ozw log into HA configuration GUI and clicking on Refresh button doesn’t change only:
Loading ozw log…
But ozw_log.txt can be loaded into any other editor.

No errors in Home Assistant log. Z-wave log starts as normal but doesn’t have any additional entries after it starts. Like the service has stopped for whatever reason

Me too, can’t get into any of the config options for zwave devices. all the drop downs just flash and don’t show anything

If you have not tried it, do a reboot. I saw the same when I went to .66 and the upgrade does not do a reboot. After the upgrade /dev/ttyACM0 was now /dev/tty/ACM1 if you look at the hardware details. A reboot fixed it for me as /dev/ttyACM0 was correctly being used.

It’s fixed in 0.67.1 see this post: Z-Wave configuration error

Yikes, glad I did not upgrade. If one did, is downgrading as easy as going to a snapshot before the upgrade?

downgrading is not difficult at all, no matter the install method, just always take a backup lol