inovermyhead

@geddy, will do🙂

@Geddy Thanks for the suggestion: I checked all of my plugins and the log level for a couple were set at "error" or "critical" level . I've now got them all at "warning". I can rule out a router problem: two weeks ago my custom router (Untangle running on a Supermicro 1U) failed (I think an HDD problem but haven't had a chance to do a real diagnosis yet) so I switched to a backup - an old Linksys WRT54G - and the offline/online notifications have continued.

@bwdavis7, yes, I've been getting the offline/online notifications well before 2/1. I don't recall exactly when I started noticing these, since I was just deleting them. Part of the impetus for "fixing" the issue and posting on the forum is that I will be going on a long international trip soon and wanted to delete unnecessary push notifications that will incur roaming data charges. Did you recently add or update your eisy? While I've had my eisy for nearly a year, it was only in December that I finally sat down and migrated everything from my trusty but old ISY994. Extending from @Geddy's thinking could it be a plugin that's causing this? I have installed: ISYLink, Weatherflow, Wireless Tags, Holidays, Webcontrol832, AVremote, Roku Media Player, Push, Sun, ISY Portal, Nanoleaf, Presence, Backup, Ecobee, TimeData, UnifPresence and Kasa (some outdated from ISY994/PG2)

@bwdavis7, no, no match between your offline/online times and mine. @Geddy, yes same versions of UDx, isy and PG3x. I haven't tried (but will) a hardpower off restart on my easy. However, the fact that my cycle/notification times don't match those of bwdavis7 AND that the offline/online notifications have been going on for me for some time (I just finally got tired enough of this to post in the forum) would suggest that the problem is local to individual eisys, not something at UD's end, correct?

@flsenior - same here: During the eisy "offline" periods I can and have other internet services going, like Amazon Music. So the problem is not at the ISP end... Sort of reassuring to hear that others are observing the same issue; suggesting that it's not something unique to my setup. Thanks.

I’m getting frequent UD Portal notifications that my eisy is offline, then a few minutes later that it’s back online. The notifications seem to come in random spurts, sometimes many (6-10) in a day, sometimes none. And the offline to back online interval is always 8 or 9 minutes. The eisy is on a wired Ethernet connection, not Wi-Fi. So far I haven’t been able to discern any pattern or obvious cause for the notifications. Anybody have any clues or suggestions for what to check?

I'm finally getting around to moving from my venerable ISY994 to EISY. The migration instructions are clear and I've updated both IoX and the EISY to the latest versions (5.8.4), and also PG3x to its latest version (3.2.27). I have a number of node servers using the original Polyglot and talking to the ISY994. I realize that many (all?) of these can't be immediately migrated to PG3x versions, so I would like to check on the configuration details of these before moving to the PG3x versions on the EISY. However, I'm having trouble accessing Polyglot to see these older node servers: http://"ISY IP address":8080 doesn't work - "can't open the page because the server isn't responding" What am I missing or doing wrong? I saw references in some threads that once one updates to PG3x, it's no longer possible to see the PG2 home page? If this is correct, then why or how do Polyglot or PG2 node servers continue to run (in my case on the ISY994. Thanks, John

I’m also using the Web control 8 and would love to have a PG3 plugin to directly interact with it from the eisy. A question however, will a PG3 plugin work in PG3x?

KDFC.com out of SF

After updating & rebooting the EISY, the HA VM is up and accessible via a browser - everything is good. Thanks for help.

@apnar That worked; thanks very much. The HA VM install script ran with no errors. For my education, please: 1. Now that I've made the directory /etc/zfs, the "storage" zpool will mount automatically upon a reboot of the EISY? 2. What does the zpool export then immediate import do? I haven't been able to log into HA yet; the http://homeassistant.local.8123 URL doesn't work and I can't find HA in my router devices/hosts lists but I'll follow the "Home Assistant on easy not online" thread for help with that. Again, thanks for your help. John

It looks like I have a partition "storage" but not a pool......

@MWoods329 Thanks for the suggestions; however no luck. Attached are the the results of zfs list (there does not seem to be a "Storage" file system. Changing the directory to /storage before running the curl command gave the same error ..

Bump. Anyone have suggestions?

Living up to my moniker, I'm stumped: Per the "Increase performance or add redundancy?" blog, I installed and set up a NVMe in my new EISY using the script (sudo fl.ops setup.nvme.boot). I did answer "Y" (I thought) to creating an additional "Storage" partition (of 500 Gb) and zpool, for setting up Home Assistant in a VM. However when I run the HA install script (curl -s https://pkg.isy.io/script/create_ha_vm.sh | sudo bash) it errors at "cannot create 'storage/vms': no such pool 'storage'" (attached screen capture from Terminal). "gpart show" does show the 500 Gb partition (2nd screen capture); however "zpool list" shows only one pool (zudi). So while I have the disk partition, I apparently didn't successfully get a zpool set up? How do I fix this? I did set the NVMe up for maximum performance, not mirrored, so I can't go back and rerun the NVMe set up script again. Suggestions and/or directions for a FreeBSD & ZFS noob would be most appreciated. John

I have a question about using antenna extension cables for the ZMatter board My Polisy is on a shelf in a computer rack in the basement. Because the equipment above and below shelf is much deeper than the Polisy, the Zwave and Zigbee antennas (from the ZMatter board) would have to be horizontal and surrounded by the grounded metal rack and computer cases - not good for range according to UD tech support. So I would like to add short (~1 M) extension cables to get the antennas out of the rack and vertical. I looked up the specs for sma extension cables, typically rg316 cable. At Zwave and Zigbee frequencies (Zwave = 908-920 MHz; Zigbee = 902-908 MHz & 2.4 Ghz), the attenuation would be ~1.25-1.90 db/1 M, so not much. For any of you with real rf experience, have I missed anything important? I did notice that the ZMatter board antenna extension cables to the Polisy case are rp-sma. Thanks

@TechmanYes, I was thinking the same. For some reason my IoP seems pretty resolutely stuck on v5.4.0. I just wanted to make sure I wasn't missing something. Thanks.

@Techman Still no luck: I unplugged the Polisy for >30s, plugged it back in and let it reboot. Then cleared the java cache, restarted IoX Launcher from start.jnlp. Polisy IoP is still v5.4.0. How do I do an update, since 5.4.0 doesn't have the "upgrade packages" option?

Possibly relevant: I have Polyglot v2 still installed. And when I open Polyglot v3 (policy:3000/dashboard) under "ISYs" it shows only my ISY994, not the IoP instance. However, IoX Launcher does show both the ISY 994 and the Policy IoP (which is also still showing as v 5.4.0)

No luck. I pushed the reset "button" on the front of the Policy (a paper clip into the hole and felt a click). The left most light on the Policy went from flashing to solid. I waited several minutes, then cleared the Java cache (applications, resources, deleted applications), restarted IoX Launcher (from downloaded start.jnlp file) and opened the IoP admin console. It still shows v 5.4.0

I just received my ZMatter board this afternoon and have hit a snag getting ready to install it: The UDI instructions say to check the Policy OS via ssh. Mine is FreeBSD 13.0-RELEASE-p6, instead of 13.1 (as later instructions for IoP indicate it should be be). So I tried the "Upgrade Process - As of July 2002" in the wiki. With the IoX Launcher, I open the admin console for IoP; however there is no "Upgrade Packages" under configuration/system. With some forum sleuthing I saw that this is because IoP is only v5.4.0, and the "Upgrade Packages" was added in v5.4.4. I tried the "automatically upgrade Policy to 5.4.4" option under help but this doesn't work. The admin console closes, then I cleared the Java cache. After finding the IoX Launcher file again (clearing the Java cache deletes this) and waiting a few minutes, I reopen the IoP admin console - and it still says v5.4.0. I've tried restarting the Polisy; no improvement. What am I missing or not understanding?

I found that a small hemostat (https://www.hopkinsmedicalproducts.com/product/kelly-hemostat-scissors-HMP?option=571002) works well, both for pulling out the set button, then for the long press in.

@javi. Sorry, I did not mean to hijack this thread. I will start a new one. Unfortunately, your instructions did not resolve the problem….

Another subscription problem, possibly related: My iPhone (iOS14.7.1) is not/will not connect to the Portal (UD Mobile 0.6.1): When I open the app I get two error notifications "System: Valley Lane (the name of my system) Error, then "Could not get get Portal credentials. Portal is not set". When I go to Settings/ ISY Portal Accounts and click on the account there and then "continue", I get "Starting subscription", then again quickly "Could not get get Portal credentials. Portal is not set". I do have a Portal subscription, recently renewed - and UD Mobile and the Portal connection are working fine on my iPad (iOS14.8.1) with no error messages . On the account page (on the iPhone) and clicking "login", I get the circular icon, then eventually "ERROR Authorization Tokens are Null" Clearly something amiss with my Portal account settings on the iPhone but how do I fix this? Other than this hiccup, UD Mobile has been flawless and getting better with each update. Thanks, John

Sorry to pour cold water on this. I'm a molecular biologist and this is 99.7% advertising smoke and mirrors, Any anti-microbial activity would be vanishingly small/exceedingly difficult to demonstrate.