Ethrex

Is it possible the ISY hardware could support the Thread protocol? If so, is there any plan for ISY to support Thread?

I was able to plug in my dyndns.org host in the MobiLinc app and confirm that it works while both at home and remotely as well. This solved everything for me - you saved me $299, thanks MWareman!

Ah thank you. I was unaware MobiLinc Connect had all of these features other than just allowing me to connect the Android phone app. I am browsing mobilinc.com now and will research. However now it looks like the real price of MobiLinc Connect is $299, not the $199 advertised in the MobiLinc Pro phone app. $299 is a little steep and I will probably not get wife-sign-off and have to look for alternatives for a phone app, or just go without.

Okay, wow, I must have missed that memo. So you are telling me that I cannot use both IFTTT and a remote mobile phone connection to my ISY? I hope I misread that. Well thank you so much for telling me this before I shelled out $199 for a lifetime subscription of mobilinc the ISY won't even let me use without disabling IFTTT. Please confirm...

In mid-October I got a new Android phone. I wanted to try MobiLinc on it so I installed the app and and bought the "Portal Integration - MobiLinc Connect" module. Installing the module required rebooting the ISY, which it did. The phone app has been working fine. However right around that time, IFTTT stopped working and I haven't investigated why until just now. Right now if I go to https://my.isy.io the state of my ISY says: "Offline since Tuesday October, 23rd, 10:07:19 PM" Attempting to perform nearly any action on the ISY gives a modal with the error "ISY is not online". So I go to my Administrative Console and in Configuration > Portals it shows it is connected/online: Portal Integration - Mo... / Online / Registered [Refresh] Refreshing still shows online. Below I pasted all the statuses of my installed modules. My ISY thinks its talking to https://my.isy.io but the web portal thinks its not talking to it. I tried removing the ISY from the website and adding it again but that doesn't update the status (nor does the refresh button). There was a firmware update available so I let it automatically update hoping that might solve it, but that didn't solve it either. Anybody know how to fix this? VERSIONS Firmware version: Insteon_UD994_OADR v.4.7.3 (2018-07-09-16:50:21) UI: Insteon_UD995 v.4.6.2 (2017-06-21-13:52:47) MODULES: Portal Integration - MobiLinc Connect Installed on: October 24, 2018 Active ISY Portal Expires: February 17, 2020 Installed on: February 17, 2018 Active Open Auto Demand/Response Module Installed on: November 28, 2017 Active Z-Wave Module Installed on: November 28, 2017 Active

Okay through trial and error I have narrowed down the issue quite a bit. On each KPL, the 'C button' is assigned to a "Deck Lights" scene. The "Evening Mood" scene also turns off the LED of those C buttons. As soon as I remove the C buttons from the "Evening Mood" lights scene, the 'B button' works as expected - the buttons blink twice then the LED turns off. If I add the C buttons back to the "Evening Mood" scene, the 'B button' LED immediately illuminates and doesn't turn off. So is this just a limitation of KPL? A bug? A bad expectation? Thanks

01_ButtonToggleMode: This shows that each KPL has a "Non-Toggle (On)" setting. 02_LEDBrightness: This shows the LED brightness levels of the KPLs, in the case the question came up. 03_SceneWithKtnAsController: This shows the "Evening Mood" scene my "B button" is activating, and specifically the bottom of it where the other KPL is shown to have its LED be turned off. 04_SceneWithEntryAsController: Same as previous except the other KPL. 05_MainKPLSwitchIsResponder: This shows the KPL switch itself is set up as a responder to the "B button". My working 'A button' is setup the exact same way, only assigned to the "TV Mood" scene which has far fewer responders than the "Evening Mood" scene. To be very clear, I want to re-explain the symptoms I am seeing. I have two KPLs, Ktn and Etry, both set to "Non-Toggle (On)" and assigned to scene "Evening Mood". If I press Ktn:B Ktn:B is illuminated immediately, and never blinks. (Bad: should double-blink and LED turns off) The entire "Evening Mood" scene is activated correctly. Etry:B (which is a responder to the scene) is also correctly affected (LED turned off) If I press Etry:B Etry:B is illuminated immediately, and never blinks. (Bad: should double-blink and LED turns off) The entire "Evening Mood" scene is activated correctly (except for the next point): Ktn:B (which is a responder the scene) is illuminated immediately and does not turn off (Bad: the picture even shows the scene should disable the LED) When taking these screenshots, something occurred to me. There is a distinct difference between the this setup and "A button" setup: The "TV Mood" only controls devices in a separate room but the "Evening Mood" scene also controls the main switches of each KPL. The Etry KPL is hard wired to lights which are turned off by the "Evening Mood" scene. If its not some obvious misconfiguration on my part, I wonder if the problem is related to the fact that the buttons are controlling the KPLs they belong to? Because this is affecting two KPLs, I don't thing this is a hardware problem. Any help appreciated! Thanks

Hi, I have two Keypad Lincs in opposite ends of a room, both in 6-button mode. Over a year ago I made the 'A' buttons correspond to an "evening" mode. In the ISY I created a scene which includes all the devices I want included, then I made the two 'A' buttons controllers of the scene. Each controller also turns off the LED of the other button 'A'. The "Button Toggle Mode" of each Keypad Linc is set to "Non-Toggle [On]" for the 'A' buttons. When I click each button 'A', the scene is activated, and the button I clicked has it's corresponding LED blink on twice, and then turns off. This setup has worked great for over a year. Fast forward over a year and now I want to do something nearly identical to the 'B' buttons of the same two Keypad Lincs. It is identical setup, just a different scene. The difference now, though is that the button I press has its LED immediately turn on (doesn't blink) and it persists on. It doesn't give me the same blinking effect. While trying to debug, I switch it over to "Non-Toggle [Off]" and the light persists on in that mode too (no blinking), except now the scene turns off of course. Next i try it on just "Toggle" mode and I get the effect you would think -- when turning on, the scene is turned on and the LED is turned on. When turning off, the scene is turned off and the LED turns off. So this is my question. How do I get that "LED blinks twice then turns off" effect that I get with the other button 'A's on the two Keypad Lincs when in "Non-Toggle [On]" mode? As far as I can tell, the settings are identical in my ISY. Thanks