larryllix

If you really need to have the box fill in, you can - wait until dark - put the unit in a dark closet and wait 5 minutes - open the back and click the link button 5 times in rapid sequence. IIRC some may take 7 clicks in rapid succession.

Accurate temperatures in the house. I use 0.3C deadlines on both my ecobee stats without any short cycling, just no huge waves of hot and cold. Short cycling usually refers to the off time between runs for an air conditioner. ecobee allows that to be set also. Sent from my SM-G781W using Tapatalk

My older Roku Stick supports the TV off via CEC but the newer Roku has no support for that and the TV power button sends iR only now. For some reason Roku has abandoned the CEC feature Sent from my SM-G781W using Tapatalk

You cannot modify settings/options in battery operated devices unless they are put into linking mode first. If you enable the remote settings DIP switch, the rest cease functioning. IIRC you can only set options in the main page for an Insteon MS. The ancilliary pages will not allow setting options.

Sounds like you have some interference with your comms happening. Possibly your new PLM is not good? Are you using the same PLM as your ISY994? Have you done factory reset and Restore on each device?

Do you have dual band Insteon devices nearby each battery operated device? Battery operated devices are RF only and not likely to communicate with your PLM directly.

If both devices support CEC / HDMI then it should work. My older Roku Stick turns off my TV but the newer units will not. IIRC: If the Roku remote has a TV power button on it then it controls the TV via iR only. If no power button for the TV then it will control the TV via CEC/HDMI. Roku support plays dumb about this, as usual.

Battery devices will not respond to status queries unless they are placed in linking mode first. However by clicking on Query for battery devices you can flood your Insteon comm cache until ISY bogs right down. I suggest you put each battery operated device in linking mode, one at a time, and then use write updates to each device before doing the next, until all your 1011 icons are gone again.

Didn't you have a hub that was just bricked? Did your hub work right out of the box or did it take human intervention? What did it do right out of the box? Consume energy? How thick was the manual you got with it?

You may have just pissed off a few thousand happy users of some of the best and most reliable products in the home automation world. UDI works with it's customers and supports them...well. You just got caught in an upgrade that caused your device to need more hardware and UDI supplied it. That doesn't make the product garbage. It makes the product supported and you not a good fit for the development going on.

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

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.

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

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.?

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.