BillB66

True, I don't need to run HTTPS. I would like to, and Polisy is built on a platform that supports a robust infrastructure (FreeBSD) that can support more then just self signed certs. Also, it used to work with polyglot.

Blame it on OCD, and Chrome's inconsistent behavior on letting you click through on an cert from an untrusted CA. Good suggestion on a support ticket. It may end up being a feature request based on how the Self Signed certs are being handled in pg3. (just from looking at the setup)

Even my epson printer control panel supports custom SSL certs. What is the target audience if certs are too complex, yet they still understand that a self signed cert is safe to click through. Boggles the mind.

Pretty poor answer. USI could at least document where they are putting the certs. Their placement/naming is non standard. Cost is a red herring when talking about user supplied certs other then the documentation effort. The thread is deep in opinions, but light on facts. Managing/Issuing certs with Let'sEncrypt and ACME is trivial. Took me about 15 minutes to set it up. Then about a day to automate installation of the certs to QNAP, Plex, nginx, etc. https://letsencrypt.org/docs/client-options/ it's also free. Far lower investment cost then using IoP. Disappointed in the stance to say the least. Thanks, Bill B.

Not a fan of using an untrusted cert in a browser. Have have a wildcart cert for my domain that I would like to use. Is there instruction on where they need to be installed? I see various SSL installed, which one is used for the website? /var/polyglot/pg3/ssl /var/polyglot/ssl Thanks, Bill B.

Fixed with 2.0.5. Thank you.

Still seeing the same errors. Pretty sure it maps the the screen saver or sleep mode. So I get a lot of them when I am not watching any of my 9 Rokus (thousands of them) 2023-02-17 13:24:45,747 Thread-2354 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2023-02-17 13:24:45,750 Thread-2353 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2023-02-17 13:24:45,767 Thread-2356 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2023-02-17 13:24:45,774 Thread-2352 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2023-02-17 13:24:45,793 Thread-2357 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction.

Same issue, issued the manual PKG update command for PKG. Processing normally now via IoP update sudo pkg install -r udi pkg [admin@polisy ~]$ sudo pkg install -r udi pkg Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. New version of pkg detected; it needs to be installed first. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pkg: 1.18.4 -> 1.19.0 [udi] Number of packages to be upgraded: 1 8 MiB to be downloaded. Proceed with this action? [y/N]: y ... Once issued pkg is updated and can update polisy from within IoP sudo tail -f /var/udx/logs/log [1/2] Fetching ca_root_nss-3.86.pkg: .......... done [2/2] Fetching udx-3.3.2_5.pkg: .......... done Checking integrity... done (0 conflicting) [1/2] Upgrading ca_root_nss from 3.85 to 3.86... [1/2] Extracting ca_root_nss-3.86: .......... done [2/2] Upgrading udx from 3.3.2_4 to 3.3.2_5... removing mdns configuration file [2/2] Extracting udx-3.3.2_5: .......... done executing from /usr/local/etc/udx.d/static Starting uninstall Once udx is fully uninstalled, isy service stops mosquitto not running? (check /var/run/mosquitto.pid). ud_net_detect not running? (check /var/udx//dudnd.pid). stopping udx @ 1284 Thu Dec 15 09:35:49 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: using hardware tpm Thu Dec 15 09:35:49 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: starting udx v3.3.2_5 ... Thu Dec 15 09:35:49 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: verifying signature ... Thu Dec 15 09:35:49 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: udx v3.3.2_5 signature verified! Thu Dec 15 09:35:49 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: ipv6 all OK Thu Dec 15 09:35:50 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: FreeBSD.conf is AOK ...

Sounds good. Yell when it is fixed and I will update. In the meantime I created the node manually. Looking at the code, I already see special handling for &, is there a regex of valid chars for node name somewhere? https://github.com/BME-node servers/udi-roku-poly/blob/master/nodes/roku.py#L78 Also if you are in there, I see a lot of Error spam on application 2022-10-16 12:37:03,818 Thread-311584 udi_interface ERROR roku_node:update_status: App id 0 is not mapped to an appliction. 2022-10-16 12:37:03,831 Thread-311579 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction.

Guessing the " needs to be escaped. When I tried to created manually on the ISY with the " in the name gave ISY gave a Bad Request. I do see the nodes under the node server. 55" TCL Roku TV - 7125x 2022-10-14 17:38:59,066 MainThread udi_interface ERROR roku:updateNode: Is TV = True 2022-10-14 17:38:59,067 MainThread udi_interface ERROR roku:updateNode: Adding Roku TV node 81739 32" TCL Roku TV - 8116x 2022-10-14 17:39:13,059 MainThread udi_interface ERROR roku:updateNode: Is TV = True 2022-10-14 17:39:13,060 MainThread udi_interface ERROR roku:updateNode: Adding Roku TV node 30106 All the non TV Rokus did not have an issue (7)

Found the issue, Policy GUID has a typo on it. Working now.

I must have missed a step somewhere. Using existing ISY994 unable to purchase any of the node servers, or refresh listing on the Purchases tab. p2 works fine. What am I missing?

just checked. Now I am getting nothing in the error log. However still not working. Short of wireshark, what other options are there to get troubleshooting data.

That was my thought as well. However I have updated the password and ensured that the characters are ascii just incase Roomie is doing something odd with special characters. Any other thoughts? I have updated the username/password a few times via copy/paste from my password safe. Thanks, Bill B.

Working on integrating ISY and the SimpleControl (Formerly Roomie Remote). I am gettting a series of errors in the logs when I try to use the interface from my iphone. Any troubleshooting help would be appreciated. The IP listed is from my iphone on the home network (192.168.0.115): Mon 2016/03/14 01:24:30 PM System -170001 [Auth:-10011] 192.168.0.115:61284->80, Num=3 Mon 2016/03/14 01:24:31 PM System -170001 [Auth:-10011] 192.168.0.115:61285->80, Num=4 Mon 2016/03/14 01:24:31 PM System -170001 [Auth:-10011] 192.168.0.115:61286->80, Num=5 Mon 2016/03/14 01:24:33 PM System -170001 [Auth:-10011] 192.168.0.115:61287->80, Num=6 Mon 2016/03/14 01:24:33 PM System -10108 Check log Mon 2016/03/14 01:24:33 PM System -170001 [Auth:-10011] 192.168.0.115:61288->80, Num=7 Mon 2016/03/14 01:24:33 PM System -10108 Check log Mon 2016/03/14 01:24:34 PM System -170001 [Auth:-10011] 192.168.0.115:61289->80, Num=8 Mon 2016/03/14 01:24:34 PM System -10108 Check log Mon 2016/03/14 01:24:34 PM System -170001 [Auth:-10011] 192.168.0.115:61290->80, Num=9 Mon 2016/03/14 01:24:34 PM System -10108 Check log Mon 2016/03/14 01:24:34 PM System -170001 [Auth:-10011] 192.168.0.115:61291->80, Num=10 Mon 2016/03/14 01:24:34 PM System -10108 Check log Mon 2016/03/14 01:24:35 PM System -170001 [Auth:-10011] 192.168.0.115:61292->80, Num=11 Mon 2016/03/14 01:24:35 PM System -10108 Check log Mon 2016/03/14 01:24:35 PM System -170001 [Auth:-10011] 192.168.0.115:61293->80, Num=12 Mon 2016/03/14 01:24:35 PM System -10108 Check log Mon 2016/03/14 01:24:38 PM System -170001 [Auth:-10011] 192.168.0.115:61294->80, Num=13 Mon 2016/03/14 01:24:38 PM System -10108 Check log Mon 2016/03/14 01:24:41 PM System -170001 [Auth:-10011] 192.168.0.115:61295->80, Num=14 Mon 2016/03/14 01:24:41 PM System -10108 Check log Mon 2016/03/14 01:24:44 PM System -170001 [Auth:-10011] 192.168.0.115:61296->80, Num=15