Michel Kohanim Posted April 10, 2015 Share Posted April 10, 2015 Hi oberkc, It all depends on the version of the firmware: older firmware didn't support IDREQ and thus AutoDiscover will not work. Most new sensors that support I2CS also support IDREQ. There's really nothing wrong with version 0.0 except that in the case of these sensors, the version has meaning as to the functionality (i.e. does it have heart beat, etc.). With kind regards, Michel Link to comment
oberkc Posted April 10, 2015 Share Posted April 10, 2015 Hi oberkc, It all depends on the version of the firmware: older firmware didn't support IDREQ and thus AutoDiscover will not work. Most new sensors that support I2CS also support IDREQ. There's really nothing wrong with version 0.0 except that in the case of these sensors, the version has meaning as to the functionality (i.e. does it have heart beat, etc.). With kind regards, Michel Yeah, I haven't really been worried about it. I was partly reacting to mike ippolito's comment that v0.0 was an indication of a faulty linking process, but I have seen nothing that makes me suspect any problems (other than one ALL ON event that happened simultaneously with one sensor triggering). Status seems correct every time I check, and the update is pretty quick, making me suspect good comms. Both of my sensors have heartbeat and battery nodes, along with open/close. I thought these were relatively new to me, but my ability to judge time is not as good as it once was. I am simply more curious than anything. I enjoy the experimentation. Link to comment
Michel Kohanim Posted April 10, 2015 Share Posted April 10, 2015 Hi oberkc, Mike is partly correct since, the new ones, do not have the battery mode and the only way to figure it out is to know the firmware version. I am glad you like the experimentation! That makes one of us!!! With kind regards, Michel Link to comment
doctorjerry Posted April 17, 2015 Author Share Posted April 17, 2015 I just received a new 2843-222 open/close sensor. It has no jumper pins whatsoever. Is this some new version, or did I receive a bad unit? I called smarthome, but I got no answer. I thought I'd ask here before returning it. Link to comment
LeeG Posted April 17, 2015 Share Posted April 17, 2015 The Specs and User Manual indicate the pins should be there. What is the Open/Close 2843-222 firmware level? Are the two pins there without the jumper in place? My latest is v.40 firmware and it has the Jumper? Link to comment
doctorjerry Posted April 17, 2015 Author Share Posted April 17, 2015 Unit say 4614REV 1.B In ISY v.43 No pins at all. Just the two empty holes in the board where they should be. Link to comment
Teken Posted April 17, 2015 Share Posted April 17, 2015 Unit say 4614REV 1.B In ISY v.43 No pins at all. Just the two empty holes in the board where they should be. Does it still have the two screw terminals for external sensor use? Link to comment
doctorjerry Posted April 17, 2015 Author Share Posted April 17, 2015 And the interesting thing is it seems to be registered in the default mode. I would have expected the multi-scene mode if the pins were just missing, because that would be like taking off the jumper. This is the event log for on and off 1. Fri 04/17/2015 12:15:59 AM : [ 36 FB EF 1] DOF 12. Fri 04/17/2015 12:15:59 AM : [ 36 FB EF 1] ST 03. Fri 04/17/2015 12:16:01 AM : [ 36 FB EF 1] DON 14. Fri 04/17/2015 12:16:01 AM : [ 36 FB EF 1] ST 255 And for future reference Lee, could you explain the 4 lines to me? Link to comment
doctorjerry Posted April 17, 2015 Author Share Posted April 17, 2015 Yes, the terminals are there. It looks just my other unit except for the missing jumper pins. Link to comment
LeeG Posted April 17, 2015 Share Posted April 17, 2015 Sure. The first two lines are generated when the device sends an Off command (DOF is Off command, STatus 0 = Off) The last two lines are generated when the device sends an On command (DON is On command, STatus 255 is On) 1. Fri 04/17/2015 12:15:59 AM : [ 36 FB EF 1] DOF 12. Fri 04/17/2015 12:15:59 AM : [ 36 FB EF 1] ST 03. Fri 04/17/2015 12:16:01 AM : [ 36 FB EF 1] DON 14. Fri 04/17/2015 12:16:01 AM : [ 36 FB EF 1] ST 255 A LEVEL 3 trace shows the actual messages containing the commands. 0x11 is On command Fri 04/17/2015 01:07:20 AM : [iNST-SRX ] 02 50 31.BD.14 00.00.01 CB 11 01 LTONRR (01) Fri 04/17/2015 01:07:20 AM : [std-Group ] 31.BD.14-->Group=1, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:20 AM : [D2D EVENT ] Event [31 BD 14 1] [DON] [1] uom=0 prec=-1 Fri 04/17/2015 01:07:20 AM : [ 31 BD 14 1] DON 1 Fri 04/17/2015 01:07:20 AM : [D2D EVENT ] Event [31 BD 14 1] [sT] [255] uom=0 prec=-1 Fri 04/17/2015 01:07:20 AM : [ 31 BD 14 1] ST 255 Fri 04/17/2015 01:07:20 AM : [iNST-SRX ] 02 50 31.BD.14 00.00.01 CB 11 01 LTONRR (01) Fri 04/17/2015 01:07:20 AM : [std-Group ] 31.BD.14-->Group=1, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:20 AM : [iNST-DUP ] Previous message ignored. Fri 04/17/2015 01:07:20 AM : [iNST-SRX ] 02 50 31.BD.14 00.00.01 CB 11 01 LTONRR (01) Fri 04/17/2015 01:07:20 AM : [std-Group ] 31.BD.14-->Group=1, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:20 AM : [D2D EVENT ] Event [31 BD 14 1] [DON] [1] uom=0 prec=-1 Fri 04/17/2015 01:07:20 AM : [ 31 BD 14 1] DON 1 Fri 04/17/2015 01:07:20 AM : [iNST-SRX ] 02 50 31.BD.14 22.80.0B 41 11 01 LTONRR (01) Fri 04/17/2015 01:07:20 AM : [std-Cleanup ] 31.BD.14-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Fri 04/17/2015 01:07:20 AM : [iNST-DUP ] Previous message ignored. Fri 04/17/2015 01:07:21 AM : [iNST-SRX ] 02 50 31.BD.14 11.01.01 C7 06 00 (00) Fri 04/17/2015 01:07:21 AM : [std-Group ] 31.BD.14-->11.01.01, Max Hops=3, Hops Left=1 Fri 04/17/2015 01:07:21 AM : [iNST-INFO ] Previous message ignored. Fri 04/17/2015 01:07:21 AM : [iNST-SRX ] 02 50 31.BD.14 11.01.01 C7 06 00 (00) Fri 04/17/2015 01:07:21 AM : [std-Group ] 31.BD.14-->11.01.01, Max Hops=3, Hops Left=1 Fri 04/17/2015 01:07:21 AM : [iNST-INFO ] Previous message ignored. 0x13 is Off command Fri 04/17/2015 01:07:28 AM : [iNST-SRX ] 02 50 31.BD.14 00.00.01 CB 13 01 LTOFFRR(01) Fri 04/17/2015 01:07:28 AM : [std-Group ] 31.BD.14-->Group=1, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:28 AM : [D2D EVENT ] Event [31 BD 14 1] [DOF] [1] uom=0 prec=-1 Fri 04/17/2015 01:07:28 AM : [ 31 BD 14 1] DOF 1 Fri 04/17/2015 01:07:28 AM : [D2D EVENT ] Event [31 BD 14 1] [sT] [0] uom=0 prec=-1 Fri 04/17/2015 01:07:28 AM : [ 31 BD 14 1] ST 0 Fri 04/17/2015 01:07:28 AM : [iNST-SRX ] 02 50 31.BD.14 00.00.01 CB 13 01 LTOFFRR(01) Fri 04/17/2015 01:07:28 AM : [std-Group ] 31.BD.14-->Group=1, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:28 AM : [iNST-DUP ] Previous message ignored. Fri 04/17/2015 01:07:28 AM : [iNST-SRX ] 02 50 31.BD.14 22.80.0B 41 13 01 LTOFFRR(01) Fri 04/17/2015 01:07:28 AM : [std-Cleanup ] 31.BD.14-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Fri 04/17/2015 01:07:28 AM : [iNST-DUP ] Previous message ignored. Fri 04/17/2015 01:07:28 AM : [iNST-SRX ] 02 50 31.BD.14 13.01.01 CB 06 00 (00) Fri 04/17/2015 01:07:28 AM : [std-Group ] 31.BD.14-->13.01.01, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:28 AM : [iNST-INFO ] Previous message ignored. Link to comment
LeeG Posted April 17, 2015 Share Posted April 17, 2015 Will need another report from someone with v.43 to see if a manufacturing error or change that dropped Multi Scene Link to comment
Brian H Posted April 17, 2015 Share Posted April 17, 2015 It will be interesting to see if another firmware v.43 module has the Multi Scene removed. Could be the sales page and manuals are not updated yet. As the manual I just downloaded was published on 05/21/2013. Link to comment
doctorjerry Posted April 17, 2015 Author Share Posted April 17, 2015 Smarthome said the jumper has been eliminated and the change in mode is now done through software. They offered no help whatsoever in how to accomplish this. The phone rep seemed to know nothing himself, but relayed the message from someone else in "tech support". He did say that the Insteon Hub could not do it and knew nothing about the ISY. Then he quickly excused himself and said goodbye. I must say it was a miserable experience. Hopefully the savvy guys here can get further than I can. Link to comment
Teken Posted April 17, 2015 Share Posted April 17, 2015 Smarthome said the jumper has been eliminated and the change in mode is now done through software. They offered no help whatsoever in how to accomplish this. The phone rep seemed to know nothing himself, but relayed the message from someone else in "tech support". He did say that the Insteon Hub could not do it and knew nothing about the ISY. Then he quickly excused himself and said goodbye. I must say it was a miserable experience. Hopefully the savvy guys here can get further than I can. I would have to gather this will be like the heart beat node appearing in the Open / Close sensor as it never had it before. More than likely UDI will once again have to reach out to someone at Smartlabs and determine what *Magic* needs to be added into the next firmware release to take advantage of this new firmware feature. As I have stated many times here and abroad in other forums. Smartlabs inability to take just a small amount of time and communicate to their internal staff never mind to the general public. Is truly astounding and continue to show the piss poor consideration for the consumer! This is 2015 and they have half a dozen methods to inform and update the consumer and their tech support. Yet at every turn they fall miserably on their face and let the general public beta test yet another new *feature* You know the phrase STUPID is not lightly used when addressing someone. But, in this case after 10 freaking years Smarthome / Smartlabs truly embodies STUPID on all levels of communication and deployment. Link to comment
doctorjerry Posted April 17, 2015 Author Share Posted April 17, 2015 I decided to try email to Smarthome tech support and did get a quick response as follows: Thank you for contacting Insteon. UDI did not get the update in time to add to the latest firmware release. The ability to set that will be in the next beta firmware release that they make. In the mean time, you can use programs to accomplish what you are trying to do until the update is pushed out. Link to comment
Michel Kohanim Posted April 19, 2015 Share Posted April 19, 2015 Hi doctorjerry, Unfortunately we were not privy to this change at all. Thankfully one of our beloved SmartHome reps noticed the issue on the forum and immediately notified us and provided us with the necessary information. We are waiting for a unit to test. With kind regards, Michel Link to comment
doctorjerry Posted April 19, 2015 Author Share Posted April 19, 2015 I'll quote my favorite movie (Cool Hand Luke) ' What we got here is a failure to communicate' Link to comment
Brian H Posted April 19, 2015 Share Posted April 19, 2015 Michel; They have not even updated their sales site or manuals yet. So you are not the only one in the dark. Link to comment
Michel Kohanim Posted April 19, 2015 Share Posted April 19, 2015 Hi Guys, I feel a lot better! I just wish we did know about it before our official release. With kind regards, Michel Link to comment
doctorjerry Posted May 9, 2015 Author Share Posted May 9, 2015 I have my program to notify me when the garage door opens and closes working well. But I'd like to refine it. When I enter or leave I get two messages, door opened then door closed. I'd like to avoid the door closed message unless it doesn't close within 5 minutes. Perhaps a timer that starts when the door opens and waits 5 minutes before sending a door open message. If the door closes within that time the timer stops and no message is sent. I have the idea, but no clue how to program it. Any help is appreciated. Link to comment
LeeG Posted May 9, 2015 Share Posted May 9, 2015 doctorjerry I was a little confused about which message should be suppressed, first thought Closed message but detail about Wait sounds more like the Open message (and Closed message) should be suppressed. Also need to know if the I/O Linc Sensor is On or Off when Open and if Trigger Reverse is used. Suggest posting the current Open and Closed message Programs along with which message should not be issued as well as info on I/O Linc Open/Close Sensor state and use of Trigger Reverse. Link to comment
MFBra Posted May 9, 2015 Share Posted May 9, 2015 There are many experienced contributors here that may have better ideas, I'd suggest you to have 3 programs (you may solve with 2, but this way you may find other applications also) 1- GD OPENED NOTIFY RUN PROGRAM 2 then path 2- GD TIMMER (normally disabled) no conditions Wait x minutes Notify GD still open You may include here some repeat clause to keep informing you about the door. I have a "growing counter" for this, first starts with 5, then doubles (10,20,40...) does not bother that much but still remembering you about it. (Without considering any potential risk, you may here command the door to close, you should have to detect if is safe to close) 3 - GD CLOSED STOP PrOGRAM 2 The program 1 will start the timer after notifying you, the TIMMER will keep running and notify you after some time. If the door close it will stop the TIMMER and no notification will be sent. Enviado do meu iPhone usando Tapatalk Link to comment
doctorjerry Posted May 11, 2015 Author Share Posted May 11, 2015 MFBra, Thanks, you got me over the hump and I've come up with a pair of programs that accomplish my goal. Most of the time I get only the one open message. But if I get two more open messages I can then close the door manually using Mobilinc. Program 'Garage ® Open1' If Control 'Wireless Sensors / Garage Door Sensor®-Opened' is switched On Then Send Notification to 'Text Message' content 'Garage Door Open' Wait 5 minutes Run Program 'Garage ® Open2' (If) Wait 15 minutes Run Program 'Garage ® Open2' (If) Send Notification to 'Text Message' content 'Diane's Garage Door Open' Wait 15 minutes Run Program 'Garage ® Open2' (If) Send Notification to 'Text Message' content 'Diane's Garage Door Open' Else - No Actions - (To add one, press 'Action') Program 'Garage ® Open2 If Status 'Wireless Sensors / Garage Door Sensor®-Opened' is Off Then Stop program 'Garage ® Open1' Else - No Actions - (To add one, press 'Action') Link to comment
Techman Posted May 28, 2015 Share Posted May 28, 2015 As of 5/25/15 the current shipping version of the open/close sensor(2843-222) is Rev 1.B, V.43. There is a manual specifically for the 1.B release that shows the absence of the jumper. However there's no mention of the Heartbeat node. The ISY still shows this as a TriggerLinc model 2421. I haven't found a way to access the 3rd "closed" node Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.