DaveStLou

I'm up and running too. Thanks!

[admin@polisy ~]$ sudo pkg update -f Password: Updating FreeBSD-base repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.txz: 100% 10 KiB 10.0kB/s 00:01 Processing entries: 100% FreeBSD-base repository update completed. 113 packages processed. Updating udi repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.txz: 100% 108 KiB 110.3kB/s 00:01 Processing entries: 100% udi repository update completed. 398 packages processed. All repositories are up to date. [admin@polisy ~]$ sudo pkg install FreeBSD-kernel-polisy Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The most recent versions of packages are already installed =====After reboot===== [admin@polisy ~]$ sudo service udx restart Password: Stopping udx. Waiting for PIDS: 1119. eval: cannot create /dev/speaker: Device busy eval: cannot create /dev/speaker: Device busy eval: cannot create /dev/speaker: Device busy CURRENT OS 13.0.3 No need to upgrade the OS libwebsockets already removed flashrom already removed net/avahi already removed dns/nss_mdns already removed pkg already installed dbus already installed ca_root_nss already installed dual-dhclient already installed bash already installed mongodb36 already installed libnghttp2 already installed git already installed polyglot already installed mosquitto already installed powerdxx already installed e2fsprogs-libuuid already installed c-ares already installed rapidjson already installed mongo-c-driver already installed npm already installed isy already installed tpm2-tools already installed tpm2-abrmd already installed py38-sqlite3 already installed Starting TPM security services Starting udx. [admin@polisy ~]$ sudo service isy restart isy not running? (check /var/isy/isy_daemon.pid). loading uftdi.ko kldload: can't load uftdi.ko: No such file or directory /usr/local/etc/rc.d/isy: WARNING: failed precmd routine for isy [admin@polisy ~]$ uname -a FreeBSD polisy 13.0-RELEASE-p3 FreeBSD 13.0-RELEASE-p3 #11 releng/13.0-n244752-b368bb75bad: Tue Jul 13 23:39:11 UTC 2021 ec2-user@bsdev.isy.io:/usr/obj/usr/src/amd64.amd64/sys/POLISY amd64 [admin@polisy ~]$

I'm seeing the same thing.

I haven't tried this yet but I found this webservice that appears to do what you're looking for: https://github.com/TaiPhamD/WindowsShutDownWS

Thank you! Though, unless I'm missing something, I am unable to edit again once I change a node to "Status Only".

I'm seeing the delay much less frequently. My experience is much like Jimbo's. The workaround I've noticed is if favorites are not responding, I click the Home button and then right back to Favorites and it immediately responds. Hopefully that may help you with what's happening under the hood. Agree!

Glad it's not just me. It's inconsistent though. Sometimes it works fine and next click doesn't> I haven't figured out the pattern.

@Javi Great stuff! I'm reconfiguring now. Question - Is there a way to have a node that just display the status of a switch without the function of turning it on and off? Also, frequently the elements of the app do not respond to my tap (Android v.0.82) on Android 12 my Pixel 3 XL. I've found that clicking back and forth between the Home and Favorites allows clicking to resume. This has been happening since the grid layout was introduced.

What type of motion detectors (zwave, Insteon, brand, etc)? And as @lilyoyo asked, what firmware and UI are you on?

I couldn't get my old USB PLM to be found either. I'm using a extra serial PLM with DB9 cable.

You can see if it's connected here: Mine:

I'm up and running with a single device and a single node server.

So true!

In my case, it's only off by 2 seconds from my coordinates-based location.

I don't know what changed but It is working now. To answer your question http.

@Michel Kohanim I haven't changed the default Username/Password which works when I login through Admin Console but I am getting this in PG3 when I attempt to connect to Polisy ISY: I'm not sure of the actual status since it warns credentials are wrong but then reports the database was retrieved. When I attempt to install a nodeserver in the Polisy ISY, I get the following: Also note, in the attached error log, that the year is logging as 1951. Year is showing correctly in Polisy ISY. ISY Error Log.v5.0.1__Tue 2021.07.20 06.46.08 AM.txt

I connected my 2413U this morning. It's stuck with System Busy, looping over and over "Refreshing Views". It's been years since I last used this PLM (V1.B) but I factory reset it before I connected it. Since system busy message is up, I can't get to anything to look at logs via the Administrative Console. Is there somewhere else I can look via SSH to see what's going on? The PLM may be bad for all I know. Update edit: I realized I can get to the Error Log. Which is attached. Oddly, the date in the log shows the year 1951. I checked via SSH and Polisy is reporting the correct date. Also note in the left corner of screenshot that the AC is showing correct date as well. At this point, I don't believe it's communicating with the PLM. I ran usbconfig which shows the PLM is connected at least: ugen0.2: <FTDI FT232R USB UART> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (90mA ISY Error Log.v1.3.0__Sat 2021.07.17 08.53.43 AM.txt

I found one today that I forgotten I had. Updated ISY on my Polisy. I'll hit it in the morning.

Hash and spam is NOT a good combination either.

Possibly spam?

It's just the node servers.

Under Settings > Polisy Configuration, click the [Download] button right above and save the file wherever you want.

It's been awhile since I did this but I believe what you propose DOES work. Select and copy the configuration table for each of my Nodeservers and paste into a document. Sometimes I have to manually add something that doesn't copy but I have found that there's always something I forget if I do it from memory. Let us know how it goes!

I use the Kasa app to set up the device names which are pulled into the Kasa Nodeserver so there's no configuration there. A Kasa account is used only to control outside of the LAN which I don't use. The app works locally without logging in but blocking traffic to *.tplinkcloud.com assures there's no phoning home. Of course you do need to open it up to install firmware updates to the device but I've only had to do that when I first installed the device.

I second the Kasa plugs. They emailed a code this morning for 30% off the exact item @MrBill llinked to above. Unfortunately, it is a one use code which I quickly took advantage of but even without the discount, they are a good deal.... and Prime Day starts tomorrow.