MrBill

That's true, but part of the problem above was that HA itself wasn't running on a machine with backup power.

@andrew77I think you need to continue working with support on this. Hopefully @Michel Kohanim has your ticket.

What issue are you having with telnet?

I'm pretty sure that the first error dialog you posted above means that there's a problem with your memory card. You're trying to upload the zip file and it's being written to the card wrong. Either the card isn't inserted full, or it needs formatting, or it's a bad card.

they are repeaters themselves. you just need more z-wave devices that repeat spaced around the place.

Ok, did you format the new memory card after it was installed, or did you skip that step because the wiki say's it doesn't need to be formatted if it's new? Also what memory card is it... brand and size and does it have an A1 rating?

Try leaving one of them plugged in downstairs near the ISY. The zwave board in the ISY doesn't have a strong transmitter. Some users once reported putting the ISY in vertical orientation also helped with z-wave signal strength with a 500 board. You need to build a mesh network of repeaters with at least one close to the ISY.

Is your Mac set to not unzip files when you download them?

When you say "It starts" do you mean loading the firmware with "Help > Manually update ISY"?

good, now reload the firmware that your backup was created with, Help > Manually Upgrade ISY, then check Help > About and make sure the firmware and UI versions are the same. THEN reload your backup. If you have problems with any step above, stop and tell me what's happening before you continue.

No it's not, any Polisy can be upgraded to IoP. Do you know how to use SSH? you need to for this. Go here .

I'm confused, Both what?

Type it as http://IP.ADDR.FOR.ISY/desc then hit save. If you're on a mac are you using the ISY Launcher, or are you using admin.jnlp?

It sounds like you can't get the admin console running? Do you know how to use your router interface to manually find i'ts IP address? Is your computer windows or mac?

for ISY994 version 5.3.4 check this thread: In step 3 (download firmware), there are 2 links to choose from. The first is for ISY994's with a PLM, the second is for ISY994's without a PLM.

Did you factory reset your ISY994 by chance? I'm just making a guess... if you did there's probably some extra steps to get back to normal... reload the firmware the backup was created in, then restore backup. Other than that, you're really in "open a ticket with support" territory. User to user advice for this type of thing isn't good because catastrophic events don't happen routinely to other users.

I don't, I fought with that issue for years. Until I added the NUT add-on. The NUT server doesn't have to run on the same machine as the HA and the NUT integration, but it wouldn't make sense to have HA go down when the power was out.

@larryllix... looks like he's got that covered.

Home Assistant. I run the NUT (Network UPS Tools) which appears to have most cyber power units on it's hardware compatibility list. The UPS plugs into the Pi running HA, and various items show up as entities in HA. I'm not using Cyberpower but here's what I'm getting from my APC: Most of which I don't actually use... I also have HA updating a State Variable in ISY.... I haven't finished building it out yet, but the purpose to make sure lighting is where is should be after power restore. Insteon returns to it's previous state, but if we passed into another time period things may not be correct.

You need to WAIT 24 hours for the heartbeat... whatever you read about the set button sending all 3 signals is just plain wrong... Set does not send heartbeat.

But what batteries are you using?

@shunsader what type of batteries are you using? I've not had any luck getting heartbeat to transmit except on it's own. It sometimes triggers when the battery is installed but I think that might be firmware specific (but I've never studied it since I realized that as being a might be). The sensors are designed to be used with alkaline batteries. I've seen people say they are having heartbeat issues and I ask are you using lithium batteries instead of alkaline and they never answer, but we don't hear from them again. Put a fresh Alkaline battery in, and wait 25 hours and see what you get.

As previously mentioned... don't rely on text messages, us an alternative method. The email to text gateway at your cell provider gets nailed with spam that clogs the opening up for all users. It's not an ISY problem it's an email to text at your provider problem. two great alternatives posted above....

A better Heartbeat Program: This is a door sensor, but the same applies for any of the Insteon Battery Devices that generate heartbeats. The advantage here over what you've posted above is that you're only notified when the heartbeat is missed, your program is sending you a barrage of heartbeat notifications everyday. First I create 3 integer variables for the device: Missed Heartbeats, Battery Days, and Total transmissions. (Total Transmissions in fact isn't as useful as I thought it would be, but nonetheless it does help somewhat in deciding if the battery needs to be replaced or the sensor just needs a reboot (i.e. remove and re-install battery). hb.BarnOHD - [ID 0063][Parent 0072] If 'Door Switches / Barn OHD / Barn OHD-Heartbeat' is switched On Or 'Door Switches / Barn OHD / Barn OHD-Heartbeat' is switched Off Then Wait 25 hours $iDoor.BarnOHD.HBmissed += 1 $iDoor.BarnOHD.HBmissed Init To $iDoor.BarnOHD.HBmissed Wait 2 seconds Resource 'NotificationNS.DoorTrouble.BarnOHD' Run Program 'hb.BarnOHD' (Then Path) Else - No Actions - (To add one, press 'Action') Note: all the heartbeat programs are also run-then by a program that runs at startup, That program waits 10 minutes to start these... (my ISY struggles at startup due to the size of the insteon network and the query all that runs) What happens here, is that when the heartbeat is received we jump right into a 25 hour loop to wait for the next heartbeat. If the next heartbeat is received within that window the rest of the program never complete.... instead the wait starts over. If the next heartbeat is missed, the integer variable is incremented, and a notification is sent in this case via a Network Resource and Pushover. (that line could also be changed to "Notify") Finally the last line of the program starts the loop over again waiting for the next heartbeat. (If that line was skipped, the program would end and we would never be reminded.) It should be noted that some of the battery sensors are better about sending heartbeat than others. Some need only need 24 hour waits (like the hidden door sensor) while some even need 26 hour, you just need to fine tune that. It should also be noted that when heartbeats stop coming in the battery isn't actually dead yet, the sensor will still work for a number of days afterward. Bottom line, failed heartbeat isn't an emergency, check the sensor at your convenience of the next day or so. Sometimes the next heartbeat will just arrive, and sometimes you just need to pop the battery out and back in. High battery day counts, and high transmission counts tell you when it's time to actually replace the battery. For total transmission counts: BarnOHD - [ID 0042][Parent 0033] If 'Door Switches / Barn OHD' is switched On Or 'Door Switches / Barn OHD' is switched Off Or 'Door Switches / Barn OHD / Barn OHD-Heartbeat' is switched On Or 'Door Switches / Barn OHD / Barn OHD-Heartbeat' is switched Off Then $iDoor.BarnOHD.TransCount += 1 $iDoor.BarnOHD.TransCount Init To $iDoor.BarnOHD.TransCount Else - No Actions - (To add one, press 'Action') For the battery days counts: AddAge - [ID 003D][Parent 0034] If Time is 12:12:12AM Then $iDoor.BarnOHD.BatteryDays += 1 $iDoor.BarnOHD.BatteryDays Init To $iDoor.BarnOHD.BatteryDays [Redacted about 30 other battery day variables that follow] Else - No Actions - (To add one, press 'Action') Then there's also a quick way to reset the 3 counters when a battery gets changed. I run this program manually from a Home Assistant dashboard button, but it could be also run manually from the admin console. The program actually does send 4 notifications so that I have the final counts in case I reset the wrong one (which has happened), I also used to keep the totals in a spreadsheet but the bottom line is I've got the feel of the system now and don't record them anymore. BarnOHD.reset - [ID 01A1][Parent 01B5] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Resource 'NotificationNS.DoorTrouble._resetCountersBegin' Wait 1 second Resource 'NotificationNS.DoorTrouble.BarnOHD' Wait 2 seconds $iDoor.BarnOHD.HBmissed = 0 $iDoor.BarnOHD.HBmissed Init To $iDoor.BarnOHD.HBmissed $iDoor.BarnOHD.BatteryDays = 1 $iDoor.BarnOHD.BatteryDays Init To $iDoor.BarnOHD.BatteryDays $iDoor.BarnOHD.TransCount = 1 $iDoor.BarnOHD.TransCount Init To $iDoor.BarnOHD.TransCount Wait 2 seconds Resource 'NotificationNS.DoorTrouble.BarnOHD' Wait 1 second Resource 'NotificationNS.DoorTrouble._resetCountersComplete' Run Program 'hb.BarnOHD' (Then Path) Else Resource 'NotificationNS.DoorTrouble.BarnOHD'

Ahhh I didn't catch the clear button comment. Although I do have one package of those, I could use for special cases since SH isn't laser printing the gold gilded custom buttons anymore ("Gold gilded" is the price they charged, not an actual product feature.)