larryllix

Yup. Now they are pushing the RPi4 with 8GB, needs fan cooling and so on. Meanwhile you can buy a Windows 11 PC with HDD and 8 GB Ram for about the same price. Gone are the days of the little cheapie computer. Some of the chopped down versions are much cheaper but you still need to add a keyboard, mouse, monitor, case, power supply and a few cords and SD card to make it actually be something usable.

My wife and I both like to push each other's buttons too. Sometimes the taps escalate into closed hand taps and then it's time self...never mind. Sent from my SM-G781W using Tapatalk

Try this for URL escape sequences. https://www.urlencoder.org/

I know very little about Zwave. I have avoided it since the beginning of time, until about 1 year ago and my initial trials turned me off. For now they are all in a box, at least until I downsize my abode. I think @Techmanis your guide there.

Much easier to read if you right click on the program in the program tree and select "copy to clipboard" then paste it into your post using the '<>' tool. BTW: I dissembled some of Bill Gates code back in the 70s. He was not a good code writer.

I attempted to use the sudo pkg update/upgrade method and got permission problems. See partial output below. -- Since version 1.25 HTTPS connections are now verified by default which is done via "cert_reqs = 'CERT_REQUIRED'". While certificate verification can be disabled via "cert_reqs = 'CERT_NONE'", it's highly recommended to leave it on. Various consumers of net/py-urllib3 already have implemented routines that either explicitly enable or disable HTTPS certificate verification (e.g. via configuration settings, CLI arguments, etc.). Yet it may happen that there are still some consumers which don't explicitly enable/disable certificate verification for HTTPS connections which could then lead to errors (as is often the case with self-signed certificates). In case of an error one should try first to temporarily disable certificate verification of the problematic urllib3 consumer to see if that approach will remedy the issue. isy not running? (check /var/isy/isy_daemon.pid). mkdir: /var/isy/FILES: Permission denied mkdir: /var/isy/FILES/LOG: Permission denied Checking to see whether or not we need to migrate from 994 ... Setting permissions for ISY directories/files chown: /var/isy: Permission denied chmod: /var/isy: Operation not permitted Setting permissions for LEDs chown: /dev/led/led1: Permission denied chown: /dev/led/led2: Permission denied chown: /dev/led/led3: Permission denied chown: /dev/led: Permission denied chmod: /dev/led/led1: Permission denied chmod: /dev/led/led2: Permission denied chmod: /dev/led/led3: Permission denied chmod: /dev/led: Permission denied checking udx version = 2620 for possible upgrade udx is upto date udx is not running. udx service must be running Starting udx. cd: /var/udx: Permission denied /usr/local/etc/rc.d/udx: WARNING: failed to start udx you can disable uftdi driver by adding isy_load_uftdi=NO in /etc/rc.conf 7 1 0xffffffff81d12000 8320 uftdi.ko Starting isy. cd: /var/isy: Permission denied /usr/local/etc/rc.d/isy: WARNING: failed to start isy [admin@polisy ~]$ chown: /var/isy: Permission denied chmod: /var/isy: Operation not permitted Setting permissions for LEDs chown: /dev/led/led1: Permission denied chown: /dev/led/led2: Permission denied chown: /dev/led/led3: Permission denied chown: /dev/led: Permission denied chmod: /dev/led/led1: Permission denied chmod: /dev/led/led2: Permission denied chmod: /dev/led/led3: Permission denied chmod: /dev/led: Permission denied checking udx version = 2620 for possible upgrade udx is upto date udx is not running. udx service must be running Starting udx. cd: /var/udx: Permission denied /usr/local/etc/rc.d/udx: WARNING: failed to start udx you can disable uftdi driver by adding isy_load_uftdi=NO in /etc/rc.conf 7 1 0xffffffff81d12000 8320 uftdi.ko Starting isy. cd: /var/isy: Permission denied /usr/local/etc/rc.d/isy: WARNING: failed to start isy

missed that point. Sent from my SM-G781W using Tapatalk

...advice from the girlfriend?

Insteon devices can have many links. One for commands and one for status back messages and more. When your ISY does a query and doesn't get a proper response it marks it as "can't communicate". When ISY issues commands, it assumes the device did what it wanted and you see that. If the devices reports a different status ISY will update and you will see that. A query usually gives the true picture. Try right clicking on the device and select "Restore" to write proper links back into the device. If that doesn't correct the problem then you likely have some interference in your Insteon comms. I would suspect the last item added...your Zwave device. Unplug it and see if things start to work after a restore.

Microprocessors did not exist in the public until 1970-71. Apollo 11 was 1969.

You need to experience VR for a while...then you will believe. Besides,...we are not programmers, we are just script writers.

HTML5 cannot replace a programming language. HTML5 is a text formatting language... with some minor exceptions.

I would base the whole thing around a single state variable. 0,1,2,3 value for Off, Low, Med, High. Then I would write four programs to set the variable to 0,1,2,3 Fan High, Fan Med....Fan Off Then I would write four programs to run scenes for the KPL lamps (with a Wait 2 sec) and fan speeds to the appropriate speed to match the variable 0,1,2,3 With Alexa I would use the four programs to control it... ...Alexa turn on medium fan. Now you can control the fan sped from almost any program by setting the variable to the desired speed and programs can never lock each other out, or get confused. KPL lamps will change automatically, no matter where you set the fan speed variable from. With this technique if you need to "borrow" the fan for something temporarily, like exhaust a fume or some reason to make the fan speed on high for ten minutes, then just save the fan speed variable somewhere else, set whatever you want and then restore the fan speed to what it was before the "borrow", when you are done The existing speed might be Off. It always works.

What's with all the anti-Matter?

if you are running on an RPi you would reimage the SD card. PG2 has so many parameter files it will likely never be revealed. Me thinks PG3 does also. Sent from my SM-G781W using Tapatalk

Let us know if it ever becomes a reality. Matter has only been three years now and still being thought out, apparently.

I don't believe a total wipe has been programmed into IoP yet. Good idea! Before anybody starts populating their IoP with programs, save an empty backup!

Is the program actually running Else or is your resultant flag just indicating it ran Else? I wondered about your True/False constants. If they have lost their values. What version of IoP are you running?

Are you actually located in L.A.?

What fun is that. Stumbling around in a dark bedroom can have benefits. I have three kids that were "Accidents". However I have red lights in my bedroom but they come on with a long delay, so the excuse remains valid.

Have you found a motor to unwind measured amounts of toilet paper though? You will have to compensate for the changes in roll diameter and know when a roll change has been effected. ISY should be able to handle a chart of roll diameters by brand in integer variables to keep the issued paper constant. Would it appropriate for heavier people to get more length of paper issued to them? Now we need somebody to write a NS for PG3.

Sounds like IoP didn't grab the links properly out of the PLM upon transfer. Links must be stored in ISY/IoP or else restores couldn't work. Also the transfer software must be new and likely need some bugs ironed out.

If ISY hung, it couldn't logic out enough to reset itself anyway. I have had a few "hung" incidences over the years, not always ISY's fault, existing without an IP address, and a few other weird things that a power cycle usually fixed. Biggest problem is detecting them.

I have mine on a WiFi remote switch. What would be really nice is an Insteon power cycler so ISY could send the signal based on programming logic, it would turn the power off and 5 seconds later turn it back on. ...Not gonna' happen because it would be an admission by programmers that their software / firmware can actually hang. My Insteon network can power cycle my LAN and Internet equipment based on logic. My Internet and LAN equipment can power cycle my Insteon equipment based on my frustration from around the world.

Although I use a few folder conditions they are dangerous for most people. They are obscure and can cause programs to stop unexpectedly midstream, and leave functions not complete causing other problems downstream. Most users would never even know they exist and their states are not very obvious. Additionally IMHO UDI has changed how folder conditions work. A year and more back when you added a condition to a folder, it was always considered false and no programs would run, unknown to the programmer. Now when you install a condition in a folder, the logic is run immediately (sometimes) to update the state of the folder, and alleviate the previous problem I mentioned, and this may be an unexpected result also. Another problem you just spent time on is programs inside a False condition folder, will not run when invoked manually with no indication of why. This problem has killed more space and time on this forum than most other problems. It should be removed from ISY programming primitive programming options, after variables were introduced many years ago that follow more modern structured programming concepts.