Bill Morrow

It looks like my ISY994i is dead. After I update the firmware I can get into the Admin Console once or twice, then I get locked out. I can't Telnet to it and my MobilLinc won't communicate with it. Although I did manage to turn on one light right after the firmware update. I'm waiting for a replacement and wondering what my Next Steps are. I assume I upgrade the firmware on the new unit, load my backup and update the MAC ID in the Portal. Do I have to update the PLM? I'd like to resurrect the old ISY eventually, although I have no idea what illness it has. The LED sequence is apparently OK, but it's not talking.

Yes, Michael had sent me this link, but the launcher would not load. The standard launcher would load, but the Admin Console would not, as Brian was alluding to I gather. It just crashed the ISY. I ended up using the Web Console to reload the latest firmware manually. I have not used the Web Console previously, but the load went well. The restore was also painless. I just hope my 4.9 backup is OK, as that is the second SD card in a year. I also replaced the power supply, based on the LED sequence when I tried a factory reset the first time. The factory reset worked after I replaced the SD. I could not Telnet to the ISY until after the factory reset, although I suspect it was the power cycle that solved my problem, as the Admin Console was crashing the ISY. Anyway, thanks for the help, hopefully it saves someone else the aggravation.

Yeah, the first time I tried to factory reset it, it came back with the power only light for a while, but this could have been my impatience. Replacing the power supply did seem to alter the LED sequence slightly, but I kept getting the error light and the memory light never blinked at the end of the sequence. I took out the SD card to inspect it, but it did not seem to have any formatting or corruption issues. However, the guide indicates that an error light without a memory light is an SD card issue. I formatted a fresh SD card and replaced the card in my ISY. It booted up with the power light and the TX light blinked once. The good news is that it shows up in my router with the original IP again. The bad news is that I can't launch the Admin Console, it just seems to hang. The weird news is that it says the firmware is now 5.3. I can launch the DashBoard, but I'm a little hesitant to a restore from here. If I open the portal, it says that my ISY is still offline. It makes me wonder if my firmware is corrupt, since it crashed while updating the firmware. At least it does not seem to be dead. Any thoughts on Next Steps?

Thanks, no I can't seem to start a new ticket so, I sent an email. I replaced my SD card a few months ago, as the ISY was getting flakey. There are several blue lights and a red blinking light on power-up.

I tried to update my firmware from 4.9 to 5.3, but it failed during reboot. Now I have a red flashing led on powerup. The portal says my unit is offline. I tried to open a ticket, but I can't bring up my existing tickets either. Help.

OK, I'm talking to myself at this point, but maybe it will help someone else, although I found illumination from searching the forums. Apparently simple is better, who knew. ? I went back and corrected my original program after reading some posts. This seems to work, but I had to do a walkabout and record it, as there's never a dog walker when you need one. My two major takeaways from this experience: The ISY programs run asynchronously (makes sense), so don't count on the statements after your Wait statement being executed, as your program may get retriggered before your post Wait statements ever get executed Don't mess with the criteria in your If statement in the Then/Else, as the If statement is event driven (always being checked), so your program will stop executing, even if you change the criteria to the same value Someone else has probably run into your problem, so do some creative Googling These are the two programs that seem to solve my problem. The first is my original program with the Wait removed. The second is my Timer program that disables my original program until the Wait completes and then re-enables my original program. The Timer program has no If statement. I probably could have disabled the Timer, as it only gets called by the parent program. My original Motion Sensor program My Timer program that disables Mama for a period of time to eliminate multiple triggers I likely missed something, so feel free to suggest improvements.

OK, the above code doesn't work because the Resource program is getting triggered again before the wait completes. Makes sense when I think about it, the Wait would have to be asynchronous. This doesn't work either, the code after the Wait does not execute, the program does not get re-enabled and the variable does not get reset. If I run the Then a second time the code after the Wait does execute, the program does get re-enabled and the variable does get reset. ?

OK, things are working a bit too well now. The RPi is very chatty now, I'm getting Garage, Garage, Garage multiple times. I tried inserting a Wait after the resource call, but this does nothing. I assume the events are still getting queued. I thought separating the status from the resource all might solve my problem, but I don't think so. The first wait is to stop the RPi from stuttering; not sure what causes this. The first program is the original, the next three are my Status program, the Status Update program and the Resource call program. I'm trying to make it wait before calling the resource again. I think I really need a countdown timer with a second condition of the Resource call program. The old stuff The new stuff Any thoughts? The Resource program with just the Wait 5 did not seem to work, I got fewer announcements, but they were not 5 seconds apart. The original program with the Wait 5 did nothing to reduce the multiple announcements. Five seconds is just a placeholder BTW, I may change it dependent upon the complaint level.

I had an on/off variable in all of my announcement programs, so I could disable them all at once. It seems to be this variable that was causing the delays. The other issue I had was that I had to put a delay before the resource call or the resource call would get stuck in an endless loop. I did not have this issue when I first wrote the programs, it showed up later. Teken suggested adding the delay to stop the stutter. Two seconds seemed to be the minimum required.

I'm doing something similar; I have a RPi with a HiFiBerry amp that plays various wav files stored on the RPi. If I test the Network Resource I get an instant response, so the delay must be in my code that launches the Network Resource. The weird thing is that the delay is not consistent, the odd time the RPi speaks before Alexa, but mostly it's about a minute behind. My Network Resource looks like this:

Pardon me if this is not in the right forum. I have been using my UDI to make motion triggered voice announcements through a Network Resource to my Raspberry Pi. This works, but the delay is so bad that the motion detection occurs long before the voice announcements. I recently spent the time to get this working on my Alexa using the portal and the delay is much less. I can actually see the perpetrators on the cameras when Alexa is speaking. I still have the Raspberry Pi connected, so I am still getting both announcements. The Raspberry Pi is typically delayed by 30 seconds to a minute or more. Today the Raspberry Pi actually spoke right after Alexa, but that was a one off. I'm thinking there is either a delay in the UDI sending the network command or there is some kind of network polling delay on the Raspberry Pi? Does anyone have any idea what is causing this delay? TIA

Any updates on this? I am currently using a Raspberry Pi for my Voice Announcements, but the delay is very frustrating. I'm also likely going to move on from ISY ASP to SmartThings.

Yeah, I'm not sure this worked the first time I powered up the EZIO PLM. I could not link the device until I plugged it in the second time. I also had to select [07 04] from the device type drop-down to get it to link of course. Thanks

Yay, I'm hearing voices again. I thought I could hear the announcements if I wandered around near the front door with the front door open, but apparently not. I also restarted the interface, so who knows. I sent the boss out to do a walk about and they are working again. I think the one motion sensor might have wiring issues, since we had the trim capped with aluminum. But I'm installing all new IP cameras, so what's one more cable. ? .

Thanks Brian, I did not see it when I was playing with the context menu, but I did not spend a lot of time before I killed the dead EZIO PLM. I just looked up the codes I wanted from the PGM files in the ISY backup. There are not that many motion programs to update. Although I don't think I have sound yet. I am seeing most of the EZIO inputs in the Event Viewer, so I guess something else is broken.

OK, so I got the new device to link, but I couldn't find a way to replace the existing PLM address. So it wiped out the controls in all of my motion programs. I have a backup of the ISY before I replaced the EZIO PLM, so if there is a way to substitute the new PLM that would be great.

I forgot that I had an old 2413S that I had done the capacitor fix on. So I hooked it up and added the new device to my ISY, but it says that it could not identify the Insteon device type? The 2413S seems to react normally to a reset. Any bright ideas?

My motion voice announcements recently stopped working and I've traced it back to my EZIO8SA PLM. My ISY won't talk to it and when I did a factory reset it didn't blink or buzz. Nada. I remember having to plug my laptop into the original PLM to get the EZIO8SA up and running with the ISY. But it's been so long since I did this, that I don't remember what software I ran or what I did. I tried to download the manual, but my Malware software is complaining about a Trojan on the Smartenit site. I also posted my original issues here, but the post seems to have scrolled into the ether? I'm hoping I can just plug the replacement PLM in, but as I recall, it's not that simple? Thanks

Thanks.

It seems I need the IOS version for this to work. This would explain why my App looks nothing like the screen shots on the website.

I want to be able to view my Insteon camera in MobiLinc, is this possible with ISY?

I was looking at the Optex 'Wireless' motion sensors, trying to figure out what receiver they used. Then I noticed that it says 'wireless ready'. LOL, why would I pay twice the price of their wired sensors for a 'wireless ready' sensor? I can just stick a battery pack and an Insteon door sensor in an IP66 enclosure and use my existing Optex wired sensors. I think I've found my next science experiment. I'd actually like to use a leak sensor, except that they are not momentary contact.

Yeah, it gets relatively cold here in the winter, we're protected by the lakes somewhat, that and global warming. The summers are getting warmer, but again the lakes help mitigate that too. I can't see myself trudging through the snow in January to replace batteries though. ❄️ I think the one sensor is failing, so it might be time to replace it, but I'll check for spider webs first.

Thanks, I was hoping to get something native, but it's more important to me that it works reliably. So Wireless with some external interface would not be horrible.

I'm actually happy with what I have, but I was hoping there was a decent wireless option by now. My current sensors have lasted a long time and do not have issues with false alarms, i.e. they are not subject to sun/shade issues or wind, as long as I keep the bushes trimmed. Although I'm sure the lenses may have some sun damage by now.