I noticed in my log that every time one of my switches beeps as a result of a program telling it to, I get this error log. This is true for multiple programs working on different switches. All programs have the same structure. The switch does beep as expected. Also, if someone could tell me what the number next to beep duration means. I have set it to different numbers and don't notice anything different.

 

Kitchen / Pantry-Light L   Beep   100   Thu 2011/12/08 02:50:45 PM   Program   Log
Kitchen / Pantry-Light L   Beep   100   Thu 2011/12/08 02:50:45 PM   Program   -1


If
       Status  'Kitchen / Pantry-Light L' is not Off

Then
       Set 'Kitchen / Pantry-Light L' 100 (Beep Duration)
       Wait  30 seconds
       Set 'Kitchen / Pantry-Light L' Off

Else
  - No Actions - (To add one, press 'Action')

Hello Lou,

 

-1 means Request Failed. Unlike device communication errors, -1 means that the device returned a NACK. You might want to use the Event Viewer on Device Communications level and capture the traffic.

 

With kind regards,

Michel

OK, but then why does it happen? I have about 5 programs written like this to beep the switch a minute or so before it is going to be flipped off. All of them appear to be giving the nack every single time they receive the beep command. The beep does beep.

 

Also, how does the duration number work? As I mentioned it seems like the beep sounds the same no matter what the number.

apostolakisl

 

If you can post the Event Viewer trace from a beep operation it will be easier to evaluate.

 

No one has found a device that utilizes the beep duration. It appears to be one of those Insteon interface values that may eventually be used by some device but so far none do. The beep function itself is generic but only a few devices have implemented beep in any form.

 

There is often function described in the command spec's that take time to show up in an actual device. In what is sometimes described as Insteon 1 (I1) there is an entire collection of Extended commands that no device ever implemented.

 

Lee

 

EDIT: what is the switch device type and the firmware level in the device

Michel and Lou,

 

I was about to post back that I "sometimes" see the -1 log entry as well. After testing, I have to change that to "always".

 

I had also wondered if this was associated with "differences" in some of my Icon switches. It is not. I've tested a SWL relay, SWL dimmer, and Icon relay. They all generate the -1 log error.

 

Curiously, there is no indication of an error in the event monitor:

 

Event Monitor

Fri 12/09/2011 09:39:26 AM : [iNST-ACK ] 02 62 16.10.95 0F 30 FA 06 BEEP (FA)

Fri 12/09/2011 09:39:27 AM : [iNST-SRX ] 02 50 16.10.95 13.22.F9 2B 30 FA BEEP (FA)

Fri 12/09/2011 09:39:27 AM : [standard-Direct Ack][16.10.95-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Fri 12/09/2011 09:39:28 AM : [iNST-ACK ] 02 62 16.10.95 0F 30 FA 06 BEEP (FA)

Fri 12/09/2011 09:39:29 AM : [iNST-SRX ] 02 50 16.10.95 13.22.F9 2B 30 FA BEEP (FA)

Fri 12/09/2011 09:39:29 AM : [standard-Direct Ack][16.10.95-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Fri 12/09/2011 09:39:30 AM : [iNST-ACK ] 02 62 16.10.95 0F 30 FA 06 BEEP (FA)

Fri 12/09/2011 09:39:31 AM : [iNST-SRX ] 02 50 16.10.95 13.22.F9 2B 30 FA BEEP (FA)

Fri 12/09/2011 09:39:31 AM : [standard-Direct Ack][16.10.95-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Error Log

1st Floor / Mud Room Beep 250 Fri 2011/12/09 09:39:27 AM Program Log

1st Floor / Mud Room Beep 250 Fri 2011/12/09 09:39:27 AM Program -1

1st Floor / Mud Room Beep 250 Fri 2011/12/09 09:39:29 AM Program Log

1st Floor / Mud Room Beep 250 Fri 2011/12/09 09:39:29 AM Program -1

1st Floor / Mud Room Beep 250 Fri 2011/12/09 09:39:31 AM Program Log

1st Floor / Mud Room Beep 250 Fri 2011/12/09 09:39:31 AM Program -1

apostolakisl

 

If you can post the Event Viewer trace from a beep operation it will be easier to evaluate.

 

No one has found a device that utilizes the beep duration. It appears to be one of those Insteon interface values that may eventually be used by some device but so far none do. The beep function itself is generic but only a few devices have implemented beep in any form.

 

There is often function described in the command spec's that take time to show up in an actual device. In what is sometimes described as Insteon 1 (I1) there is an entire collection of Extended commands that no device ever implemented.

 

Lee

 

EDIT: what is the switch device type and the firmware level in the device

 

Hello LeeG,

 

I created a thread about the chime / beep feature on the new dual band KPL. Would you consider perhaps this new KPL would utilize this unused feature??

 

Once I receive the new unit I will surely test it to confirm my thoughts.

 

Teken . . .

I was disappointed that the new DB keypadlinc did not support the beep duration (not variable duration).

I posted some results at Smarthome, two devices did support the duration command (variable length) were:

The PLM and Access points.

 

http://www.smarthome.com/forum/topic.asp?TOPIC_ID=8734&SearchTerms=beep,duration

I was disappointed that the new DB keypadlinc did not support the beep duration (not variable duration).

I posted some results at Smarthome, two devices did support the duration command (variable length) were:

The PLM and Access points.

 

http://www.smarthome.com/forum/topic.asp?TOPIC_ID=8734&SearchTerms=beep,duration

 

 

ELA,

 

As always, I thank you for your contributions and insight. This truly saddens me . . .

 

Teken . . .

It's every switch I have set to beep.

 

2476d's

2476s's

2476db's

 

All of my switches are about 2 years old or less as I replaced essentially all of them for the paddle issue.

 

If I sort the log by "beep" it is 100% of them that do the error.

Hi guys,

 

Thanks so very much for all the input. We'll look into it and report back.

 

With kind regards,

Michel

Any resolution/update for this? I also have noticed a -1 error in each case there is a beep called in a program...the beeps do work, but errors are still displayed in each instance in the log file...

 

Thanks!

Hello gfridland,

 

Sorry, for the lack of update. This is fixed in 3.1.17.

 

With kind regards,

Michel