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: Homeseer 2 Plugin Question



The log is from the bottom up, not top to bottom :D

Cheers

Marc

--- In xap_automation@xxxxxxx, "marcrfuller"
<yahoogroups@s...> wrote:
> As a side note to this. I was no longer receiving updates so I did the
> following..
>
> Stopped Homeseer Service
> Stopped xAP Hub Service
> Stopped Quasar Application
>
> Started xAP Hub Services
> Started Quasar Application
> Started Homeseer Services
>
> I then noticed I had "New Hardware" in xAP config (even
though the
> original device was still in Homeseer).
>
> Added the new device and got the following in the logs (with debug on)
>
> 02/09/2005 19:25:37   xAP Conduit  Set status 30.69
> 02/09/2005 19:25:37   xAP Conduit  HSEVENT
> Ismenuclick=false64,[4,30.69,,,,
> 02/09/2005 19:25:37   xAP Conduit  HSEVENT =64
> 02/09/2005 19:25:37   xAP Conduit  HSEVENT =64,[4,30.69,,,,
> 02/09/2005 19:25:37   xAP Conduit  Device is homeserver com3 one
> temperature.current temp
> 02/09/2005 19:25:37   xAP Conduit  xAP Engine Go Input (5,30.69)
> 02/09/2005 19:25:37   xAP Conduit
>
ersp.telemetry.homeserver.com3:one-xap-temp.notification-temperature.current-unit-C
>
> 02/09/2005 19:25:37   Database Item  There were errors generated
> during the save of the database item. Please consult this log for more
> details and report any data loss to HomeSeer Technologies.
> 02/09/2005 19:25:37   xAP Conduit  Incoming message Stage 4 - First
> message check
> 02/09/2005 19:25:37   xAP Conduit
>
ersp.telemetry.homeserver.com3:one-xap-temp.notification-temperature.current-location-One
>
> 02/09/2005 19:25:37   xAP Conduit  Incoming message Stage 4 - First
> message check
> 02/09/2005 19:25:37   xAP Conduit
>
ersp.telemetry.homeserver.com3:one-xap-temp.notification-temperature.current-seq-2
>
> 02/09/2005 19:25:37   xAP Conduit  Incoming message Stage 4 - First
> message check
> 02/09/2005 19:25:37   xAP Conduit
>
ersp.telemetry.homeserver.com3:one-xap-temp.notification-temperature.current-temp-30.69
>
> 02/09/2005 19:25:37   xAP Conduit  Incoming message Stage 4 - First
> message check
> 02/09/2005 19:25:37   xAP Conduit
>
ersp.telemetry.homeserver.com3:one-xap-temp.notification-temperature.current--
>
> 02/09/2005 19:25:37   xAP Conduit  Incoming message Stage 4 - First
> message check
> 02/09/2005 19:25:37   xAP Conduit  Incoming message Stage 3 - Post
> known hardware check
> 02/09/2005 19:25:37   xAP Conduit  xAP message
> ERSP.telemetry.homeserver.com3:One(xap-temp.notification)
> 02/09/2005 19:25:37   xAP Conduit  Incoming message Stage 2 - Post
> header extraction and Iam ignore
> 02/09/2005 19:25:37   xAP Conduit  Re processing last xAP message
> 02/09/2005 19:25:37   xAP Conduit  mid1 new device0
> 02/09/2005 19:25:37   Database Item  Device Comparison Error 5, field
> name : Cannot set column 'name' to 'homeserver one homeserver com3 one
> temperature.current temp'. The value violates the MaxLength limit of
> this column. Exception:Cannot set column 'name' to 'homeserver one
> homeserver com3 one temperature.current temp'. The value violates the
> MaxLength limit of this column.
> 02/09/2005 19:25:37   Database Item  Saving Device homeserver one
> homeserver com3 one temperature.current temp
> 02/09/2005 19:25:37   xAP Conduit  Created new device homeserver
> homeserver com3 one temperature.current temp
> 02/09/2005 19:25:37   xAP Conduit  Using [4
> 02/09/2005 19:25:37   xAP Conduit  Trying [4-4
> 02/09/2005 19:25:37   xAP Conduit  Skipped (HS says it exists)[3-17-
> 02/09/2005 19:25:37   xAP Conduit  Trying [3-3
> 02/09/2005 19:25:37   xAP Conduit  Skipped (HS says it exists)[2-15-
> 02/09/2005 19:25:37   xAP Conduit  Trying [2-2
> 02/09/2005 19:25:37   xAP Conduit  Skipped (HS says it exists)[1-12-
> 02/09/2005 19:25:37   xAP Conduit  Trying [1-1
> 02/09/2005 19:25:37   xAP Conduit  Creating new device homeserver com3
> one temperature.current temp([)
>
>
> The error is still there, but hopefully more helpful information.
>
> Cheers
>
> Marc
>
>
>
> --- In xap_automation@xxxxxxx, "marcrfuller"
> <yahoogroups@s...> wrote:
> > --- In xap_automation@xxxxxxx, Kevin Hawkins <lists@u...>
wrote:
> > >
> > >  Kevin Hawkins wrote:
> > >
> > > >Marc - the version of the xAP plugin you are using is
2.0.182 ??
> > > >(About Tab)
> > > >
> > > >
> > > Hmm - just revisited your first post - you are :-)
> > >
> > > Might have to see what James says on this ...
> > >
> > > (I note the network UID is FE but that's just out of
interest
and not
> > > related to this problem)
> > >
> > >
> >
> > Yeah I'm running the latest version 2.0.0.182 :)
> >
> >
> > > K
> > >
> > > >The xAp message u sent doesn't generate HS errors for
me....
> > > >
> > > >02/09/2005 16:45:57 ~!~xAP Conduit~!~Created new device
homeserver
> > > >homeserver com3 one temperature.current temp
> > > >02/09/2005 16:45:57 ~!~Database Item~!~Saving Device
homeserver
one
> > > >homeserver com3 one temperature.current temp
> > > >02/09/2005 16:45:58 ~!~xAP Conduit~!~Created new device
homeserver
> > > >homeserver com3 one temperature.current unit
> > > >02/09/2005 16:45:58 ~!~Database Item~!~Saving Device
homeserver
> > com3 one
> > > >temperature.current unit
> >
> > That's strange.. I wonder why it does with mine... every single
time I
> > get the error so it's easily duplicated.
> >
> > Cheers
> >
> > Marc





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.