Hate to say it, but it seems the device never answers to SensorMultilevel Supported Sensor Get, Wakeup Capabilities Get and Association Groupings Get. Commands are delivered to device, but it never sends a report back. And it appears it is not a MultiCmd issue here, because device previously handles much larger packets.
Try pressing "Force re-interview" for these command classes one by one (so they're not combined into MultiCmd) to completely rule out possible MultiCmd issues. But I doubt something will change.
Interview failed with Philio PST02-1A
Re: Interview failed with Philio PST02-1A
I tried pressing "Force re-interview" in interview details many times, command class by command class, and after a while comes the symbol "ø" appears showing that it failed.
When I press "Force re-interview" for the whole device, it start a new interview, and it has always the same result, some CC fail.
What else can I try?
When I press "Force re-interview" for the whole device, it start a new interview, and it has always the same result, some CC fail.
What else can I try?
Re: Interview failed with Philio PST02-1A
I mean not pressing them all, but press only one and wake device, and see if interview completes.
When you press them all and then wake the device, they're packed into MultiCmd. I want to rule out this case and see if device answers the single command.
When you press them all and then wake the device, they're packed into MultiCmd. I want to rule out this case and see if device answers the single command.
Re: Interview failed with Philio PST02-1A
Ah ok, I understand.
Here the log output by forcing the interview of only one cc, SensorMultilevel for example that was failing:
The cc stayed at failed afterwards.
I also tried with the other failed ccs, the log is similar, and the interviews doesn't complete.
Here the log output by forcing the interview of only one cc, SensorMultilevel for example that was failing:
Code: Select all
[2015-03-18 13:25:06.805] [I] [zway] Adding job: SensorMultilevel Supported Sensor Get
[2015-03-18 13:25:06.814] [I] [zway] Node 2:0 CC Security: sending Nonce Get
[2015-03-18 13:25:06.814] [D] [zway] SETDATA devices.2.instances.0.commandClasses.152.data.rNonceAckWait = **********
[2015-03-18 13:25:06.815] [I] [zway] Adding job: Nonce Get
[2015-03-18 13:25:06.815] [D] [zway] SETDATA devices.2.data.lastNonceGet = 1424554 (0x0015bcaa)
[2015-03-18 13:25:06.825] [D] [zway] SENDING (cb 0x98): ( 01 09 00 13 02 02 98 40 05 98 A0 )
[2015-03-18 13:25:06.827] [D] [zway] RECEIVED ACK
[2015-03-18 13:25:06.831] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2015-03-18 13:25:06.831] [D] [zway] SENT ACK
[2015-03-18 13:25:06.831] [D] [zway] Delivered to Z-Wave stack
[2015-03-18 13:25:07.027] [D] [zway] RECEIVED: ( 01 07 00 13 98 01 00 13 61 )
[2015-03-18 13:25:07.027] [D] [zway] SENT ACK
[2015-03-18 13:25:07.027] [I] [zway] Job 0x13 (Nonce Get): Not delivered to recipient
[2015-03-18 13:25:07.027] [D] [zway] SETDATA devices.2.data.lastPacketInfo.delivered = False
[2015-03-18 13:25:07.028] [D] [zway] SETDATA devices.2.data.lastPacketInfo.packetLength = 5 (0x00000005)
[2015-03-18 13:25:07.028] [D] [zway] SETDATA devices.2.data.lastPacketInfo.deliveryTime = 197 (0x000000c5)
[2015-03-18 13:25:07.028] [D] [zway] SETDATA devices.2.data.lastPacketInfo = **********
[2015-03-18 13:25:07.028] [D] [zway] SETDATA devices.2.data.isAwake = False
[2015-03-18 13:25:07.028] [D] [zway] Sending the queue for node 2 into sleep
[2015-03-18 13:25:10.524] [D] [zway] RECEIVED: ( 01 08 00 04 04 02 02 84 07 74 )
[2015-03-18 13:25:10.525] [D] [zway] SENT ACK
[2015-03-18 13:25:10.525] [D] [zway] SETDATA devices.2.data.lastReceived = 0 (0x00000000)
[2015-03-18 13:25:10.525] [I] [zway] Node 2:0 CC Wakeup: Wakeup notification
[2015-03-18 13:25:10.525] [D] [zway] SETDATA devices.2.instances.0.commandClasses.132.data.lastWakeup = 1426681510 (0x55096ea6)
[2015-03-18 13:25:10.525] [D] [zway] SETDATA devices.2.data.isAwake = True
[2015-03-18 13:25:10.525] [D] [zway] SETDATA devices.2.data.lastSend = 1424921 (0x0015be19)
[2015-03-18 13:25:10.525] [D] [zway] SETDATA devices.2.data.lastNonceGet = 1423921 (0x0015ba31)
[2015-03-18 13:25:10.525] [D] [zway] Running wakeup handler for node 2
[2015-03-18 13:25:10.595] [D] [zway] SENDING (cb 0x98): ( 01 09 00 13 02 02 98 40 05 98 A0 )
[2015-03-18 13:25:10.596] [D] [zway] RECEIVED ACK
[2015-03-18 13:25:10.602] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2015-03-18 13:25:10.602] [D] [zway] SENT ACK
[2015-03-18 13:25:10.602] [D] [zway] Delivered to Z-Wave stack
[2015-03-18 13:25:10.626] [D] [zway] RECEIVED: ( 01 07 00 13 98 00 00 02 71 )
[2015-03-18 13:25:10.626] [D] [zway] SENT ACK
[2015-03-18 13:25:10.626] [I] [zway] Job 0x13 (Nonce Get): Delivered
[2015-03-18 13:25:10.626] [D] [zway] SETDATA devices.2.data.lastPacketInfo.delivered = True
[2015-03-18 13:25:10.626] [D] [zway] SETDATA devices.2.data.lastPacketInfo.packetLength = 5 (0x00000005)
[2015-03-18 13:25:10.626] [D] [zway] SETDATA devices.2.data.lastPacketInfo.deliveryTime = 23 (0x00000017)
[2015-03-18 13:25:10.626] [D] [zway] SETDATA devices.2.data.lastPacketInfo = **********
[2015-03-18 13:25:10.627] [D] [zway] SendData Response with callback 0x98 received: received by recipient
[2015-03-18 13:25:10.627] [D] [zway] SETDATA devices.2.data.lastSend = 1424931 (0x0015be23)
[2015-03-18 13:25:10.627] [D] [zway] Job 0x13 (Nonce Get): success
[2015-03-18 13:25:10.627] [D] [zway] SETDATA devices.2.instances.0.commandClasses.152.data.rNonceAckWait = **********
[2015-03-18 13:25:10.627] [I] [zway] Removing job: Nonce Get
[2015-03-18 13:25:10.627] [I] [zway] Node 2:0 CC Security: sending Nonce Get
[2015-03-18 13:25:10.627] [D] [zway] SETDATA devices.2.instances.0.commandClasses.152.data.rNonceAckWait = **********
[2015-03-18 13:25:10.628] [I] [zway] Adding job: Nonce Get
[2015-03-18 13:25:10.628] [D] [zway] SETDATA devices.2.data.lastNonceGet = 1424931 (0x0015be23)
[2015-03-18 13:25:10.636] [D] [zway] RECEIVED: ( 01 10 00 04 00 02 0A 98 80 E9 64 21 15 3C A4 77 D7 7A )
[2015-03-18 13:25:10.636] [D] [zway] SENT ACK
[2015-03-18 13:25:10.637] [D] [zway] SETDATA devices.2.data.lastReceived = 0 (0x00000000)
[2015-03-18 13:25:10.637] [I] [zway] Node 2:0 CC Security: received Nonce Report
[2015-03-18 13:25:10.637] [W] [zway] Node 2:0 CC Security: Nonce Get was not ACKed yet. Ignoring this nonce
[2015-03-18 13:25:10.697] [D] [zway] SENDING (cb 0x99): ( 01 09 00 13 02 02 98 40 05 99 A1 )
[2015-03-18 13:25:10.698] [D] [zway] RECEIVED ACK
[2015-03-18 13:25:10.702] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2015-03-18 13:25:10.702] [D] [zway] SENT ACK
[2015-03-18 13:25:10.703] [D] [zway] Delivered to Z-Wave stack
[2015-03-18 13:25:10.717] [D] [zway] RECEIVED: ( 01 07 00 13 99 00 00 02 70 )
[2015-03-18 13:25:10.717] [D] [zway] SENT ACK
[2015-03-18 13:25:10.717] [I] [zway] Job 0x13 (Nonce Get): Delivered
[2015-03-18 13:25:10.717] [D] [zway] SETDATA devices.2.data.lastPacketInfo.delivered = True
[2015-03-18 13:25:10.718] [D] [zway] SETDATA devices.2.data.lastPacketInfo.packetLength = 5 (0x00000005)
[2015-03-18 13:25:10.718] [D] [zway] SETDATA devices.2.data.lastPacketInfo.deliveryTime = 14 (0x0000000e)
[2015-03-18 13:25:10.718] [D] [zway] SETDATA devices.2.data.lastPacketInfo = **********
[2015-03-18 13:25:10.718] [D] [zway] SendData Response with callback 0x99 received: received by recipient
[2015-03-18 13:25:10.718] [D] [zway] SETDATA devices.2.data.lastSend = 1424940 (0x0015be2c)
[2015-03-18 13:25:10.718] [D] [zway] Job 0x13 (Nonce Get): success
[2015-03-18 13:25:10.718] [D] [zway] SETDATA devices.2.instances.0.commandClasses.152.data.rNonceAckWait = **********
[2015-03-18 13:25:10.719] [I] [zway] Removing job: Nonce Get
[2015-03-18 13:25:10.737] [D] [zway] RECEIVED: ( 01 10 00 04 00 02 0A 98 80 AC 4B 0D E6 94 89 63 FE 77 )
[2015-03-18 13:25:10.737] [D] [zway] SENT ACK
[2015-03-18 13:25:10.737] [D] [zway] SETDATA devices.2.data.lastReceived = 0 (0x00000000)
[2015-03-18 13:25:10.738] [I] [zway] Node 2:0 CC Security: received Nonce Report
[2015-03-18 13:25:10.738] [D] [zway] SETDATA devices.2.instances.0.commandClasses.152.data.rNonce = **********
[2015-03-18 13:25:10.738] [I] [zway] Removing job: SensorMultilevel Supported Sensor Get
[2015-03-18 13:25:10.738] [I] [zway] Node 2:0 CC Security: Sending a secure message
[2015-03-18 13:25:10.738] [I] [zway] Node 2:0 CC Security: sending encrypted packet: SensorMultilevel Supported Sensor Get
[2015-03-18 13:25:10.738] [D] [zway] SETDATA devices.2.instances.0.commandClasses.152.data.toFollow = False
[2015-03-18 13:25:10.738] [D] [zway] SETDATA devices.2.data.lastNonceGet = Empty
[2015-03-18 13:25:10.739] [I] [zway] Adding job: Security, SensorMultilevel Supported Sensor Get
[2015-03-18 13:25:10.788] [D] [zway] SENDING (cb 0x9a): ( 01 1D 00 13 02 16 98 81 04 16 D1 7D 73 2E 09 CF AD EB 4E AC 10 E4 D2 39 B7 B1 2D 39 05 9A EF )
[2015-03-18 13:25:10.791] [D] [zway] RECEIVED ACK
[2015-03-18 13:25:10.795] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2015-03-18 13:25:10.795] [D] [zway] SENT ACK
[2015-03-18 13:25:10.795] [I] [zway] Job 0x13 (Security, SensorMultilevel Supported Sensor Get): Response received - transfered to encapsulated jobs
[2015-03-18 13:25:10.795] [D] [zway] Delivered to Z-Wave stack
[2015-03-18 13:25:10.795] [D] [zway] Delivered to Z-Wave stack
[2015-03-18 13:25:10.818] [D] [zway] RECEIVED: ( 01 07 00 13 9A 00 00 01 70 )
[2015-03-18 13:25:10.819] [D] [zway] SENT ACK
[2015-03-18 13:25:10.819] [I] [zway] Job 0x13 (Security, SensorMultilevel Supported Sensor Get): Callback received - transfered to encapsulated jobs
[2015-03-18 13:25:10.819] [I] [zway] Job 0x13 (SensorMultilevel Supported Sensor Get): Delivered
[2015-03-18 13:25:10.819] [D] [zway] SendData Response with callback 0x9a received: received by recipient
[2015-03-18 13:25:10.819] [I] [zway] Job 0x13 (Security, SensorMultilevel Supported Sensor Get): Delivered
[2015-03-18 13:25:10.819] [D] [zway] SETDATA devices.2.data.lastPacketInfo.delivered = True
[2015-03-18 13:25:10.819] [D] [zway] SETDATA devices.2.data.lastPacketInfo.packetLength = 25 (0x00000019)
[2015-03-18 13:25:10.819] [D] [zway] SETDATA devices.2.data.lastPacketInfo.deliveryTime = 23 (0x00000017)
[2015-03-18 13:25:10.820] [D] [zway] SETDATA devices.2.data.lastPacketInfo = **********
[2015-03-18 13:25:10.820] [D] [zway] SendData Response with callback 0x9a received: received by recipient
[2015-03-18 13:25:10.820] [D] [zway] SETDATA devices.2.data.lastSend = 1424950 (0x0015be36)
[2015-03-18 13:25:10.820] [D] [zway] Job 0x13 (Security, SensorMultilevel Supported Sensor Get): success
[2015-03-18 13:25:10.820] [I] [zway] Removing job: Security, SensorMultilevel Supported Sensor Get
I also tried with the other failed ccs, the log is similar, and the interviews doesn't complete.
-
- Posts: 1
- Joined: 01 Apr 2015 22:39
Re: Interview failed with Philio PST02-1A
Hi!
Did you get it to work?
My Razberry got totally instable after connecting PST02 so i excluded the device and not really know what to do.
Any advice?
Mikael
Did you get it to work?
My Razberry got totally instable after connecting PST02 so i excluded the device and not really know what to do.
Any advice?
Mikael
Re: Interview failed with Philio PST02-1A
I just tried it with v2.0.1-rc24 and the same, it is impossible to complete the interview.
Really frustrating. Is there anything we can do or help with?
Really frustrating. Is there anything we can do or help with?
Re: Interview failed with Philio PST02-1A
I have the same problem with my new sensors Philio Slim Multi-Sensor PST02-A. For test purpose I already bought one before, everything worked without problems. My latest sensors are Application Version 1.17, SDK Version 6.51.02, the old one still was Application Version 1.0, SDK version 6.02.00.
During inclusion in my z-wave network the interview does not complete totally. After several reboots of my Razberry (after some configuration changes I can't access the webinterface anymore and have to reboot the z-wave Server) the only item for which the interview stays incomplete is "AssociationGroupInformation". Even repeated complete interview and re-include did not solve the problem. Because of the missing association the sensor does not send triggering events to the Razberry.
I don't know any other solutions, maybe a Firmware-downgrade could solve the problem? Where can I download Firmware for Philio sensors?
Thanks for your help
Christian
During inclusion in my z-wave network the interview does not complete totally. After several reboots of my Razberry (after some configuration changes I can't access the webinterface anymore and have to reboot the z-wave Server) the only item for which the interview stays incomplete is "AssociationGroupInformation". Even repeated complete interview and re-include did not solve the problem. Because of the missing association the sensor does not send triggering events to the Razberry.
I don't know any other solutions, maybe a Firmware-downgrade could solve the problem? Where can I download Firmware for Philio sensors?
Thanks for your help
Christian
Re: Interview failed with Philio PST02-1A
The sensor PST02-1B is showing the same behavior. Take in consideration that the Philio sensor is not the problem. It's the z-way server. I have some other Gen5 devices and all of them does not work. There is no help possible except the guys who work on the z-way software. I wish us all that the Gen5 problems are solved faster because otherwise our investment is useless.
Re: Interview failed with Philio PST02-1A
I have some serious doubts about thisthaui wrote:Take in consideration that the Philio sensor is not the problem. It's the z-way server. I have some other Gen5 devices and all of them does not work.
They're clearly violating some of Z-Wave+ specifications, so it actually is a problem.
Note that Gen5 chips are new to the market, and have completely new firmwares. So vendors will obviously face a lot of issues before devices become stable.
I'm not saying z-way is completely free of errors, but the log provided here makes it look innocent
This issue was reported to Philio during CeBIT, but we don't have a response from them yet. Stay tuned.
Re: Interview failed with Philio PST02-1A
Thanks for the prompt response. I agree Gen5 is only a few month in the market but if the old sensores are sold out and only the new devices are available it is disappointing if you do not get a system running with the neccessary devices. To switch on and off your lights with a tablet is not really a smart home solution. Cross our fingers that the issues are sorted out in the next few months.