Interview failed with Philio PST02-1A

Discussions about existing Z-Wave device and their usage with Z-Way/Z-Cloud/Z-Box
opperman
Posts: 14
Joined: 03 Feb 2015 12:06

Re: Interview failed with Philio PST02-1A

Post by opperman »

Is there a way to downgrade the firmware to an earlier version? My older Philio device with older firmware works perfectly, only the newer ones with z-wave plus certification produce the errors described.
The device supports on the air firmware update, I only can't find older file versions of the firmware in the internet to upload them to the device.
opperman
Posts: 14
Joined: 03 Feb 2015 12:06

Re: Interview failed with Philio PST02-1A

Post by opperman »

I contacted Philio support, and they said me that my Razberry Controller is 400 series chipset and that's why it doesn't work with their 500 series sensors. Razberry support says they only work with 500 series chipset on their controllers so this can't be the problem.
Conclusion of my contact with Philio support: Now the only thing you can do is change your controller, perhaps in the future the Razberry can handle 500 series sensors, but now apparently not.
pofs
Posts: 688
Joined: 25 Mar 2011 19:03

Re: Interview failed with Philio PST02-1A

Post by pofs »

RaZberry controller only exists on 300 or 500 series chips. We've never used 400 series.
thaui
Posts: 65
Joined: 28 Jan 2015 19:14

Re: Interview failed with Philio PST02-1A

Post by thaui »

Still not working in RC33 but interview is getting better. Not working in HA gui. I am waiting on further improvments and after seeing the last developments I am sure it is soon before finalizing this issue. Keep going guys.
neurotux
Posts: 1
Joined: 24 Jun 2015 20:43

Re: Interview failed with Philio PST02-1A

Post by neurotux »

Hi all,

I'm newbie in z-way server but i encounter the exact same behavior with my new PST02-1A multi-sensor. It's never finishing interview and sensor such presence or temperature not give back information to z-way server, also make it totally unstable, i had to exclude device in order to get it worked with my other z-way devices. Worked multiple times and also tried all described in the post, no improvement.

For information, i asked Philio support also to get their feedback, here is the mail exchange:
##############################################################################################
Hi Steve

thanks for your email.

we found that it’s a compatible issue.
we believe Z-way can fix this issue without Philio’s support.

when Philio's device cause Z-way crash, that means the application does not take care all the situations.
we will modify the firmware by the end of this year but we won’t be able to provide the HEX file to the end customer but only to the business customer.

as far as we know that Z-way has a SDK to play the Z-Wave. the most of the users are student, so we are not sure if there is any commercial product using this SDK or not.
and you may find some more info at Z-Wave.me.

any further questions please do not hesitate to let us know.

BR
Arthur
______________________________________________________

Philio Technology Corporation
Arthur C. / Sr. Director of Sales & Marketing
8F., No.653-2, Zhongzheng Rd., Xinzhuang Dist.,
New Taipei City 24257, Taiwan (R.O.C.)
Tel: +886-2-2908-8952 #777
Fax: +886-2-2908-8652
E-Mail: arthur@philio-tech.com http://www.philio-tech.com

> On 23 Jun 2015, at 20:38, Marty, Steve <steve.marty@pictboard.ch> wrote:
>
> Hello Philio-Tech,
>
> I'm contacting you regarding your multi-sensor Z-wave device PST02-1A. i tried to make it working using Raspberry PI 2 and Razberry board with latest firmware, but i'm encountering the exact same behavior than explained in this forum (and reviewed by z-way server expert):
> viewtopic.php?f=3423&t=21185
>
> Apparently plenty of other people also having the exact same issue in which the interview between z-way server and PST02-1A device is never completed, and most of the time making sensors not giving information back to z-way server and also crash of the z-way server.
>
> Are you aware of such issue and have you some kind of solution, such firmware upgrade/downgrade ? is that a known issue from your side ?
>
> Thanks for your help,
> Steve
##############################################################################################

This clearly state, they will not really improve the situation frome their side, due to the fact they said it's a z-way server issue, and not directly related to the PST02-1A (but also mentionned firmware upgrade end of the year but only fot business Customer...good support isn't it ? ).

Don't know if this could also help somehow..just to add my small contribution to this story.. i will let this vendor aside, no other device give me issue like this Philio sensor (only z-wave device i have from them, probably last one if this story is continuing for long time).
thaui
Posts: 65
Joined: 28 Jan 2015 19:14

Re: Interview failed with Philio PST02-1A

Post by thaui »

But they continue to sell this device and promote the device as compatible. I just send back a PST02-1B. This problem is now over 4 months old and no solution. I tried out some fibaro motion devices. They do what they promise. Try it

RC44 still not working with PST02-1B. Temperature and illumination is ok Motion not.
michap
Posts: 442
Joined: 26 Mar 2013 10:35
Contact:

Re: Interview failed with Philio PST02-1A

Post by michap »

With version 2.0.1 the interview will be complete.

But.... no value changes.

All the day today no change in Lux and temperature - sensor is located at window.

The only i get is: (no values inside since last night - same block all the time)

Code: Select all

[2015-07-13 15:35:32.011] [D] [zway] SETDATA devices.13.data.lastReceived = 0 (0x00000000)
[2015-07-13 15:35:32.011] [D] [zway] SETDATA devices.13.instances.0.commandClasses.132.data.lastWakeup = 1436794532 (0x55a3bea4)
[2015-07-13 15:35:32.012] [D] [zway] SETDATA devices.13.data.isAwake = True
[2015-07-13 15:35:32.012] [D] [zway] SETDATA devices.13.data.lastSend = 2575092 (0x00274af4)
[2015-07-13 15:35:32.012] [D] [zway] SETDATA devices.13.data.lastNonceGet = 2574092 (0x0027470c)
[2015-07-13 15:35:32.012] [D] [zway] SETDATA devices.13.instances.0.commandClasses.132.data.lastSleep = 1436794532 (0x55a3bea4)
[2015-07-13 15:35:32.098] [D] [zway] SETDATA devices.13.data.lastPacketInfo.delivered = True
[2015-07-13 15:35:32.098] [D] [zway] SETDATA devices.13.data.lastPacketInfo.packetLength = 5 (0x00000005)
[2015-07-13 15:35:32.098] [D] [zway] SETDATA devices.13.data.lastPacketInfo.deliveryTime = 15 (0x0000000f)
[2015-07-13 15:35:32.098] [D] [zway] SETDATA devices.13.data.lastPacketInfo = **********
[2015-07-13 15:35:32.098] [D] [zway] SETDATA devices.13.data.lastSend = 2575101 (0x00274afd)
[2015-07-13 15:35:32.099] [D] [zway] SETDATA devices.13.data.isAwake = False
[2015-07-13 16:04:54.883] [D] [zway] SETDATA devices.13.data.lastReceived = 0 (0x00000000)
[2015-07-13 16:04:54.883] [D] [zway] SETDATA devices.13.instances.0.commandClasses.132.data.lastWakeup = 1436796294 (0x55a3c586)
[2015-07-13 16:04:54.883] [D] [zway] SETDATA devices.13.data.isAwake = True
[2015-07-13 16:04:54.883] [D] [zway] SETDATA devices.13.data.lastSend = 2749226 (0x0029f32a)
[2015-07-13 16:04:54.884] [D] [zway] SETDATA devices.13.data.lastNonceGet = 2748226 (0x0029ef42)
[2015-07-13 16:04:54.884] [D] [zway] SETDATA devices.13.instances.0.commandClasses.132.data.lastSleep = 1436796294 (0x55a3c586)
[2015-07-13 16:04:54.973] [D] [zway] SETDATA devices.13.data.lastPacketInfo.delivered = True
[2015-07-13 16:04:54.973] [D] [zway] SETDATA devices.13.data.lastPacketInfo.packetLength = 5 (0x00000005)
[2015-07-13 16:04:54.973] [D] [zway] SETDATA devices.13.data.lastPacketInfo.deliveryTime = 15 (0x0000000f)
[2015-07-13 16:04:54.974] [D] [zway] SETDATA devices.13.data.lastPacketInfo = **********
[2015-07-13 16:04:54.974] [D] [zway] SETDATA devices.13.data.lastSend = 2749235 (0x0029f333)
[2015-07-13 16:04:54.974] [D] [zway] SETDATA devices.13.data.isAwake = False
[2015-07-13 16:23:57.175] [D] [zway] SETDATA devices.13.data.lastReceived = 0 (0x00000000)
And - I can not add the description record, so I'm not able to check / set any parameters (or ... it is not easy ;) ).

Any idea?

Michael
pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Re: Interview failed with Philio PST02-1A

Post by pz1 »

michap wrote: And - I can not add the description record, so I'm not able to check / set any parameters (or ... it is not easy ;) ).
l
That (and a few other things) has been fixed with v2.0.2-rc1
michap
Posts: 442
Joined: 26 Mar 2013 10:35
Contact:

Re: Interview failed with Philio PST02-1A

Post by michap »

RIGHT - description can now be loaded.

(I didn't want to "hop" at this installation from rc to rc ... ;) ..)

Door sensor:

Code: Select all

[2015-07-13 19:49:16.270] [D] [zway] RECEIVED: ( 01 24 00 04 00 0D 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 16 00 05 31 05 03 01 59 06 31 05 01 0A 00 47 24 )
[2015-07-13 19:49:16.271] [D] [zway] SENT ACK
[2015-07-13 19:49:16.271] [I] [zway] Got frame from device 13 to controller, but command class 0x8f for device is not registered - instantiating it as not supported
[2015-07-13 19:49:16.272] [W] [zway] Command Class 0x8f is not supported (requested for node 13:0)
[2015-07-13 19:49:16.272] [D] [zway] SETDATA devices.13.data.lastReceived = 0 (0x00000000)
[2015-07-13 19:49:19.751] [D] [zway] RECEIVED: ( 01 24 00 04 00 0D 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 17 00 05 31 05 03 01 57 06 31 05 01 0A 00 47 2B )
[2015-07-13 19:49:19.751] [D] [zway] SENT ACK
[2015-07-13 19:49:19.752] [I] [zway] Got frame from device 13 to controller, but command class 0x8f for device is not registered - instantiating it as not supported
[2015-07-13 19:49:19.752] [W] [zway] Command Class 0x8f is not supported (requested for node 13:0)
[2015-07-13 19:49:19.752] [D] [zway] SETDATA devices.13.data.lastReceived = 0 (0x00000000)

But Motion - nothing, no temp. or lux change ....

Michael
User avatar
PoltoS
Posts: 7579
Joined: 26 Jan 2011 19:36

Re: Interview failed with Philio PST02-1A

Post by PoltoS »

@michap

You are using UZB without license loaded? It clearly does not support some features.
> Command Class 0x8f is not supported (requested for node 13:0)
Post Reply