Did a backup, factory reset, attempted to restore via the ZBK file, logging messages show devices with lots of "empty", and now no devices.
I would say things are... worse.
Search found 35 matches
- 08 Dec 2018 23:58
- Forum: Discussions in English
- Topic: Inability to include any new Z-Wave device
- Replies: 18
- Views: 11442
- 08 Dec 2018 23:50
- Forum: Discussions in English
- Topic: Inability to include any new Z-Wave device
- Replies: 18
- Views: 11442
Re: Inability to include any new Z-Wave device
20 devices presently active, ~60 previously (old house, moved a few months ago), last device id added was 116.
License appears to be valid/active. Had wondered if that might have been an issue over upgrades.
License appears to be valid/active. Had wondered if that might have been an issue over upgrades.
- 08 Dec 2018 23:44
- Forum: Discussions in English
- Topic: Inability to include any new Z-Wave device
- Replies: 18
- Views: 11442
- 08 Dec 2018 23:37
- Forum: Discussions in English
- Topic: Inability to include any new Z-Wave device
- Replies: 18
- Views: 11442
Re: Inability to include any new Z-Wave device
Thanks for your reply. Controller is primary, and only controller. Reset API via /expert/network/control, and have reboot the Raspberry Pi. Same issue. To reiterate my initial post, all existing devices are controllable, and work perfectly. Seems only inclusion is broken (exclusion works fine). Z-Wa...
- 06 Dec 2018 19:40
- Forum: Discussions in English
- Topic: Inability to include any new Z-Wave device
- Replies: 18
- Views: 11442
Re: Inability to include any new Z-Wave device
Looked at this some more, and I noticed the instant fail was occurring before I even walked over to trigger the device's inclusion button.
- 06 Dec 2018 00:04
- Forum: Discussions in English
- Topic: Inability to include any new Z-Wave device
- Replies: 18
- Views: 11442
Inability to include any new Z-Wave device
Tried adding a Leviton DZPA1, and now a Honeywell (Jasco) ZW4103, and they're both failing (instantly): [2018-12-05 13:00:54.827] [zway] Adding job: Add/re-include node to network [2018-12-05 13:00:54.831] [D] [zway] SENDING (cb 0xeb): ( 01 05 00 4A C1 EB 9A ) [2018-12-05 13:00:54.832] [D] [zway] RE...
- 11 May 2017 18:25
- Forum: Discussions in English
- Topic: Schlage BE469 door lock notifications?
- Replies: 12
- Views: 17076
Re: Schlage BE469 door lock notifications?
So Niffler works in 2.3.1?
- 28 Mar 2017 06:42
- Forum: Device specific
- Topic: 2.3.0 and Schlage Lock
- Replies: 13
- Views: 19383
Re: 2.3.0 and Schlage Lock
Bump. Is there any resolution for Niffler, or roadmap for NIffler-like support...?
- 24 Feb 2017 22:04
- Forum: Device specific
- Topic: 2.3.0 and Schlage Lock
- Replies: 13
- Views: 19383
Re: 2.3.0 and Schlage Lock
Having similar issues with the Niffler module that worked with 2.2.5, albeit on GE switches. Should I follow-up here, or open a new forum thread and or Git issue? Will Z-Way eventually provide the same NIF workaround that the Niffler module did prior to 2.3.0? Original issue that led me to discover ...
- 24 Feb 2017 21:37
- Forum: Official announcements
- Topic: v2.3.0 is out!
- Replies: 19
- Views: 71487
Re: v2.3.0 is out!
Issues here as well. I have my locks (Schlage and Yale) as well as some dimmers and binary switches all running under the module 'Niffler'. I can control all the above mentioned devices, I just never see a state change. This was operating fine in 2.2.3. I can provide logs if needed as I see Niffler...