Teken

MustangChris04, Can you share your use case and over all intent in having the ability to send the Level 3 logs to a SysLog server?

To add to the information provided by Paul. Do not enable 2 form authentication on your GMAIL account. As the ISY Series Controller does not support such features. Ideals are peaceful - History is violent

Given the low voltage you indicated above I would think it would be enough to trip the I/O Linc safely. Using a photo cell unless properly fined tuned and balanced to pick up the LED light may prove a hit or miss affair.

My personal observation is the latest PLM units RF output is much stronger than years past. This is causing near field over load on the 2440 Remote Lincs which explains those instances. It does not explain why this problem has impacted a couple of users who did not receive a new PLM upgrade though. Then again maybe the OP's never clearly explained they did in fact receive a new PLM and thus the same issues.

Hello Harold, That is great to hear! [emoji4] Ideals are peaceful - History is violent

Not sure where you got that information but they are. Members have indicated that this particular remote needs to be positioned very far away from the PLM to enable linking. Ideals are peaceful - History is violent

Received another Open - Close sensor the other day with a hardware production date of 4114, revision 1.B, ISY firmware listed as v.43. This is the first Open - Close / Trigger Linc that does not have the mechanical jumper. I understood that the next Beta release would offer a software option to access the jumper feature. Also, this version like many others does not have the ability to set the battery / heartbeat node values. I was a little disappointed in that because there is a project I wanted to test out with these new options.

I received another 2852-222 Leak Sensor which indicates a hardware production of 4314, Rev 2.3 and ISY firmware of v.43. As others indicated this version of hardware does not seem to toggle the sensor from on to off when pressed? To confirm a few basics and expected behavior placing the sensor in a plate of water caused the device to immediately send a wet on. The dry node indicated off in the Admin Console, as expected. Watching the leaks sensor the LED flashed about every 15 - 17 seconds. Taking the unit out of the plate of water did not make the node change state which was also expected in the Admin Console. While viewing the sensor in a dry state the LED indicator stopped flashing?? I have to assume that meant it was no longer wet. Taking this test one step further I linked the leak sensor to a KPL status bar. Placing the sensor in a plate of water caused the expected KPL status to light up. As I reset the KPL status each time the leak sensor flashed its LED the KPL status also came on? This repeated about 4-5 times and no other ON's were seen from the unit. As indicated above after drying the sensor pressing the reset button did not in fact change the nodes state from wet off, to dry on. It did however continued to send another ON to the KPL status bar?? I am not sure why the engineers have decided to go this way but find this a little odd. I will be testing a couple more later this week and see if they react the same. Right when you thought you knew the expected behavior of how these things operate. Surprise . . .

Hello Michael, For the benefit of the forum members can you please indicate what the sticker says for the hardware production date is along with the ISY firmware version.

Yes . . .

Very strange another person is having similar issues unless he physically taps the sensor. Can you try to adjust the sensitivity to its maximum and see how it reacts? http://forum.universal-devices.com/topic/16663-motion-sensor-question/

That's a good step. Ideals are peaceful - History is violent

Its funny you're asking about this problem and another member in the SH forum as well. Our resident Tfitzpatri8 offered up this possible solution so give it a try and report back. http://forum.smarthome.com/topic.asp?whichpage=1&TOPIC_ID=17063#91751 Essentially he asked if anyone had tried to link all One Link sensors to the Smoke Bridge. Could it really be that easy to obtain the low battery warning when such a condition exists? I will give this a go on the week end and report back if no one beats me to it. Ha . . .

Do you have a recent back up image? If so you can do a File - Restore Backup, and yes doing the *Restore PLM* does take a considerable amount of time. If it takes under two minutes either your network is extremely small or there are issues. How many devices do you have? Do you have extensive programs and scenes created with in the ISY Series Controller? If your answer is: I have a very small network of less than 10 devices and also don't have a lot of complex scenes and programs. Ultimately its up to you to decide the risk vs reward in starting from scratch. I always try to pursue the tried and true methods as listed above before going the route of a replace PLM. Also please keep in mind please don't confuse a lack of updating or no response to a bad PLM recovery. I call this out because many of us have experienced where you're login to the Admin Console thinking all is well and you're fully connected. When in reality you're not connected and will not see live up to the moment updates in the console. I have been dealing with this exact issue for years and it appears to be getting worse. I just finished another new install where the same behavior was seen on another brand new ISY Series Controller. We were adding new leak, on-off, and open-close sensors. The system didn't appear to do be doing anything?? Closing and opening the Admin Console the first time showed the one device was indeed added but had pending writes. The On-Off plugin relay did not add and using the add new device did absolutely nothing so did a tap and link method. This time the device showed up but again there were writes pending?? Doing a write device caused the system to write and complete the enrollment. Moments later pressing the On-Off relay module would not show the actual state. So once again I closed the Admin Console and the system was able to reflect the status. I am unsure why this behavior happens but its really frustrating when trying to commission a new install and all the basics are in place. As aside please do ensure you have proper coupling / bridging in your network as confirmed via the 4 tap (beacon) test outlined in the 2413S PLM guide. Also please ensure your PLM is not hampered by any UPS, chargers, computers, etc. None of these were my issues because I was sitting in a completely brand new and empty home. So there are no noise makers / signal suckers involved here. Besides the network was also filtered so can't explain why the system continued to show no live status.

Hello Simon, Are there existing budget constraints to solve this problem? I ask because the web based switch which I indicated about *Ping Alive* would be a possible solution to this. http://www.digital-loggers.com/lpc.html

Understood about missed data if the server happens to be off line etc. But, I am sure most people can appreciate these are things that need to be kept top of mind. I also have to gather those going this route would have to accept the fact this is not the primary method and is an auxiliary method to bolster an existing system in place. I already have lots of over lap in some areas but I like the fact your node server solution will finally offer features sadly missing in its current form. ie. Your node server will offer amps, pulse, temperature, which are not available.

Another silly question have you considered placing a wait in the program before it fires off the e-mail? It doesn't really address the fact the sensor is firing off two open commands. But gather this is being done to insure the signal is getting through give it a try. Also, can you bring up the level 3 error logs and toggle the device to single node and also disable the repeat ON. Perhaps the ISY needs to be updated to see if these options are even supported correctly. I would submit a ticket to UDI referencing this thread and I am sure they will figure out what is happening.

Hello Simon, I thought this issue was addressed in your other related thread where you posed the same Q, no? http://forum.universal-devices.com/topic/15752-synchrolinc-is-the-power-consumption-of-my-device-too-low-to-use-it/?do=findComment&comment=135175

I wanted to add some visual aids for those who don't have full ZigBee integration to their Brultech GEM system. Below is how the nodes are represented in the system as of today called nodes In another screen capture called Main 1 you can see what the system currently provides. I would like to see all 32 channels show the current / amps but also have direct access to those values in scenes and programs. As can be seen in this image the ISY does not show or reflect the amps as global counter. In another screen shot called single channel there are only two items available for viewing. One being the ever changing watts that fluctuate from moment to moment based on the send interval from the GEM. The other is the total KWH consumed for that specific channel. I would like to have the ability to reset KWH counter only in the ISY Node Server and not on the GEM or ISY Series Controller. Ideally there would be two counters one acting as a monthly counter and the other a global counter like an odometer on a vehicle which could also be reset but only on the ISY Node Server. I am making this distinction because there are use cases where you want to keep the total value but not impact the GEM's real time counters. Also, it would be great if you could incorporate the following values in each channel to be viewed and tracked: current watts, low watts, high watts.

As part of the replace process the old PLM address is replaced with the new. I would try this one more time ensuring the following is done in correct sequence. 1. Unplug PLM. 2. Unplug ISY. 3. Plug back PLM and wait about 10-30 seconds. 4. Plug back the ISY Series Controller and wait for it to be fully operational and no *busy writes / reads* are in progress. 5. Select the File -> Restore PLM. Go grab a hot cup of coffee and do something else.

The Smoke Bridge in my environment is linked to a 120 VAC hardwired smoke in the hall way outside of the bedrooms. The other 120 VAC hardwired unit is in the basement by CEC code. The other ten units are battery only which eight are the smoke / CO variety. Since living through a massive lightning storm about five years ago which took out two 120 VAC Kidd alarms. I wanted to insure if the hardwired units were some how impacted by a electrical event these remote units would still be on guard and ready to protect the family. Since installing a secondary surge protector and a optical relay the above condition isn't much of a concern to me. But you still have to plan for those unknowns in case those strategies fail.

Um . . . What the heck happen to Paul's reply??? Based on Paul's reply now that I think about it I believe he is on to something. The One Link system is supposed to link all smoke alarms to one another. As far as I am aware this is only intended to *alert* in unison if there is a smoke, fire, CO condition. If any device has a fault or battery condition only that single device will do the low battery chirp / LED notification etc. You will not hear the linked devices doing the same otherwise how would you know which device was needing assistance? Since the Smoke Bridge is linked to only one device my belief is a low battery condition is only declared for the single linked device. If so this is unfortunate but seems to be expected behavior and limitation of balancing of declaring which unit needs attention. As can be seen the last low battery alert I received was on October 21, 2013. Mostly due in part to changing out all devices to use high output long lasting lithium cells. Also, depending on the location regardless of battery voltage the unit is replaced with fresh batteries as part of my cUL certification regimen on a annual basis.

Can you advise which model you have on hand? Hard wired 120 VAC smoke, battery operated smoke only, battery operated smoke / CO? Have you tried to hard reset the smoke bridge and delink and perform the same test? Or perhaps link to the other smoke detector? Ideals are peaceful - History is violent

Nice . . .

Did you in fact follow all the steps for a replacement of the PLM outlined in the Wiki?