Announcement

Collapse
No announcement yet.

Error trapping

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Just checked today, got a weird one.
    HS log, showing remote PI restarted at 16:16:
    Code:
    Dec-05 16:16:08	 	Kinect	INFO Kinect version 3.0.0.39
    Dec-05 16:16:08	 	Kinect	DEBUG Logger Initialized
    Dec-05 16:16:08	 	Info	Plugin Kinect with instance LivingRoom has connected. IP:192.168.5.10:50492
    Log of the remote instance:
    Code:
    Dec-05 16:14:41 TRACE Phrase hypothesized = House, Confidence=0.007275164 
    Dec-05 16:14:42 TRACE Phrase rejected = 
    Dec-05 16:14:46 INFO Posture Detected: HandsJoined
    Dec-05 16:16:54 TRACE Speech Detected:
    Dec-05 16:16:54 TRACE Phrase hypothesized = House, Confidence=0.004402697 
    Dec-05 16:16:54 TRACE Phrase hypothesized = House is, Confidence=0.2070283 
    Dec-05 16:16:55 TRACE Phrase recognized but confidence=0.01442062 is lower than threshold
    Dec-05 16:16:55 TRACE House who's home
    Dec-05 16:16:57 DEBUG Frame skipped
    Dec-05 16:16:59 TRACE Speech Detected:
    Dec-05 16:16:59 TRACE Phrase hypothesized = House, Confidence=0.01521048 
    Dec-05 16:17:00 TRACE Phrase rejected =
    Time of local and remote systems are exactly the same. Remote is saying it never restarted.

    Also, I've lost the interface settings pages again, but everything still seems to be functioning.

    Comment


    • #17
      Looks like I got the problem to trigger. Realised that VR wasn't working, checked the logs, looks like it tries to call the event, but then it never fires in HS:
      Code:
      Dec-07 16:58:06	 	Kinect	DEBUG Calling TriggerFire with evRef=1559
      Dec-07 16:58:06	 	Kinect	DEBUG Looking for triggers with evRef=1559
      Dec-07 16:58:06	 	Kinect	DEBUG Saving global variables: END
      Dec-07 16:58:06	 	Kinect	DEBUG Saving global variables: BEGIN
      Dec-07 16:58:06	 	Kinect	DEBUG House Change channel bee
      Dec-07 16:58:06	 	Kinect	DEBUG Phrase recognized with confidence=0.7836869
      Trying again with another VR event:
      Code:
      Dec-07 17:01:00	 	Event	Event Trigger "Time, periodic and polling events Battery Daily charting"
      Dec-07 17:00:48	 	Kinect	DEBUG Calling TriggerFire with evRef=1582
      Dec-07 17:00:48	 	Kinect	DEBUG Looking for triggers with evRef=1582
      Dec-07 17:00:48	 	Kinect	DEBUG Saving global variables: END
      Dec-07 17:00:48	 	Kinect	DEBUG Saving global variables: BEGIN
      Dec-07 17:00:48	 	Kinect	DEBUG House what's the time
      Dec-07 17:00:48	 	Kinect	DEBUG Phrase recognized with confidence=0.969849
      Now, bear in mind, this is the local PI instance, not the remote. The remote PI instance died early in the morning due to a PI restart of Zwave.
      Logs show nothing else, even though everything is set to trace - the events exist, and work once the PI is restarted:
      Code:
      Dec-07 17:14:18	 	TTS	Speak ():The time is 5:14 PM
      Dec-07 17:14:18	 	Event	Event Trigger "Voice Control VR - time"
      Dec-07 17:14:18	 	Kinect	DEBUG Calling TriggerFire with evRef=1582
      Dec-07 17:14:18	 	Kinect	DEBUG Looking for triggers with evRef=1582
      Dec-07 17:14:18	 	Kinect	DEBUG Saving global variables: END
      Dec-07 17:14:18	 	Kinect	DEBUG Saving global variables: BEGIN
      Dec-07 17:14:18	 	Kinect	DEBUG House what's the time
      Dec-07 17:14:18	 	Kinect	DEBUG Phrase recognized with confidence=0.8937574
      How about one thing to trap - if it's a remote instance (as in, there is no hs3 process), then just reinitialise if the "speech recognition stopped" is triggered? A remote instance should always be retrying to connect to HS I think?

      Comment


      • #18
        For those 2 events that didn't fire, do you have 2 triggers (one for each of your instance) configured

        IF Kinect1 A Phrase was recognized
        OR IF Kinect2 A Phrase was recognized
        THEN...
        ?

        If so I think I found the problem, a plugin instance can only fire a trigger that it owns, so probably the plugin was trying to fire the trigger associated with the other instance. Please test version 3.0.0.40 attached it should be fixed.

        Also now if ShutdownIO is called, a remote instance with the autoreconnect parameter will always try to reconnect, so this should be a good workaround to the HS3 bug we identified earlier. BTW Rich is looking at this bug as we speak.
        Attached Files
        Last edited by spud; December 7th, 2015, 03:15 PM.

        Comment


        • #19
          For those 2 events that didn't fire, do you have 2 triggers (one for each of your instance) configured

          IF Kinect1 A Phrase was recognized
          OR IF Kinect2 A Phrase was recognized
          THEN...
          ?
          Spot on, all my VR is an event for one or the other instance recognising the phrase, saves me from having to reinvent the wheel

          I'll try this latest version out, thanks Spud.

          Comment


          • #20
            Well, it's been ages since I reported in, and I think we can also put another bug to bed
            Remember that confidence bug where GB speech was selected? No longer happens.
            I now have a stable system where I don't worry about whether something might need restarting - the remote PI just reconnects when the disconnect bug kicks in, a small price to pay for not having the weatherxml PI enabled for the time being.

            Comment


            • #21
              What rev are you using?
              Hector
              ____________________________________
              Win.2003 OS, HS3
              BLDSC,BLstat,BLRadar,BLRamdom,BLOccupied
              BLups,BLrain8,HSTouch,Ultrajones Weatherbug,
              MyTrigger,ACRF2,W800,Zwave
              AP800,Honeywell Stat

              Comment


              • #22
                .40, posted earlier in the thread

                Comment

                Working...
                X