Hi Paul,
Sounds like the version of viewer that you are using may be old and not aware of the newer UID addressing.
The latest version is at http://www.edjo.pwp.blueyonder.co.uk...ewer_main.htm#
Hope that helps!
Martyn
After installing the xAP pre-reqs I have xAP messages in my environment, but I'm getting lots of invalid messages in the viewer. Both Idratk and Squeezebox are generating these messages that appear like:
Any pointers as to what maybe going on and how Ican fix it?Error Message: Invalid name/value pairing. The length of the UID value is incorrect
Message Line#: 5 - uid=FF.071F43F3:0002
Received From: 127.0.0.1:4881
xap-header
{
v=13
hop=1
uid=FF.071F43F3:0002
class=xAP-Audio.Transport.Event
source=ersp.SlimServer.Hedwig:SBRadio
}
Audio.Transport
{
Elapsed=00:10
PlayerID=00:04:20:26:27:03
Remaining=02:35
Repeat=off
Shuffle=none
}
The error that was generated is as follows:
Problem reading xAP message.
Source: xAPMessage
Problem reading xAP message.
Invalid name/value pairing
The length of the UID value is incorrect.
KCS.xAP.Framework.xAPMessageReaderException: Problem reading xAP message. ---> KCS.xAP.Framework.xAPInvalidMessageException: Invalid name/value pairing
The length of the UID value is incorrect
at KCS.xAP.Framework.Message.xAPMessageReader.ReadHea derPair(xAPMessage message, String line)
at KCS.xAP.Framework.Message.xAPMessageReader.ReadMes sage()
--- End of inner exception stack trace ---
at KCS.xAP.Framework.Message.xAPMessageReader.ReadMes sage()
at KCS.xAP.Framework.Transport.xAPListener.OnReceive( IAsyncResult ar)
Hi Paul,
Sounds like the version of viewer that you are using may be old and not aware of the newer UID addressing.
The latest version is at http://www.edjo.pwp.blueyonder.co.uk...ewer_main.htm#
Hope that helps!
Martyn
Yepp Kevin also pointed out my mistake in downloading on old version. I have now downloaded the latest release from Ed Pearson's site, http://www.erspearson.com/xAP/xFx/viewer_main.htm, all is now working.
I've updated by Blog instructions so hopefully other noobies won't make the same mistake:
http://smarthome-uk.blogspot.com/201...d-running.html
Glad it's all working now - the UID's are longer in xAP v1.3 applications.
Do check that you are running the latest hubs as well , as older ones may reject and drop xAP v1.3 messages in the same way . Any hubs or Viewers using the KCS vendor ID or throwing KCS xAP Framework named errors are likley to be older versions.
http://www.erspearson.com/xAP/xFx/hubs_main.htm
K
Double checked the hub and it is the latest one Ed has released. Thanks for the advice. I've updated my blog and will let Otto know
. Cheers
Paul