Teken

Though I haven't been able to speak with a Fire Marshal, the information I've been able to gather suggests the auxiliary alarm relays manufactured for 120v 2/4 wire systems are not rated for or advised to be used with security systems. Lots of problems seem to occur outside of the fact this type of installation violates the NEC/NFPA and will void any warranties on equipment. They seem to be manufactured to trigger auxiliary warning devices as sirens and lights only. There appears to be no way to legitimately connect a 120v unmonitored smoke detector system to the security panel. Jon Hello Jon, As I indicated in my previous post above. Here in Canada this is the method we use to interface a hardwired smoke / co device to an alarm system panel. This has been used and deployed around Canada for more than 30 years and millions of homes are wired this way. The NEC may have a specific reason for not allowing it. But, rest assured it works, and if properly installed will protect the occupants from a fire / smoke condition. I hope you're able to find a solution to your current problem. I just wanted to offer you some insight and perhaps a solution to your needs. Teken . . .

How'd you rig up this relay system. Thanks, Jon Hello Jon, The first thing you need to do is confirm if this method of connection is allowed in your city, county, etc. I live in Canada and this sort of configuration and hook up is allowed to ensure smoke, heat, co detectors can be monitored. Look up via Google two / four wire hook up for smoke alarms. Teken . . .

Wired sensors (and I'm referring to power) are available but none that I'm aware of will transmit as some wireless sensors do. I wanted to keep the hard wire so the battery would merely be backup but all in all it's looking easier to just swap 'em out with wireless transmitters Jon There is nothing stopping you from doing what you're asking. As I have my system wired in the exact same fashion you have indicated. I have my original KIDD smoke / co detector wired via a relay system to the security alarm system. Which is monitored by the alarm company for smoke, fire, co, etc. This device is in the basement in my home. In the hallway I had another hardwired 120 VAC KIDD smoke / co unit. I simply replaced that hallway unit with a First Alert Onelink smoke sensor. This hardwired Onelink sensor is connected wireless to all of the other smoke / co units in my home. From there, it is linked to the Insteon smoke bridge to my network. Works just fine and allows you to have all of the above with out compromise. The only thing I needed to follow up and confirm is if I link the smoke bridge to the smoke / co talking combination sensors is if it will actually register and send a low battery alert to the smoke bridge. As the hardwired 120 VAC Onelink sensors do not speak or indicate zones etc. So, I am going to test if the ones that do speak and can tell the user the battery is low etc will change the low battery node in the smoke bridge. I hope to complete this test by the end of the month. Teken . . .

I wanted to chime in here and thank everyone for sharing how to set up a v.40 and above KPL to integrate with the Fanlinc. I have been putting this off for quite sometime and just got around to doing this. The picture from LeeG helped out tremendously to understand what needed to be done. Incidentally, my helper did not notice that the Controller node was the one being modified to turn off the secondary responder buttons. This caused a few moments of head scratching and I then reviewed the link from LeeG, and it was clear the modifications were done to the Controller, and not to the Scene Pallet. Now, all I got to do is install 6 fans, fanlinks, and 10 KPL's. Teken . . .

LeeG, After thinking about this for a little while. I am thinking due to the complex environment in my home. I will need to test this low battery alert on a one link module that can talk. I have three types of the First Alert One Link Sensors. Smoke Only Battery Operated: This was the device that had the low battery alert which did not notify the Smoke Bridge. I have two of these units. This device is not linked directly to the Smoke Bridge. Hardwired 120 VAC / Battery Smoke Only: This device is linked to the Smoke Bridge. This device can not talk or alert the user of the zone / area. This unit is also wired to my security system and is tied to the alarm monitoring station for a fire condition. There is only one of these units. I then have nine battery operated smoke / CO units in various parts of the home. I think I will link the Smoke Bridge to the combination Smoke / CO units and see if the the response is different. I guess I will have to endure a whole day of beeping! Teken . . . Encrypted By: Phoenix Security Solutions

I finally got a chance to install and test the smoke bridge. So far it looks like the alert notification for Smoke, CO, Low Battery, Malfunction come in while pressing the Set button on the device itself. I have been able to link all the required lights and sirens I want during these events. It appears to activate all things linked as I would hope. I know others have wondered about the Low Battery alert notification. As of this writing one of my smoke alarms began to chirp. It did not initiate a signal to the Smoke Bridge, I am guessing the voltage is too high? Both AA batteries measured 1.375 VDC for the device in question. I would be interested to know from First Alert / Smarthome as to when the low battery signal is sent off? As the device does in fact sound off indicating the battery is low. I gather this threshold is much higher than what the Smoke Bridge considers low? Since I was already going to change out the battery I decided to complete the review. I performed a *Test* on the First Alert One Link module. It did in fact signal the Smoke Bridge and I received all the e-mails & text sms to all the phones I had programmed. It looks like this product is very solid and does perform as advertised. Teken . . .

Hello Michel, Are you currently using ISY Firmware 4.04, along with GEM COM 1.99, Engine 1.41 for your testing? I am using ISY Firmware 4.04, along with GEM 1.96, Engine 1.41 and have been unable to get the GEM or the ISY to display all 32 channels. I have removed the 7 nodes, removed the node in the diagnostic window, along with rebooting both the GEM / ISY to no avail. Ben has indicated that GEM firmware 1.99 is not yet available for release for public consumption. In your mind is the GEM COM 1.99, along with the ISY Firmware 4.04 working as expected and correct? If so, I shall reach out to Ben and request that this release be made available as it currently the energy management does not function at all. Teken . . .

Hello Michel, I have left my replies also in the Brultech forum and will await Ben's reply as to next steps. Please confirm the firmware you are using for the GEM for me in case I am not at the latest release. I am currently on COM 1.96, Engine 1.41 as this resolved a few com issues along with the inclusion of the secondary packet format type option. I believe once I receive my Dash Box and the firmware for both the GEM / Dash Box has been some what finalized. That the primary channel will indeed use the ISY packet format. The secondary channel will be set to what ever format (Binary) Brultech deems necessary to communicate to the Dash Box. The Dash Box will in turn take the accumulated data and push it to the SEG site. The ultimate goal is to have local / remote data capturing. While having the ISY see the power, current, volts, KWH used and thus control the Insteon network. I know this is the first go round for the GEM via the ISY-994iZ IR Pro. So, progress is being made! Once again, thank you for your continued support and development of the GEM to interface to the ISY. Teken . . .

OK, after about one hour of trouble shooting the following are my observations. It appears that the latest 4.0.3 firmware is over writing the GEM's *Primary Packet Format* from my SEG Format, to the ISY Format. This explains why my SEG has been down for almost two hours. I believe the solution is to code the next ISY firmware to send ISY Format packets using the *Secondary Packet Format* channel, as the Primary Packet Format channel is reserved for the SEG. It also appears that the other packet formats are grayed out in the secondary channel, there for the secondary channel must be used to send ISY data packets. I was able to obtain all 32 channels at one point. Later I was also able to see the huge power readings Michel had observed. All other box's were indeed blank. In the interim I have disabled the Zigbee on the ISY, as it continuously took control of the GEM, and rewrote the primary packet format channel as ISY. So, I hope this proves helpful. Teken . . .

Hello Mitchel, The previous 7 nodes were removed. The GEM was also removed via the diagnostic menu. The ISY began to add in the 32 GEM channels. Sorry to report all 32 channels remain blank. I have rebooted the ISY, the compatibility mode has been toggled to all with no positive change. I am thinking perhaps its because the GEM is set to emulate 1 ecm 1240? Also, since this new firmware release, should the GEM not be programmed to start to use the ISY format packet? Insight Teken . . .

Installed 4.0.3 with out issue. The GEM was showing some limited data on the ISY prior to the upgrade. Now, the ISY does not show anything in the first 7 channels. I have to gather I have to change the GEM back to simulate three or more ecm-1250's? Please confirm if this is the case . . . If there is a step by step guide as to what I should be doing in either controller(s) please do let me know. I will pose the same question to Ben at Brultech and hope they can provide some insight. Since they do not have a ISY controller I am hoping this 4.03 firmware build was tested on UDI's GEM unit. If so, please do let me know what settings need to be configured to see all 32 channels etc. Teken . . .

Selecting the test button with the high lighted group will only send a broadcast to those listed. Teken . . .

I am subscribing, as I too am interested in the final outcome. Teken . . .

I know I was able to do this on a older KPL. It was done by accident at the time of programming. This was about the same time I noticed that the ISY did not track and follow what I expected the levels the system said it would? Pressing the levels in both up and down to achieve the back light was fruitless. Now, somewhere doing the manual method I was able to do exactly what the OP stated. Keep in mind the LED is still lit (even if extremely dim) when pressed. But, for all intent its as close as you can get to being off / dimmed off. Teken . . .

My personal experience with metal box's is the dual band is pretty none existent. In Manitoba metal box's are required for new home builds. Retrofits, or home owner jobs can use any of the none metal box's. I plan on using the fiber style boxs as they are stronger and don't flex / break. Teken . . .

Hello Alan, Perhaps you would research for a strain gauge element. http://en.wikipedia.org/wiki/Strain_gauge If you find anything that is value priced, please do let me know. As I too am interested in something that would inform me of the presence of a occupant. Teken . . .

Perhaps we are not on the same page. I had no problem using the link you provided on the LAN, but how does that help me accessing the Admin Console remotely using HTTPS ? If the Touchswitch is pointing to a different UI how is this corrected? Teken . . .

Hello Michel, I have appended both the certificate and the encryption level the browser is using. All of which makes no difference in the ability to access the ISY via HTTPS. Also, my reply about accessing the ISY was to the public address using HTTPS. Upon selecting the public address using HTTPS, I have no problem getting to the Touch Switch home page. Upon selecting the *Admin Console* at the bottom of the web page when the Admin Console launches it produces the two listed error's which I have already appended to this thread. I only access my ISY Insteon network via HTTPS and it has always worked. Now, with the latest release I do not have the ability to do so. I hope this information provides more insight to the matter. As always, much thanks and look forward to a solution. Teken . . .

I am using SSL v3 which I have confirmed with you, and also provided a screen shot of such. The HTTPS access issue is still present so I am not sure how it can be related to SSL v2. I have done absolutely nothing to any of the 6 computers in my home. Simply rolling back the ISY firmware corrects this issue. Now, for the sake of doing a test to confirm and validate my findings for the benefit of the forum members. I have also uninstalled Java, installed the latest and greatest. Removed the certificate from all known browsers and requested a new cert be generated using any level of encryption with out success. All browsers have been cleared of cache / cookies, along with the Java console. Adjusting every browser to the lowest security setting along with adding the ISY to every known fire wall, policy, and to the browser has no affect. Simply put, I am out of ideas as it pertains to why this latest version of ISY does not allow HTTPS access either locally on the LAN, or remotely. Teken . . .

Michel, That is a great gesture and is much appreciated. But, my comment is about the SmartLinc is that it provides me the ability to access the home with out network related issues. As long as you can access a web page / address the home is accessible. The ISY relies on a Java application which in many environments do not allow such apps to run, or be hindered when its required to launch. Having said all of this: My feed back is to provide the information pertaining to issues that affect the ISY and those members. Is this not why this forum and thread is here for?? Lastly, as I stated previously above, rolling back to the last stable ISY firmware corrects this HTTPS issue. This is not related to my homes network or any firewall, or policies. I hope this is clear on all points and appreciate the on going support the team has provided. Teken . . .

I continue to experience this problem. It is not my computers or the network at home either. Rolling back to the previous versions corrects this problem. Now, at work our firewall and policies are at play so I have no expectation in connecting. This is why I am a firm believer is using the SmartLinc. No headaches with Java and all of the frustrations in making it work. Just silly . . . Teken . . .

I would like to know if this is on the UDI road map. In the House Linc 2 the software application has the ability to upload new updates to any RF Motion sensor. Once the user awakens the RF Motion sensor it will remain in a ON state to receive any new updated programming. I know this question has been asked quite a few times and I have received various replies in some cases. But, unless I am missing the obvious how is this accomplished *Assuming* this feature exists? To be clear I am asking that (I) simply have to walk in the path of the RF Motion sensor to awaken it, and then the unit will remain in this state until all new programming / firmware updates are loaded. Currently, I have to climb up on a blasted ladder and remove said sensor, remove screw, cover, and then hold the idiot button until the LED starts flashing. Having more than 12 of these sensor(s) deployed and some being as high as 20 feet on the outside is NOT a fun task! I would greatly appreciate if THIS feature could be pushed forward in the next few releases. As this is one of the major holes lacking in the power of the ISY platform. Much Thanks Teken . . .

Hello Michel, I have enclosed a screen shot of the certificate Opera is using. Please note I am getting the same errors with IE 8. I will submit my remote URL now to the support address now. Teken . . .

Hello Michel, I normally use Opera (Version 12.02, Build 1578) on all of my machines which has the same problem. I will try using IE / Chrome and see if it makes a difference today and report back. Teken . . .

I have no problems getting to the web page which uses the *Touch Switch* interface. It is when you click on the Admin Console you see the Java whirling wheel trying to load. About 5-10 seconds the two pop up messages appear: XML Parse Error HTTPS: xxx.xxx.xxx.xxx desc appears. The second pop up is what I have uploaded here. Teken . . .