Error - Failed writing highwater mark

[Michel Kohanim]

Hello Jim,

 

This is indeed very odd ... would you mind testing our 2.7.6 alpha? If you do not mind, please send me an email to tech@universal-devices.com .

 

With kind regards,

Michel

Hi Michel,

 

I just received 3 more 2420M sensors. All 3 MS units fail to add when the climate module is running. If I disable the modules or set polling so it does not occur during the add window, everything works fine. If the climate module polls during add it fails.

 

Only thing common I noticed on the MS units is the 4 digits in front of the rev.1.1 are "0909". Are these the production code?

 

Any ideas? Do you need me to send you one of the MS units?

 

Thanks,

Jim

[Jim G]

For anybody experiencing problems with RF devices failing to add and giving the errors described in this thread, here's what I found to work around the issue.

 

-adding an AP plugged directly into the PLM and adding the device within range

OR

-disabling the WB climate module during the device add

 

If I add an MS or TriggerLinc and the WB polls during the add it will fail. However if I disable the WB module I can add the device with no problems. Also if I plug an AP directly into the PLM and add the MS or TriggerLinc with the RF sensor with 10ft of the AP/PLM combo it will add successfully with the WB module enabled, even with polling set to 15sec.

 

I haven't had any problems adding ToggleLincs, OutletLincs, ApplianceLincs or KPLs, only RF devices.

 

Once the RF devices are added, I haven't had any issues. Only when they were in communications mode and being added to the ISY-99i/PLM.

 

Since I can plug the AP directly into the PLM and add the devices I thought it was a power line noise issue, but being able to disable the WB and make it work anywhere in the house contradicts that idea. So I'm really not sure of the cause, just glad I have a work around.

 

Jim

[Michel Kohanim]

Hello Mr. Graber,

 

Thanks so very much for the update. Personally I think by adding the AP on top of your PLM, you are making your MS/TL use that access point instead [of the other one]. In all likelihood, I think the problem is that your WiFi is interfering with some of your INSTEON access points.

 

In any case, I want to thank you again for posting your experiences to this forum.

 

With kind regards,

Michel

[Jim G]

Hi Michel,

 

Thanks for the direction.

 

I turned off the radio in the LinkSys WRT54GL/DD-WRT router to eliminate any interference to the access points. Still had the same problem. I can only add an MS with WB disabled or an AP plugged directly into the PLM.

 

In my mind this ruled out the WiFi, so I began looking back on the power line side.

 

I have a data collection unit that uses Netgear XE102 power line Ethernet bridges. I unplugged the units and the problem went away! I placed the AP back in it's original location, the MS as far away from an AP as I could get it, turned WiFi back on and was able to add the MS with no issues. Didn't matter if WB was enabled or disabled.

 

I would think the Insteon APs and ISY-99i/PLM would be able to coexist with the Netgear power line devices. Still not sure why disabling the WB module allowed the add device to work or why only RF devices were affected when the interference was coming from the Netgear power line bridges.

 

 

Thanks,

Jim

 

 

Hello Mr. Graber,

 

Thanks so very much for the update. Personally I think by adding the AP on top of your PLM, you are making your MS/TL use that access point instead [of the other one]. In all likelihood, I think the problem is that your WiFi is interfering with some of your INSTEON access points.

 

In any case, I want to thank you again for posting your experiences to this forum.

 

With kind regards,

Michel

[someguy]

I am getting this same error. I've tried disbling the climate module and putting an access point on top of the PLM. I still get the error.

 

Here is the curveball: I'm using a beta Motion sensor.

 

Anything else I can try before I tell Smarthome that this is a bad motion sensor?

[Michel Kohanim]

Hi someguy,

 

Do you have any HomePlug devices (bridge to Ethernet)? Jim's issue was related to HomePlug bridge devices. I really do not think the problem is the motion sensor.

 

With kind regards,

Michel

 

I am getting this same error. I've tried disbling the climate module and putting an access point on top of the PLM. I still get the error.

 

Here is the curveball: I'm using a beta Motion sensor.

 

Anything else I can try before I tell Smarthome that this is a bad motion sensor?

[someguy]

Michel:

 

I do not have a HomePlug.

 

any other ideas?

 

thanks,

 

someguy

 

 

Hi someguy,

 

Do you have any HomePlug devices (bridge to Ethernet)? Jim's issue was related to HomePlug bridge devices. I really do not think the problem is the motion sensor.

 

With kind regards,

Michel

 

I am getting this same error. I've tried disbling the climate module and putting an access point on top of the PLM. I still get the error.

 

Here is the curveball: I'm using a beta Motion sensor.

 

Anything else I can try before I tell Smarthome that this is a bad motion sensor?

[Michel Kohanim]

Hi someguy,

 

What firmware version are you running? Also, adding an AccessPoint right on top of the PLM helped before. All and all, this problem is due to RF cross interference from an Ethernet device to powerline.

 

With kind regards,

Michel

[someguy]

Hi someguy,

 

What firmware version are you running? Also, adding an AccessPoint right on top of the PLM helped before. All and all, this problem is due to RF cross interference from an Ethernet device to powerline.

 

With kind regards,

Michel

 

I am on 2.7.5 and I have my accesspoint right on top of the PLM. Still gives me the error.

 

thanks,

 

Someguy

[Michel Kohanim]

Hi someguy,

 

This is quite odd. Do you have any other powerline devices in your installation?

 

With kind regards,

Michel

[someguy]

Hi someguy,

 

This is quite odd. Do you have any other powerline devices in your installation?

 

With kind regards,

Michel

I'm not sure what you mean by powerline devices.

 

My motion sensor is a beta unit, but another beta tester WAS able to get his to work with his isy-99i.

[MikeB]

Hi someguy -

 

Try factory resetting the Motion Sensor before adding to the ISY.

[someguy]

I factory reset it and it still won't work.

 

Here is something that is odd:

 

sometimes when I try to link the Sensor to the ISY, the box comes up to show me what is happening, this happened before when I got this error.

 

Today, no box pops up. I am using "Link Management" "New Insteon Device", putting in the address for it and selecting the "Device type". I put the Sensor in linking mode and click okay and the box disappears and nothing more happens.

 

any ideas?

[Michel Kohanim]

Hello someguy,

 

I think it's about time to call our tech support so that you wouldn't have to waste more time trying to get the motion sensor to work.

 

With kind regards,

Michel

 

I factory reset it and it still won't work.

 

Here is something that is odd:

 

sometimes when I try to link the Sensor to the ISY, the box comes up to show me what is happening, this happened before when I got this error.

 

Today, no box pops up. I am using "Link Management" "New Insteon Device", putting in the address for it and selecting the "Device type". I put the Sensor in linking mode and click okay and the box disappears and nothing more happens.

 

any ideas?

[someguy]

problem solved. I was able to get it to connect. The reason that it "wouldn't connect" was that it was already connected. It is a beta unit and, surprisingly, they sent the same unit back to me, so when I tried to reassociate it with the ISY, nothing happened because it was already associated with it, unbeknownst to me.

 

thanks Rand,

 

Scott

[wpmjones]

Ugh.. Same issue here.

 

ISY 99i/IR PRO - v2.7.15

PLM (2413S) - v1.0 (0931)

 

I successfully added a ToggleLinc Relay (2466SW). Works great.

 

Trying to add a ToggleLinc Relay (2466DW) and two ICON Appliance On/Off Adapters (2856S3B) and I get the highwater mark error here is the Event Log.

 

15.2B.DB is the ToggleLinc

15.13.79 is the On/Off Adapter

 

Thu 08/26/2010 05:15:49 AM : Setting Time From NTP

Thu 08/26/2010 07:57:46 AM : ---- Initializing the linked devices ----

Thu 08/26/2010 07:57:46 AM : ---- All Linked Devices are now initialized ---

Thu 08/26/2010 07:57:46 AM : ---- Add remaining devices ----

Thu 08/26/2010 07:57:46 AM : [ 15 2B DB 1] Removing all links

Thu 08/26/2010 07:58:08 AM : [15 2B DB 1 ] Failed getting engine version. Reverting to i1.

Thu 08/26/2010 07:58:30 AM : [ 15 2B DB 1] ** Not added ** Remove Device Links failed

Thu 08/26/2010 07:58:30 AM : ---- All Remaining Device Added ----

 

Thu 08/26/2010 08:06:46 AM : ---- Initializing the linked devices ----

Thu 08/26/2010 08:06:46 AM : ---- All Linked Devices are now initialized ---

Thu 08/26/2010 08:06:46 AM : ---- Add remaining devices ----

Thu 08/26/2010 08:06:46 AM : [ 15 13 79 1] Removing all links

Thu 08/26/2010 08:07:10 AM : [ 15 13 79 1] ** Not added ** Remove Device Links failed

Thu 08/26/2010 08:07:10 AM : ---- All Remaining Device Added ----

 

 

I took the On/Off adapter into the same room with the ISY (which is attached to the cable modem/router which makes it difficult to move). Same results. I don't know if it's an i1 vs. i2 issue or a powerline issue or what. I've invest about $600 so far and don't really want to keep buying parts "until it works". I also have a TriggerLinc I want to connect, but don't even want to try that til I get the lights figured out.

 

Please help!!!!

[LeeG]

When you start the Event Viewer click on Change level and set to level 3. The posted trace says a problem exists but no detail. Level 3 will show the actual commands issued and what failed. On the surface it looks like a powerline communication problem. Assuming the ISY is not having trouble communicating with the existing devices such as being able to manually control existing devices the PLM should be okay. Do you have a pair of Dual Band devices such as Access Points coupling the 120V legs.

[Sub-Routine]

Hi wpmjones,

 

Please try a factory reset on the devices that don't want to add.

 

Rand

[wpmjones]

Tried the factory reset (had no idea the little light on the ToggleLinc was a Set button!) with no success.

 

============================

 

Level 3 Event Log

 

Thu 08/26/2010 03:54:26 PM : ---- Initializing the linked devices ----

Thu 08/26/2010 03:54:26 PM : ---- All Linked Devices are now initialized ----

Thu 08/26/2010 03:54:26 PM : ---- Add remaining devices ----

Thu 08/26/2010 03:54:26 PM : [ 15 2B DB 1] Removing all links

Thu 08/26/2010 03:54:26 PM : [15 2B DB 1 ] Querying engine version

Thu 08/26/2010 03:54:26 PM : [iNST-ACK ] 02 62 15.2B.DB 0F 0D 00 06 (00)

Thu 08/26/2010 03:54:27 PM : [iNST-SRX ] 02 50 15.2B.DB 13.27.18 27 0D 01 (01)

Thu 08/26/2010 03:54:27 PM : [standard-Direct Ack][15.2B.DB-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Thu 08/26/2010 03:54:27 PM : [15 2B DB 1 ] Retrieved engine version is i2

Thu 08/26/2010 03:54:27 PM : [15 2B DB 1 ] Using engine version i2

Thu 08/26/2010 03:54:27 PM : [iNST-ACK ] 02 62 15.2B.DB 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (02)

Thu 08/26/2010 03:54:28 PM : [iNST-SRX ] 02 50 15.2B.DB 13.27.18 27 2F 02 (02)

Thu 08/26/2010 03:54:28 PM : [standard-Direct Ack][15.2B.DB-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Thu 08/26/2010 03:54:37 PM : [iNST-ACK ] 02 62 15.2B.DB 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (02)

Thu 08/26/2010 03:54:37 PM : [iNST-SRX ] 02 50 15.2B.DB 13.27.18 27 2F 02 (02)

Thu 08/26/2010 03:54:37 PM : [standard-Direct Ack][15.2B.DB-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Thu 08/26/2010 03:54:46 PM : [iNST-ACK ] 02 62 15.2B.DB 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (02)

Thu 08/26/2010 03:54:49 PM : [iNST-SRX ] 02 50 15.2B.DB 13.27.18 27 2F 02 (02)

Thu 08/26/2010 03:54:49 PM : [standard-Direct Ack][15.2B.DB-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Thu 08/26/2010 03:54:53 PM : [ 15 2B DB 1] ** Not added ** Remove Device Links failed

Thu 08/26/2010 03:54:53 PM : ---- All Remaining Device Added ----

[LeeG]

Suggest you install 2.8.1 Beta. The Event Trace shows the form of the ALDB command used to access the link database (because the device reports I2) has a value of 02 in the cmd2 value. That value is used with an IRLinc to access IR code information but should be 00 when accessing the actual link database in non IRLinc.

 

 

Thu 08/26/2010 03:54:27 PM : [iNST-ACK ] 02 62 15.2B.DB 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (02)

[wpmjones]

I actually called UDI this afternoon and, of course, when you call the tech, it works normally. Sorta. I still couldn't add manually, but Start Linking allowed me to get everything added. I thought I had tried that before, but maybe I wasn't doing it exactly right. I still can't add manually, but as long as I can get them added, I'm satisfied.

 

Now, all I have to do is figure out how to use the ISY now that everything is added!

 

Thanks for all the quick responses!