junkycosmos

Posting a quick note overhere incase anyone else is looking for it. There appears to be some issue with Mobilinc connect since Sat 6/4/22 evening. Bit of a discussion about it over here https://forum.universal-devices.com/topic/36731-unable-to-access-994i/#comment-340580 Noted that I am not affilited with Mobilinc but rather user/subscriber for last decade

@stillwater Completely agree, this is not resolved.. also I too emailed Wes (Mobilinc owner/founder) yesterday morning who for the last 12+ years has provided quick solid support to myself and others here. It is very much not like him not to reply so I hope nothing too bad is up here. Edit: also posted pointer message in Mobilinc Forum to this thread:

same here, 4 ISYs all having issues connecting to Mobilinc connect. I did try rebooting 2 of them, no change. Phone app shows "checking" when I try to check license status. All four are paid up in recent months. My guestimate on when this broke is sometime Saturday 6/4 evening. Changing my mobilinc app on phone to direct IP of my ISY works fine so clearly seems to be Mobilinc issue

Will the ISY support a XC SD card or only the HC ? I understand the 32GB limit and I am not interested in larger size but rather fastest possible SD. I looked this AM and the fastest SanDisk A2 U3 v30 cards only come in XC (extended capacity) format at 64GB. While going to a 32GB card drops to A1. I take it the XC format is not recognized by ISY ?

KSchex, Have you been in touch with UDI to report what you are seeing with the missed messages in a smaller setup ? Seems that might be ideal given limited factors at play vs some of the more complicated setups trying to troubleshoot. Your comment noting on V5 also caught my attention since my ISY is busy and sometimes checks out in v4 but due to having a lot of nodes. The extra resource use on V5 has me hesitant to move to v5. All, Regarding mimo lite (not the mimo2); when power is removed and reapplied they do falsely report status of the relay and sensor as ON regardless of real state. However a query does then report correct status. I too am curious on the mimo2 when anyone tries it with ISY.

I called SH just now and they noted V2.5 is the current PLM version and yet they might have old version of v2.4 which could ship out instead if we ordered today. I also see on the SH sales info page the 2413s now supports 2,000+ links so maybe v2.5 has new chip ?

I updated the other PLM (massive thread) with pictures on v2.4 internals for a unit that arrived today. I was going to ask about the 2000 link reference here too since the box for the v2.4 that showed up says "Supports up to 1,000" links

did the restore PLM again just now and it appears to have worked but 2 things I will note 1. this time I have a flood (5 minutes of status bar scrolling too) with these messages in the log "MNG-LNK-RSP" ... that is new! 2. did another PLM link count after restoring .. this time its still running and counting aroung 1882 and still running. Keep in mind my counts for prior restores were 600 then 900 something. progressive growth but then given the issue/bug of plm count timing out who knows what was valid prior. so .. if I didnt know better I would be inclined to think the ISY is corrupting the PLM, really strange and of course not the ISY here as code is on 4.62 oh it finished .. 1888 links .. ? Really .????

just had another occurance of this PLM losing all links. Again ZERO communiction problems other than the entire PLM losing its DB. doing another Restore PLM now

Also noticed SH is now carrying Smartenit 5010N PLM too although I understand from UDI this is untested with ISY https://www.smarthome.com/smartenit-5010n-zbplm-zigbee-insteon-x10-interface.html https://smartenit.com/product/zbplm/

Thanks for the replies. I forgot to include the version info in my original post I installed it 4/28/16 , V2.2, date code 1611 (so it was born 11th week of 2016) To be clear when these events (all three) have happened: the PLM remains 100% functional for communication, can control, query devices fine. LED is on bright green. Only issue is that its MEMORY (aka link data base) has gone missing. Brain H, thx for the link that that capacitor repair thread. All failures in that thread appear to be power supply related side. I'm thinking the power supply side here is good? I did a re-read of it and saw your post mentioning possibly serial chip failures, guess we might want to count this as eprom/nvam failure? Also interesting to note my prior PLM was a v2.1 date code 1534 installed 10/05/15 (removed on 4/28/16) because it had the exact same failure as this one with the PLM memory forgetting all of the link records on 4/3/16. We were doing some electrical circuit work early that month and had breakers tripped/on/off etc and figured an electric surge hit the PLM. Looks like I might want to hunt for a v2.4 now. I did also see the comment by SH that v2.3 seems to now have some fixes ...and now we are up to seeing v2.4 from some orders (per that thread) (from here) https://www.smarthome.com/powerlinc-modem-insteon-2413s-serial-interface-dual-band.html#reviews Smarthome reply: We have identified an issue that effects Insteon PowerLinc Modem (2413S - revisions prior to 2.3) where in some circumstances a component may fail if exposed to prolonged and excessive heat. In these failures the PowerLinc Modem will cease to function. To prevent such an issue from occurring we introduced a hardware change that began shipping in January 2017 (Rev 2.3).

I need this for my mother in law. She used to think funny how the house re-acts when 'i just click around with it'. My simple fix was to add a thermostat setpoint change. IF KPL.H OFF then turn HEAT to OFF. Took her 2 days to figure it out but it worked. As for grand kids; the program above if we could get Alex to talk would be grand

Hi All Was hoping others could post here with experiences similar or not to this. Three times now I have had my current PLM lose all links. Symptom is that ISY does not see when units are controlled by switches on the wall but ISY can still control and can do a query to see actual status. Diagnostics --> Show PLM links table returns empty ! Restarting ISY does not help / power cycling PLM does not help File --> Restore Modem (PLM) completely fixes the issue (in less than 2 minutes) I have had this happen three times now over last 9 months. I am inclined to think bad PLM except that doing the restore fixes this for months till it re-occurs at some random time. ALSO when this does happen the PLM can still control all units perfectly, the only issue is that PLM does not listen to any traffic from any units. PLM is 40.xx.xx V9.E; Anyone else had this happen?

I too was wondering where we are with MIMO 2+ support. Seems very close. Any thoughts on when we can change from momentary to latching such as we can with current mimolite on V4? thanks MWareman for posting your results above.

hi Ken / Khargy, Which door sensor are you deal with here?

Hi Michel and Team UDI I am so excited to see this progress here. Clearly getting into new market territory here. I do have a roadmap question, please. Been using Mobilinc connect for a few of the ISY we have 'in the wild' yet would really like to enable ISY Portal. Are there plans to let the ISY Portal and Mobilinc Connect service co-exist? Noted: IMHO the module fee here for your connected integration service is reasonable considering the possibilities. The difficult issue is loosing Mobilinc connect portal for several of these units. thanks much for the progress on the Echo J >>from module page for ISY Portal<< Remotely connect through UDI portal. No port forwarding necessary. This is a subscription for 2 years. This will deactivate MobiLinc Connect Module Additional functionality, such as Amazon Echo and IFTTT integration, in the works. Note: Please upgrade to 4.3.26 or above before installing this module.

thanks all for the input and ideas I did not mention prior but I have found this program to fit its need well for last few years. Part of the idea is to keep down on the overall number of programs to manage overall number of sensors. I have this line in the mail template form so you can see which unit triggered ${alert.event} at ${alert.date} ${alert.time24} oberkc, yes that is the intent; loop if any of the sensors finds a leak stuviews, understood on control vs status and having status break the loop was the intent jerlands/jon, Thank you for the posting of our excellent full leak package. I actually have something very similar going for monitoring of traffic from any batt powered device with 1. a variable for each device, 2. a program for each device that increments the variable when traffic is seen, 3. one program that runs fixed time every day and checks for the all variables to be X or above, IF true sends notification template and reset counts, ELSE just reset counts 4. message notification template that lists all variables and unit names Your full leak package is really nicely done and has nice boundaries on the programs too As for my little 'kink' on the low test WET monitor at start of thread: I did just experiment and when I remove the two leak sensors the ISY does not know status for then the program is FALSE. So; anyone else care to comment on the ISY making assumption that missing status = OFF ? Has it always been that way?

Water leak sensors. Must be missing something obvious here. After restart of ISY and two units do not have batteries so the ISY does not know the state of the sensors as can be seen by blank status here however this program runs TRUE and continues to stay true WaterLeakSensor WET - [iD 00D5][Parent 01EC] If Status 'Sensors / WaterLeak Sensors / WaterLeak DownBath-Dry' is Off Or Status 'Sensors / WaterLeak Sensors / WaterLeak Fish-Dry' is Off Or Status 'Sensors / WaterLeak Sensors / WaterLeak FurnaceRoom-Dry' is Off Or Status 'Sensors / WaterLeak Sensors / WaterLeak Kitchen2-Dry' is Off Or Status 'Sensors / WaterLeak Sensors / WaterLeak Laundry-Dry' is Off Or Status 'Sensors / WaterLeak Sensors / WaterLeak MasterBath-Dry' is Off Or Status 'Sensors / WaterLeak Sensors / WaterLeakUpHallBath-Dry' is Off Then Repeat Every 15 minutes Wait 1 second Send Notification to 'J_All' content 'MyTemplate' Else - No Actions - (To add one, press 'Action')

Well I restarted my router and it appears to have cleared the issue. ISY is again emailing just fine

OK me too. Looks like my ISY stopped being able to use GMAIL to send outbound mails yesterday 9/24 after 8:30pm cst. I have been using "smtp.gmail.com" for years on ISY. Now when I try testing I get an error "Mail server DNS error" and "TCP client error". I can DNS resolve smpt.gmail.com by other clients on same LAN as ISY so I am at a loss here. Per prior poster I did just check the Google setting and mine is still at "allow less secure apps" https://support.google.com/accounts/answer/6010255?hl=en

I recent ran into some issues when changing out my PLM Seems the PLM update does not flow back into smoke bridge, OR in changing the PLM the link from Smoke Bridge to ISY is broken. In other words: when updating to new PLM my smoke bridge stopped working. I tried relinking it just with the ISY and that was not a fix Instead I had to relink each alarm back to each other, then back to my smoke bridge, and smoke bridge back to ISY I also found a small issue missing from programming. I cannot set "smoke bridge - test" to be queried by a program. Having the ability to query smoke bridge test via a program would be very useful since doing a query of that node is the only way to change "test node" status from ON to OFF. The other solution would be having the node status change to OFF when testing cycle is complete HOWEVER I believe we confirmed prior that smoke bridge does not send TEST OFF. Understood that doing a query of Smoke Bridge is not really live status but I am looking to be able to turn OFF Test status via a program after X minutes, that way if another test cycle is set to ON the ISY could see it. Edit: There is a work around for not being able to query a the smoke bridge test node in a program: add it to a scene and then query the scene. This works well. program: if SB Test is on send notification, wait 1 minute, query scene with SB Test node. This effectively sets up the ISY for next "test" cycle. I have not tested to see if querying the SB Test node before smoke alarm test cycle sets node off and then immediately back on or not.

Madbomber83 Is this the zwave meter or another you mentioned ? http://www.amazon.com/gp/aw/d/B007C8UBU ... ot_redir=1 Have you used one ?

quick post to mention that tonight I swapped to a new PLM (sticker version 1420) but sadly experienced a re-occurrence of the ALL ON mass event few hours after PLM swap. details in this thread viewtopic.php?f=25&t=11367&p=117487#p117487

Posting followup After 5 months of having these alarms linked to the ISY I have very positive results to report. They have tripped twice times. All staying in sync perfectly. False alarms in kitchen from cooking: Steam has false tripped the kitchen unit twice to say fire from a massive over boiling pot which is of mild announce but the silence button works great and I am not talking about just a little steam here. Yesterday we receive a voice alert (no siren tone) through all of the units stating "malfunction in kitchen unit", first time we have heard that and again we had a massive steam over boiling. The voice alert did sync across all of the units which was helpful since it reported "Kitchen Malfunction" however the ISY did not alert has me suspect the smoke bridge was not triggered. Retested the kitchen unit with blowing smoke into it and all units including the ISY alerted as expected. Interesting that 2 steam / pot over boil events tripped fire and the 3rd triggered "malfunction". Adding units later: Tonight I added two more units to the chain. Was very easy. Followed the directions in the package stating hold down test button on new unit while closing batt drawer till it beeps, then pushed test button on one of the old units until the new one beeped and went into room setup mode. Then immediately added the 2nd new unit to the 1st new unit in same manner. Tested by blowing smoke into the 2nd new unit. Just as before the power light flickers before alarm starts but all units alerted and ISY alerted too. Granted it would be ideal if the smoke bridge "knew" which alarm was triggered as doing custom alerts or programs would be really nice however I really like having our smoke and co alarms connected to the ISY. Thanks to the UDI Gang for Supporting the Smoke bridge ! J

Thx Michel and Lee! That fixed it. Interesting since before the remove, factory reset, re-add (via linking vs direct address) the nodes were on the ISY and the LED on the bridge would change status based on alarm condition but ISY did not see traffic. It is working now. For benefit of others here is what looks to have worked started with 2 smoke only and 2 smoke + CO alarms (all battery) 1. linked all four alarms to one another following directions in boxes that have you daisy chaining the alarms. Its clear that when you link 3rd and 4th alarm that they all group up into one group. 2. factory reset smoke bridge 3. linked smoke bridge to last (4th) alarm, per bridge directions: plugged in bridge and clicked set button, then pushed test button on 4th alarm. LED on bridge confirmed and then units continued through test cycle 4. linked smoke bridge to ISY via start linking on ISY, then press of SET button on smoke bridge, choose remove existing links 5. tested with actual smoke a. tested smoke at 4th alarm; all alarms sound and bridge changed to red, ISY changed smoke to yes b. tested smoke at 1st alarm; all alarms sound and bridge changed to red, ISY changed smoke to yes All good news here; smoke node changes ON and back OFF when alarm stops few other notes i. watching the power LEDs on the smoke alarms you can see when they are communicating with each other via onelink, the power light blinks fast when they are 'talking, linking etc' ii. the alarm where smoke was applied would have its power light start blinking fast for 2-3 seconds BEFORE sounding the siren, all four of the alarms would then sound at nearly same time with the smoke bridge in sync too. iii. I believe I saw insteon traffic from the smoke bridge when the power leds started flashing before the sirens started and then more insteon traffic from smoke bridge when the sirens started Communications to TEST node. It does look that the smoke bridge communicates when the TEST buttons are pressed too. 1. pressing test button on any of the four smoke detector units starts test. a. They all blink b. smoke bridge changes from green to blinking red c. ISY event viewer sees traffic, ISY changes TEST node to ON d. all four units start sounding e. ISY event viewer sees more traffic f. units complete test sounds g. smoke bridge changes from blinking red back to green h. NO traffic in event viewer from smoke bridge <<<<--- PROBLEM ??? i. ISY Test node does not change to OFF I tried the above scenario 4x with same result. But noted that 2nd try the TEST node in ISY was still showing as ON. Can someone check the event viewer below to confirm that the BRIDGE is not sending TEST node to OFF after test ? Here is the event viewer log from doing one test cycle. Thu 05/23/2013 11:03:48 AM : [iNST-SRX ] 02 50 23.4E.88 00.00.03 CB 11 00 LTONRR (00) Thu 05/23/2013 11:03:48 AM : [std-Group ] 23.4E.88-->Group=3, Max Hops=3, Hops Left=2 Thu 05/23/2013 11:03:48 AM : [ 23 4E 88 3] DON 0 Thu 05/23/2013 11:03:48 AM : [iNST-SRX ] 02 50 23.4E.88 11.00.03 CB 06 00 (00) Thu 05/23/2013 11:03:48 AM : [std-Group ] 23.4E.88-->11.00.03, Max Hops=3, Hops Left=2 Thu 05/23/2013 11:03:48 AM : [iNST-INFO ] Previous message ignored. Thu 05/23/2013 11:03:59 AM : [iNST-SRX ] 02 50 23.4E.88 00.00.03 CB 11 00 LTONRR (00) Thu 05/23/2013 11:03:59 AM : [std-Group ] 23.4E.88-->Group=3, Max Hops=3, Hops Left=2 Thu 05/23/2013 11:03:59 AM : [ 23 4E 88 3] DON 0 Thu 05/23/2013 11:03:59 AM : [iNST-SRX ] 02 50 23.4E.88 11.00.03 CB 06 00 (00) Thu 05/23/2013 11:03:59 AM : [std-Group ] 23.4E.88-->11.00.03, Max Hops=3, Hops Left=2 Thu 05/23/2013 11:03:59 AM : [iNST-INFO ] Previous message ignored. smoke bridge shows as v.43 in ISY and sticker on unit reads R3.0 0513 (sticker is clearly on top of old version sticker)