StangManD

I setup the HA VM a long time ago when the tutorial was posted with the instructions and it's been up and running solid on top of my Eisy since. As I realize it's completely redundant for the most part, there were things about it I liked and had integrated like Home Kit and some other things but now it seems after the 6.0.0 upgrade, it's just gone. I've opened a ticket, but I guess maybe I'm just late to the party here... is this to be expected on an upgrade? I know it was a "major OS version upgrade" but I didn't expect it to be wiped out. If it has been, I want to make sure any remnants of it that may be left are cleaned up before reinstalling. Seems like if I have to do that, I'd likely need to set back up from scratch, not sure one of my HA backups would even work. Have others run into this and is this to be expected?

This worked for me... I've been messing around with trying to get reconnected to the admin LAN console since updating and this was it for me :). Thank you a ton! Specifically this line: https://<local ip here> :8443/admin.jnlp

Okay, so the fix for me was as follows and please keep in mind I only have 1 Z-Wave device, so that may have something to do with the directions. 1) Remove/Exclude my one Z-Wave device. 2) Click the Migrate button under the Configuration tab. 3) Add the Z-Wave device back (it added correctly with ZY node names. 4) Correct my programs with the new device node names.

Still going through support, they rock. As of now, it was mentioned that I am seeing the original Z-Wave menu and I was asked if my Z-Wave nodes begin with "ZW" or "ZY". Mine begin with "ZW", which evidently "matches" the old original menu, so I'll let you know what that means as to what they are having me do to address/fix when I hear back.

Thank you... yeah my Z-Wave and Zigbee devices that run off of this device are simply water alarms and an alarm siren for now. Nothing crazy and only 5 total devices anyway. If I have to remove them all and re add them it wouldn't be the end of the world, just want to make sure I do whatever it takes right. I'll keep you posted. Thanks again

Thank you... and I agree, I usually do my "rounds" and go back up PG3, IoX, and HomeAssistant (I know that's not their deal but it's part of my backup process). Adding one more wouldn't be the end of the world but agree, would be nice to catch it all in one place somehow. I do realize this all lives on a VM environment ultimately anyway so some of that is inherent I suppose. I've created a support ticket and will report back what their suggestion and resolution is. Thanks again for your responses.

@xlurkr - Yes, I did have a Zooz 700 USB stick prior to the ZMatter dongle however I already went through that process back when I replaced it. So are you saying you clicked the migrate button in the Configuration tab, then those showed up? I'm afraid that I'm going to break what works just fine by doing that though... what was your experience by clicking the migrate button, did it take you through other setup steps or anything? @jkmcfadden - Yes, I do not have those options in my menu. This is what mine looks like:

I'm following the instructions line by line before updating my system to OS14.3 and IoX 6 for the new eisy-ui experience however in the instructions, it's telling me to go to the Z-Wave menu and select Backup when in the admin console. I do not have a "Backup" menu option. I'm currently up to date on OS 14.1 release P6 and IoX 5.9.1_18. I am running the Universal Devices ZMatter USB Dongle as well and control both Zigbee devices and Z-Wave devices from it. Can someone help me understand if this is something I need to worry about or not prior to clicking the "update packages" button? Last week I ran the update packages button successfully a couple times to make sure I was fully up to date before they did the final big release. I have also backed everything else up at this point (I do this regularly) but have never gone into Z-Wave to even look for a backup option... however there isn't one to be found. Please advise. Thank you in advance!

I get it and it’s no fun! It ultimately needed multiple rounds of updates over and over. Mike is wonderful for support. If you create a support ticket he will walk you through it all but basically mine was in a state of partially updated. Once it fully updated it worked fine and was good to go. After my full rebuild and restore and multiple rounds of updating, it finally came back to life as of my latest backup. I’ve now learned to back up every single time I make a change. I got lucky because even though I had old backups, they were probably about 90% there from what I was running the day of the crash. good luck with it and I highly recommend creating a support ticket.

Edit - nevermind... it was a firewall rule across VLANs. Thank you for taking the time to respond... I accidentally had my response (from Eisy to weather station) disabled. It's good to go now. Thank you!

Also noticing if I change the "Station Name" field and save, it saves successfully but there is a notice that pops up that says, "Failed to start Console monitoring service." It's just a blue banner notice type of message, not an error from what I can tell. Also when I review the log during a "restart" of the node server, it doesn't have any obvious errors at all in it, seems like it starts just fine.

So I have Ambient Weather already up and running however wanted to keep things local and not have to call out to the web for the data that's inside of my network. Anyway, that being said, I've followed the directions to a T from what I can tell however it's just simply sitting there with 0 nodes. The devices can communicate on the network and I have verified the config settings over and over thinking it has to be something simple/stupid. Well no dice, I'm just sitting here with no idea what to do next. I have a WS-5000 weather station and updated it to the latest firmware today which gives me the ability to define the custom server option (same as the WS-2000). I have configured it exactly as it should, IP of the Eisy, (default) port defined in the configuration of Ambient Console, and have it set to send the same ambient weather type of data, assuming that's what it needs (I've tried both settings and neither work). I have set the path to /pg3x? as the instructions say from the store, and I have also tried the path /api/ambientweather/metrics? as the github instructions say. Neither are working. Need some help here please. Thanks in advance

So it must have been a corrupt eMMC for some reason. Not sure how that happened, but re flashing the drive with a fresh image did the trick. I restored my IoX backup, restored my PG3 backup and everything in that regard seems to be working Now I have a new problem. I don't see ANY of my Insteon devices. I see all of my programs and they all have errors that there are unknown nodes/devices attached so they won't work. Under tools - Diagnostics - PLM Status/Info = it is there and communicating just fine. So during the IoX restore process, it said: "This action will replace all settings on ISY, reboot ISY, and close your browser. If the restored settings do not match the settings in your INSTEON Devices, please run "File->Restore Devices" in your next browser session." That's all good, so I'm at the point where none of the devices are showing up at all under the Main tab. My next move is to follow the directions but I hesitate because of the message I get when I select that option. It says: "This action will reprogram all of your INSTEON Devices using the settings stored in ISY. This will take 10 seconds to 2 minutes per device depending on the complexity of your network. If you have battery powered devices, make sure they are in Programming Mode BEFORE you proceed." So my issue is, I am told that as long as I don't factory reset the PLM (which I didn't - not even sure how to do that on the USB PLM if I wanted to), the links will all be there and match my system, etc. and will be fine. Well I'm okay with "Restoring" the links by reading the PLM because it's device table and links should all still be connected to all of my devices. What I fear is the warning message is going to reprogram all of my Insteon devices with settings from the ISY. Presumably right now, there are NO settings for the devices in ISY because it's not seeing any of them. Am I wrong to fear this message that it's basically going to overwrite what's in my PLM even though the PLM has the info ISY needs? I feel like I'm literally aiming at my foot with a loaded gun with that message. Please advise, I've asked support but have been waiting most the day for a response at this point and I'd like to get the show back on the road with my automation. Thank you in advance!

Support says either send it in for repair to them or I can try re-flashing a fresh image onto the mSATA drive in the unit. Then I would just update via admin console and then restore my IoX backup. Seeing how I have the new eISY on (pre)order, I don't think timing would be good for me to send it in and I'm not afraid to try to reflash the drive from an iso. I'll give it a whirl when my mSATA adapter shows up tomorrow and report back in case anyone is following or runs into something similar.

The power supply is outputting 12.34v and there's no reason to believe the current (1.5A) isn't there... the light ON the power supply itself is green and the unit doesn't seem to have any sort of "dimming lights" signs or anything else with a shortage of current. I don't think it's power either.

Yep, I kind of figured, that one is well documented... the light combo tells them exactly what needs to be done. Not sure what happened to mine but this one is unfortunately different... I'm going to test the power brick for kicks before I run up and buy some other one just to rule that out... not sure.

Ah... yes, when it becomes corrupt (certain light arrangement) you have to plug the little ROM flash board they send into the pin header if I remember correctly and it re-flashes it. Yes, that actually happened to me a few years back but that was a specific light combo after some beeping during boot... where the BIOS becomes corrupt I believe. Is that what you recall or something different? Mine is not doing that scenario this time unfortunately (as I have that little flash board they sent on-hand). That issue and solution is outlined in the Wiki. This is a whole different situation that I am not finding any documentation on.

Hope not as well... is there even a SSD card in the Polisy Pro? I know there isn't one accessible from the exterior of the unit. Do you mean there's a slot and card on the inside of the unit?

We have an electronics store near by, I can swing over there and find something of the same spec and hopefully same connector to try... good suggestion, thank you. I have not yet tested the power supply or tried a different one.

Another update... what I see (status lights on the box) when I power it on is accurate. It's silent and I only see the one light change noted previously. What I DO see suggests that something else is likely going on behind the scenes and perhaps I might be lucky enough to get bailed out of this without a factory reset? With pings, I can see this on my network when I plug power into the unit: 35-40 seconds after power is applied, it pulls an IP from DHCP and is on the network with an IP (pingable) It begins querying DNS for pkg.isy.io every ~30 seconds repeatedly and constantly All I can do is ping it... SSH is disallowed on the unit as it refuses the connection and I cleared my Java cache, reinstalled the IoX launcher fresh and tried to manually connect following the Wiki instructions with no luck. Thanks, I think this is about all of the troubleshooting / investigation I can do at this time without further ideas or direction. My gut is to factory reset it and give the IoX backup a shot... but I'll wait for a response in the meantime if anyone can help. Thank you very much in advance!

Additionally, I followed your instructions and cleared Java cache and re-installed a new launcher and tried to access via the correct IP/port/address with no luck.

Thanks DennisC, really appreciate it. I ended up creating a support ticket after documenting the boot cycle (lights/beeps) and I think I'm in real trouble here. I don't think it's actually booting. I have no idea what happened to it to get here. Whole rack is on a UPS, all equipment has been "power happy" for 3.5+ years with no power bumps or anything. So after a good solid power cycle and staring at it for 30min while I watch lights/beeps to document for this ticket... I don't think it's booting. This is what happens when I power it up (plug the power cable in): All 3 lights come on for about 1-2 seconds Just the left most light remains on - and that's it. No beeps at all, no more blinking, no nothing. Just that sequence above when first applying power to the unit and that's it. Wondering if a factory reset is in order? As much as that makes me cringe, I'm HOPING my IoX backup helps me out when I get it back up and running. Do you think that's my only chance at this point? Seems that this thing has somehow become corrupt... again, no good reason why but sometimes these things happen.

For starters, this unit has been "in production" running my home automation for 5 or more years with no changes to networking or anything that would cause any connectivity issues. I can ping the device IP just fine but I cannot get to it any other way suddenly. This all started by the unit erroring out from the UD app and my Echos with voice commands saying it was offline or unavailable. So I was able to ping the IP, get into the local portal just fine via the IoX launcher, backed the unit up for good measure (IoX Backup), then pressed the button on the face twice to do a safe reboot. Once it came back up, everything reconnected and was fine for about 5 min. Then the app started complaining again and this time, I could not get into the interface from the IoX launcher. This has ALWAYS worked. So I rebooted it again, no help. I then waited a good 10min and pulled the power cord and plugged it back in... same thing. On the face, when it's rebooting it has left light solid, right two blink together for a while then go out and it's just the left light. When it's done booting, the left light is solid, no other lights are on or blinking. Still after a power cycle this is where I am. I've had this thing up and running for years with no issues, don't know what happened or what I need to do here to get it working again. Also, I can still ping the IP of the box, so that is fine but that isn't helping much as I can't get to it via the IoX launcher or app. I'm fairly certain it's just not working at this point as I can usually tell when it's poling the Insteon devices (lights dim ever so slightly when they are communicating... and it's not doing this anymore when the box boots up which tells me it's probably not actually booting up correctly or completely) Please help! Thank you!

Hi there, I currently have a UPS running my network rack which includes many devices that can use a network ups to trigger graceful shutdown events. Currently I have my NAS connected directly to the UPS and have it configured to be used as a network UPS server... there are many other ways to do this of course, NUT, etc. I would like to know how to get the Polisy to trigger a graceful safe shutdown in the event of a power outage and low UPS battery, I have a couple NAS devices doing this and am in process of getting my firewall configured as well. Any help here would be greatly appreciated. Thank you

Great, thank you both so much, really appreciate it! Strangely enough, it all seems to be working perfectly fine now... I've been walking around my house barking orders to "Alexa" to turn lights on and off and it's super snappy again and no issues. Again, it was ONLY the Insteon devices that were having issues, the Hue controlled devices were triggering just fine through Polisy. So I really can't explain it, I don't know that the USB Stick Insteon device is going bad... not sure if that's a thing, I have backups for this hardware if I need to change to a PLM or other USB stick if need be, but seems like after picking up the Polisy physically, looking at it and setting it back down, it has somehow resolved. Very odd. Thanks again.