The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Re: xAP Stopped Working



That looks like maybe an older (xAPV1.2) hub giving that message.
'KCSoftware'
The length of the UID filed was increased in xAP v1.3.
You are using one of the latest hub builds downloaded from Edwards site
aren't you ?  An older hub will drop all the newer xAP v1.3 messages and
so only some apps will traverse the hub.

I am not sure if the 'what's using the port' app you downloaded will
correctly identify services that are bound to UDP listening ports , and
so it may not correctly show a port as in use.  Bear in mind that all
xAP applications send to UDP port 3639 but only one xAP application can
listen on that port (the hub).

The listening port is listed within the heartbeat sent by each
application and should be different for every application on the same PC
(and only the hub should indicate 3639).  If the apps are on different
PC's then you may legitimately have duplicate ports.  3639 could be used
by a different apps , one per machine , although they should really be
hubs.  We now always recommend a hub on every xAP machine as it is not a
requirement to provide fallback hub functionality within a xAP
application, in fact it's discouraged.

K




------------------------------------


xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.