Announcement

Collapse
No announcement yet.

Nest plugin only working one way? Cannot alter settings from webpage or HSTouch

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

  • Nest plugin only working one way? Cannot alter settings from webpage or HSTouch

    I've just bought a Hometroller SEL PRO. The Nest plugin is the first thing I've installed (I have a ton of z-wave devices but I can't add them yet as I'm waiting for the separate controller).

    All my Nest devices appear in HS3, and I can see the thermostat controls in HSTouch. If I change the settings on the thermostat itself or in the Nest app, the changes are rapidly shown in HS3 and HSTouch.

    However, I can't make any changes in HS3 or HSTouch. None of the "control" buttons in HS3 do anything. The mode won't change in HSTouch when I press it. The set temperature changes in HSTouch when I use the arrows, but it only changes in the app (not on the thermostat or in HS3) and it eventually changes back to what it was previously.

    How can I control my Nest devices with this plugin??

  • #2
    please set the log level to Debug from the Config page, and post what you get (View > Log) when you try to change a temp or mode from HS3.

    thanks

    Comment


    • #3
      Debug log

      Hi, thanks for the quick response -- sorry should have realised this would help!

      Mar-05 10:40:59 PM Nest DEBUG data: null
      Mar-05 10:40:59 PM Nest DEBUG event: keep-alive
      Mar-05 10:40:28 PM Nest DEBUG data: null
      Mar-05 10:40:28 PM Nest DEBUG event: keep-alive
      Mar-05 10:40:13 PM Nest DEBUG instance: af8b0138-c168-4480-b4bf-c9a197d001bb
      Mar-05 10:40:13 PM Nest DEBUG message: blocked
      Mar-05 10:40:13 PM Nest DEBUG type: https://developer.nest.com/documenta...ssages#blocked
      Mar-05 10:40:13 PM Nest DEBUG error: blocked
      Mar-05 10:40:13 PM Nest ERROR blocked
      Mar-05 10:40:11 PM Nest DEBUG PUT: path=devices/thermostats/gi6tL1If6Gj88O3JhD8dFw_VumSUMP-v payload={"hvac_mode":"off"}
      Mar-05 10:40:11 PM Nest DEBUG instance: 2d153913-54e2-47f7-88b6-4d4e7de6dc63
      Mar-05 10:40:11 PM Nest DEBUG message: blocked
      Mar-05 10:40:11 PM Nest DEBUG type: https://developer.nest.com/documenta...ssages#blocked
      Mar-05 10:40:11 PM Nest DEBUG error: blocked
      Mar-05 10:40:11 PM Nest ERROR blocked
      Mar-05 10:40:10 PM Device Control Device: Hallway HVAC Mode to Off (0) by/from: CAPI Control Handler
      Mar-05 10:40:09 PM Nest DEBUG PUT: path=devices/thermostats/gi6tL1If6Gj88O3JhD8dFw_VumSUMP-v payload={"target_temperature_c":20.5}
      Mar-05 10:40:09 PM Nest DEBUG instance: c3455631-6b61-45c0-b70a-c673b5a895d8
      Mar-05 10:40:09 PM Nest DEBUG message: blocked
      Mar-05 10:40:09 PM Nest DEBUG type: https://developer.nest.com/documenta...ssages#blocked
      Mar-05 10:40:09 PM Nest DEBUG error: blocked
      Mar-05 10:40:09 PM Nest ERROR blocked
      Mar-05 10:40:07 PM Nest DEBUG PUT: path=devices/thermostats/gi6tL1If6Gj88O3JhD8dFw_VumSUMP-v payload={"target_temperature_c":20.5}
      Mar-05 10:40:07 PM Nest DEBUG instance: 5232e5b3-1946-4093-bbbc-74c87b689335
      Mar-05 10:40:07 PM Nest DEBUG message: blocked
      Mar-05 10:40:07 PM Nest DEBUG type: https://developer.nest.com/documenta...ssages#blocked
      Mar-05 10:40:07 PM Nest DEBUG error: blocked
      Mar-05 10:40:07 PM Nest ERROR blocked
      Mar-05 10:40:04 PM Nest DEBUG PUT: path=devices/thermostats/gi6tL1If6Gj88O3JhD8dFw_VumSUMP-v payload={"target_temperature_c":20.5}
      Mar-05 10:40:04 PM Nest DEBUG instance: 5122a8d2-4af9-41ff-bc54-2f1c872605e9
      Mar-05 10:40:04 PM Nest DEBUG message: blocked
      Mar-05 10:40:04 PM Nest DEBUG type: https://developer.nest.com/documenta...ssages#blocked
      Mar-05 10:40:04 PM Nest DEBUG error: blocked
      Mar-05 10:40:04 PM Nest ERROR blocked
      Mar-05 10:40:04 PM Device Control Device: Hallway Target Temperature to + (1001) by/from: CAPI Control Handler

      Comment


      • #4
        as explained here, this error means you have reach the "rate limit" imposed by Nest. This usually happen when you test the plugin and issue too many requests.

        you just need to wait 1day or 2 until you are allowed again to do some requests.

        Comment


        • #5
          Originally posted by spud View Post
          as explained here, this error means you have reach the "rate limit" imposed by Nest. This usually happen when you test the plugin and issue too many requests.

          you just need to wait 1day or 2 until you are allowed again to do some requests.
          Thanks, hadn't seen that! Have tried today and it seems to respond!

          I didn't exactly issue floods of commands, I was just trying to test it to see if it responded as this is a new setup for me. Nest don't actually seem to specify what rate limits they impose, other than that suggestion "to avoid errors, we recommend you limit requests to one call per minute, maximum"... wow. That feels really restrictive!

          Comment

          Working...
          X