larryllix

Many of my earlier RPi devices presented two different MAC addresses for WiFi and Wired Ethernet. Therefore my routers could never assign the same IP address for the two different protocols from the same RPi.

When I have multiple logics affecting the same device cycle I find a control variable the simplest and most reliable method. With a variable once the variable flag is turned on and the scene is turned on it cannot be turned on any more and cannot be reset by other logical inputs. You could try this If From 6:00:00PM To 11:00:00PM (same day) Or From at Sunset - 30 minutes To 11:00:00PM (same day) AND Light status is Off <---- pick a major light out of scene Then Set 'Kitchen RGBW + puck' On Else Set 'Kitchen RGBW + puck' Off

That and the four tap phase identification method on AC based devices are two hidden goodies that SmartHome fell down on. Were they trying to hide it from their users or just insecure that China would continue to add those features in the firmware so they didn't document them? Who knows? Doh!

hmmmm...some of the tiny pamphlet docs mention that sequence, but not all. If 5 clicks doesn't make it update within a few seconds, try seven about as fast as you can click. I usually do to test the dark while holding it under my short and/or hand. It is good to setup the sensitivity setting also.

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.

Wow! You are some gutsy guy! Went from a code monkey, to project manager, to CEO, involved in standards groups, and now Team Leader of a new quest! Go @Michel Kohanim!!!

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.

Yes! You can buy used PLMs for around to 300 to 500 dollar mark now. Sent from my SM-G781W using Tapatalk

Don't be tossing it yet. Wait until the fat lady sings. Many people will want the devices for years to come as they have PLMs to spare. I have four myself. UDI is inthe process of attempting to aquire rights to manufacture PLMs as well as possibly more than we know of. Don't give up yet. There is likely a way to fix your hub that will be revealed later by some hacker.

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?