larryllix

Are you using a more recent mobile phone with Andoid 5 or later or an iPhone with necessary version? The Alexa app runs under windows but much is missing or doesn't function. You don't connect devices to ISY Portal. You connect the Alexa app to the UDI v2 skill that has a link to your ISY Portal account. This account security is getting stupid. When they ask for the password they don't specify Amazon account, alexa account, ISY Portal account, ISY device account, router account, WiFi account, or Admin Console account. Most just guess until one works but they have already given out all their security credentials to some snoop app they don't even know functions as stated. Sent using Tapatalk

Can you post your programs affecting this device? Did you know you can do searches for a particular device in your programs? Sent using Tapatalk

That may be due to your PLM sucking up all the noise to protect the rest of your house. Seriously though. It takes a crappy quality PLM and a noisey environment to make a bad combination. I think we know the first element is true but some have the second element also. Sent using Tapatalk

Looks like four. 2 internal and two external https://corpshadow.biz/pcengines/apu3b2-system-board

Perhaps Insteon could announce the latest technology for their products?...…... Quality Control!

Sounds like their attempt to crap down the throats of anybody that isn't Apple backfired and now they are trying to pick up some pieces. They need to put their money where their mouths are. Since Rob took over they have released the amazing Insteon Siren? Another upgraded X10 beeper? And they are still putting out PLM 2.0s? Amazing progress over 2-3 years.

When was the last time you factory reset the MS II? What is your UI version? I don't see you pinging UDI using the forum notification method. They aren't mind readers. If you are only using scenes with the MS II then ISY is not involved. Have you read any of the responses here?

You would have to notify them or do something to get their attention. Not every post is read. Try the '@'+nickname method in a post.

The WC8 supports up to 16 x 1-Wire devices. Early WC8 models had some trouble with this feat but this has been reported to be resolved mostly. Some experimenting with the 1wire transmission line terminations may be required to make it work properly with multiple 1wire devices. Mine has a resistor and capacitor installed at the board. Other users here report 16 probes successfully with ISY. My older WC8 board has worked with 2 x 1-wire temperature probes for several years while it counts pulses from my anemometer, calculating wind speeds and wind gusts, while sending 8 Webset packets to my ISY every 20 seconds, no problem. I was sending 8 Webset packets to ISY every 10 seconds but wanted to lengthen my sample period for the wind calculations. ISY has no problems handling a Webset packet from the WC8 every second while it performs many other tasks simultaneously, like PolyGlot plus NodeLink and several other home brew RPi projects updating variables.

I still get my reports at 8:00 AM every morning. Helps me track HVAC usage and Cold Cellar ventilation. With our high humidity here, in the summer it is hard to keep the walls from weeping and molds out.

There are a few ways to do this that I know of - Use io_guy's software on a RPi or other CPU - Use totally ISY software to keep track of run times without any real time logging. ….found it! - Use mwareman's technique mostly built inside ISY and using an external browser

Yes! There will be coloured oval cornered rectangles beside each device containing a "1011" code to indicate trying to write binary to the device(s).

Are you using European frequencies with North American Insteon?

Factory reset each one, and then restore it. You better get some methods in place to prevent this from going through your house in the future. It sounds like the lightning got into your wiring. This may get costly and annoying, and not just for Insteon. If you do not understand electrical discharge phenomenon, look for a sharp electrician.

Nice. Justa suggestion: Put Wait 2 Seconds between each Set line. You are writing data to each device's eProm and it can take a lot of Insteon comm talk time. This may tie up your other HA communications and flood ISY's caching, causing some operations to be dropped, devices to be marked as 'comm failure', or mess up program timing in other programs. Most Insteon operations are fairly quick and don't tie up much comm line time but updating eProms in devices can take much longer. This seems like background process anyway without any urgency.

You likely have battery Insteon devices waiting to be put into linking mode so that ISY can finish writing updates to them. That can bog ISY down attempting to write updates every time that device has any action. A factory reset of ISY with a follow up Restore may clear things out also.

import urllib.request import base64 # Server (this CPU) IP address server_IP = '192.168.0.175' server_port = 8000 # ISY parameters to be defined by user ISY_username = 'zzzzzzz' ISY_password = 'xxxxxxxx' ISY_IP = '192.168.0.161' # Heartbeat to ISY variable ISY_HBpage = 2 # 1=Integer, 2=State ISY_HBaddr = 83 # ISY heartbeat variable ISY_HBperiod = 90 # In seconds. toggles ISY flag variable ISY_HBlast_sent = 0.0 # Write ISY handshake variable via REST i/f def write_ISY(data): ISY_rest = "/rest/vars/set/%s/%s/%s" % (ISY_HBpage, ISY_HBaddr, data) get_url = urllib.request.Request('http://' + ISY_IP + ISY_rest) #format the URL ISY_authorise = base64.b64encode((ISY_username+":"+ISY_password).encode('utf-8')) #encode it get_url.add_header("Authorization", 'Basic %s' % ISY_authorise.decode('utf-8')) try: r = urllib.request.urlopen(get_url) returned = r.read() r.close() except: report("NRBridge: ISY heartbeat send failed!***") return

Most problems I have seen here are solved by disconnecting the Alexa skill from your UDI account, and then reconnecting them. It seems to take a fresh data grab and all is fixed again

Mine didn't.

I had a random problem with lights turning themselves on for about a year. Finally I recognised the pattern as one of my scenes. After digging through programs each occurrence for months I found errors in the error log after some Humidifier On (a OnOff plug-in module) commands. I unplugged the module and plugged it back in and it hasn't done it for about two years now. It seems my OnOffLinc module was sending out a scene On command (well noise, interpreted as a scene on) instead of an ACK occasionally. The module was not in any scene at all.

For the CAI Webcontrol board you don't need a RPi at all. See my screenshot (above) as the WC8 board has it's own I/o interface designed to support ISY's Rest interface without any further hardware.

The Network Module can send almost any style of Ethernet packet out. The Rest interface inside ISY can receive formatted Ethernet packets to control programs, variables, scenes etc.. The CAI WC8 board would fit your bill perfectly. it would take only a few lines of code and rest interface commands installed into it's table to write to ISY from the logic inputs on the WC8 board.

What ISY firmware and UI are you using? They must match.

@k0d3g3ar Welcome to the UDI forums! Great entrance you made! Thanks from all of us!

I have none now but... Can you use "switched" instead? Can you use "Off"? Can you use < 1% ? Why so many decimal places? I suspect ISY is showing you a rounded off value and never really matched 0.0000% BTW: Your AND specifies you must have both off. This will not work with "Switched" triggering. Two devices are never triggered at the same time with ISY logic.