Plug-in working, but scanning constantly?

[Guest]

My PIM is buzzing away like a madman. Over and over and over. This is on initial install, but I've shut down and restarted HS3 Pro and it is still going. I'm afraid I'm going to wear out my poor PIM. Any idea what the plug-in is doing that it fails to stop scanning on HS3 Pro startup?

Thanks!!!!

[spud]

could you set the log level to debug, capture the logs when the problem occurs and post them here.
does it happen before you have imported your UPStart export file?

[Guest]

Will do. It did not do anything until I configured it and set it up. I got it to stop by issuing a few device commands but then when I hit the button to poll devices from Home, it starts buzzing and never stops again. Really weird. Let me grab the log for you thanks!

[Guest]

Not sure how to grab a lot... there are thousands of lines of this, but here's an excerpt.

Apr-30 6:49:03 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply

Apr-30 6:49:03 PM UPBSpud DEBUG PIM_SEND:: Message ID 188 confirmed sent successfully

Apr-30 6:49:03 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=188)

Apr-30 6:49:03 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=188)

Apr-30 6:49:03 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140101FF30B4{0xD}]

Apr-30 6:49:03 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 188 to PIM, retry count=0

Apr-30 6:49:03 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:49:03 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 188)

Apr-30 6:49:03 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:49:03 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter

Apr-30 6:49:03 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Timer Control (1)

Apr-30 6:49:03 PM UPBSpud DEBUG PIM_SEND:: Resuming sending as we received at least one device message

Apr-30 6:49:03 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:49:03 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU0A0001FF0186FFFFFF72]

Apr-30 6:49:02 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply

Apr-30 6:49:02 PM UPBSpud DEBUG PIM_SEND:: Message ID 187 confirmed sent successfully

Apr-30 6:49:02 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=187)

Apr-30 6:49:01 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=187)

Apr-30 6:49:01 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140101FF30B4{0xD}]

Apr-30 6:49:01 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 187 to PIM, retry count=0

Apr-30 6:49:01 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:49:01 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 187)

Apr-30 6:49:01 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:49:01 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter

Apr-30 6:49:01 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Timer Control (1)

Apr-30 6:49:01 PM UPBSpud DEBUG PIM_SEND:: Resuming sending as we received at least one device message

Apr-30 6:49:01 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:49:01 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU0A0001FF0186FFFFFF72]

Apr-30 6:49:01 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply

Apr-30 6:49:01 PM UPBSpud DEBUG PIM_SEND:: Message ID 186 confirmed sent successfully

Apr-30 6:49:01 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=186)

Apr-30 6:49:00 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=186)

Apr-30 6:49:00 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140101FF30B4{0xD}]

Apr-30 6:49:00 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 186 to PIM, retry count=0

Apr-30 6:49:00 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:49:00 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 186)

Apr-30 6:49:00 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:49:00 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter

Apr-30 6:49:00 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Timer Control (1)

Apr-30 6:49:00 PM UPBSpud DEBUG PIM_SEND:: Resuming sending as we received at least one device message

Apr-30 6:49:00 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:49:00 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU0A0001FF0186FFFFFF72]

Apr-30 6:49:00 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply

Apr-30 6:49:00 PM UPBSpud DEBUG PIM_SEND:: Message ID 185 confirmed sent successfully

Apr-30 6:49:00 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=185)

Apr-30 6:48:59 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=185)

Apr-30 6:48:59 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140101FF30B4{0xD}]

Apr-30 6:48:59 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 185 to PIM, retry count=0

Apr-30 6:48:59 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:59 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 185)

Apr-30 6:48:59 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:59 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter

Apr-30 6:48:59 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Timer Control (1)

Apr-30 6:48:59 PM UPBSpud DEBUG PIM_SEND:: Resuming sending as we received at least one device message

Apr-30 6:48:59 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:59 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU0A0001FF0186FFFFFF72]

Apr-30 6:48:58 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply

Apr-30 6:48:58 PM UPBSpud DEBUG PIM_SEND:: Message ID 184 confirmed sent successfully

Apr-30 6:48:58 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=184)

Apr-30 6:48:58 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=184)

Apr-30 6:48:58 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140101FF30B4{0xD}]

Apr-30 6:48:58 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 184 to PIM, retry count=0

Apr-30 6:48:58 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:58 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 184)

Apr-30 6:48:58 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:58 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter

Apr-30 6:48:58 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Timer Control (1)

Apr-30 6:48:58 PM UPBSpud DEBUG PIM_SEND:: Resuming sending as we received at least one device message

Apr-30 6:48:58 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:58 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU0A0001FF0186FFFFFF72]

Apr-30 6:48:57 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply

Apr-30 6:48:57 PM UPBSpud DEBUG PIM_SEND:: Message ID 183 confirmed sent successfully

Apr-30 6:48:57 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=183)

Apr-30 6:48:57 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=183)

Apr-30 6:48:57 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140101FF30B4{0xD}]

Apr-30 6:48:57 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 183 to PIM, retry count=0

Apr-30 6:48:57 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:57 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 183)

Apr-30 6:48:57 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:57 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter

Apr-30 6:48:57 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Timer Control (1)

Apr-30 6:48:57 PM UPBSpud DEBUG PIM_SEND:: Resuming sending as we received at least one device message

Apr-30 6:48:57 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:57 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU0A0001FF0186FFFFFF72]

Apr-30 6:48:56 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply

Apr-30 6:48:56 PM UPBSpud DEBUG PIM_SEND:: Message ID 182 confirmed sent successfully

Apr-30 6:48:56 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=182)

Apr-30 6:48:55 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=182)

Apr-30 6:48:55 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140101FF30B4{0xD}]

Apr-30 6:48:55 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 182 to PIM, retry count=0

Apr-30 6:48:55 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:55 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 182)

Apr-30 6:48:55 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:55 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter

Apr-30 6:48:55 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Timer Control (1)

Apr-30 6:48:55 PM UPBSpud DEBUG PIM_SEND:: Resuming sending as we received at least one device message

Apr-30 6:48:55 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:55 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU0A0001FF0186FFFFFF72]

Apr-30 6:48:55 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply

Apr-30 6:48:55 PM UPBSpud DEBUG PIM_SEND:: Message ID 181 confirmed sent successfully

Apr-30 6:48:55 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=181)

Apr-30 6:48:54 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=181)

Apr-30 6:48:54 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140101FF30B4{0xD}]

Apr-30 6:48:54 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 181 to PIM, retry count=0

Apr-30 6:48:54 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:54 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 181)

Apr-30 6:48:54 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:54 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter

Apr-30 6:48:54 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Timer Control (1)

Apr-30 6:48:54 PM UPBSpud DEBUG PIM_SEND:: Resuming sending as we received at least one device message

Apr-30 6:48:54 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:54 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU0A0001FF0186FFFFFF72]

Apr-30 6:48:54 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply

Apr-30 6:48:54 PM UPBSpud DEBUG PIM_SEND:: Message ID 180 confirmed sent successfully

Apr-30 6:48:54 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=180)

Apr-30 6:48:53 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=180)

Apr-30 6:48:53 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140101FF30B4{0xD}]

Apr-30 6:48:53 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 180 to PIM, retry count=0

Apr-30 6:48:53 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:53 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 180)

Apr-30 6:48:53 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:53 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter

Apr-30 6:48:53 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Timer Control (1)

Apr-30 6:48:53 PM UPBSpud DEBUG PIM_SEND:: Resuming sending as we received at least one device message

Apr-30 6:48:53 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:53 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU0A0001FF0186FFFFFF72]

Apr-30 6:48:52 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply

Apr-30 6:48:52 PM UPBSpud DEBUG PIM_SEND:: Message ID 179 confirmed sent successfully

Apr-30 6:48:52 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=179)

Apr-30 6:48:52 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=179)

Apr-30 6:48:52 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140101FF30B4{0xD}]

Apr-30 6:48:52 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 179 to PIM, retry count=0

Apr-30 6:48:52 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:52 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 179)

Apr-30 6:48:52 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:52 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter

Apr-30 6:48:52 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Timer Control (1)

Apr-30 6:48:52 PM UPBSpud DEBUG PIM_SEND:: Resuming sending as we received at least one device message

Apr-30 6:48:52 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

Apr-30 6:48:52 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU0A0001FF0186FFFFFF72]

Apr-30 6:48:51 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply

Apr-30 6:48:51 PM UPBSpud DEBUG PIM_SEND:: Message ID 178 confirmed sent successfully

Apr-30 6:48:51 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=178)

Apr-30 6:48:51 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=178)

Apr-30 6:48:51 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140101FF30B4{0xD}]

Apr-30 6:48:51 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 178 to PIM, retry count=0

Apr-30 6:48:51 PM UPBSpud DEBUG DEVICE[1]:: Got request to set light to non-normative level -- queueing status request to confirm

[spud]

what kind of device is the "Timer Control (1) " and jhow is it configured?

Could you try to exclude it temporarily from your network in UPStart and reimport the new exported file to see if the problem is due to this specific device?

[Guest]

That should be my timed event controller. Let me see how to exclude it without deleting the device.

[spud]

The plugin doesn't support this kind of device and thinks it's a simple light device and try to get its current state.
So if I can differentiate it, I probably should just ignore it.

Could you send me your UPStart export file (the one that includes this device)

thanks

[Guest]

No problem I will send it over shortly! I use the timed event controller to handle outdoor lighting on/off at sunset, etc and other timed internal lighting events that I want to happen even if the PC is not booted and running HS2/3 for any reason, so it's an important part of my setup, but now that it's set, I don't really change it, so for now it's no big deal excluding it for the config until you have a chance to programmatically ignore it.

Thanks!

Oh and everything works perfectly without the device in the export now! Thanks for the great work. HomeSeer should be paying you extra since without your plugin I never could have upgraded to HS3 Pro from HS2.

Adam

[spud]

HomeSeer should be paying you extra

you bet!

[spud]

could you test version 3.0.0.11 available here: http://board.homeseer.com/showthread...01#post1088701

this should make it work even if the Timed Event Controller is in your .upe file

[Guest]

Will do!

[Guest]

Perfect! Thanks so much for the quick fix. All better now