mmb

I'm still seeing intermittent problems. This yesterday evening the Echo was offline but this morning ok.

@larryllix thanks for clarifying your post.

The bios lives on the hard drive? Interesting...

The Cdn$/US$ exchange rate is terrible as well (35%). I'll hold off for a [quite] while...

Edge has an Internet Explorer compatibility mode if needed...

Zooz told me there were a number they had to replace. Fyi the replacement worked perfectly.

I don't remember all the details but I ended up sending it back to Zooz for a replacement.

I have an older Chamberlain and used Insteon equipment to do mine. Obviously that will be a problem. I presume you're asking for z-wave because your Chamberlain doesn't support MyQ?

Thanks i didn't do any further testing because it was hard crashing the ISY and it was taking too long to recover. I just did the pita gmail procedure to disallow insecure apps.

I think some ISY libraries are out of date because Polisy does work properly with Outlook.com. Have we hit the end of updates for the ISY?

Thanks for my post, the point was the Outlook.com settings actually crash the ISY, like a full hard reboot and it didn't come back. A full power down was required to get the ISY to boot. I did replicate the problem several times. I did not pursue it any further and went thru Gmail process as noted. I use Gmail now with less secure apps off.

I reported this a few months ago but got no response. I ended up going through Google's process for less secure apps.

I found a handy slick little Windows program when I was setting up Home Assistant called Linknet that I used to reset my Insteon USB stick. You can use it to look at current links if any in the stick or PLM and there are other features as well. https://insteonsoftware.com

Or are updates continuing to be released and I'm just missing them? Thanks!

I expected that was you're endpoint. I need a vpn for other services so I just use it. Do you know what the Node Server listing is for in Portal? Maybe that was a place holder for access.

@kzboray I just use portal Polisy like I do for the ISY. Or are you referring to Polisy/Polyglot? In that case I use a vpn.

@jkraus good work! Next step, https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3 So you can talk to your ISY ?

@oper8 highlight the variable row, right click mouse Change Precision.

Follow this step by step https://wiki.universal-devices.com/index.php?title=ISY_Portal_IFTTT_Integration

@jkraus look into UD's ISY portal, makes all of it easy.

Perfect thanks!

For various reasons like Insteon closing its doors, I’ve had to shutdown my Polisy while I do some testing with the Hub. My prod system is an ISY and both this device and the Polisy are loaded onto UD Mobile. While in UD Mobile to control the ISY I’m constantly prompted with an error message that UD Mobile can’t connect with Polisy which of course I know because I shut it down. Short of deleting Polisy from UD Mobile is there a way to disable or pause these messages? Thanks!

Updated via command line and everything seems fine. ISY Launcher reported I had a mismatch on the FW and UI versions which I corrected. Deleting java cache and start.jnlp fixed. UI date is fixed, my one ZW scene test was fine, Insteon and ZW device tests are fine. I haven't migrated to Polyglot V3.

For me the X10s appeared in the ISY logs by hundreds at a time after I installed a new UPS. I moved the ISY from my small server room to my office and things cleared up immediately, no more X10. All the X10 records had a time/date stamp.

I had a problem with a Zooz multi sensor device that was flipping back to default. The sensor comes set for Fahrenheit as default but in Canada we use Celsius. It was relatively simple to set the sensor to C using the Polisy parameters but the next day I would check and it had reset itself to F. I contacted Zooz and they never heard of the problem but suggested maybe a problem with the Polisy. The manual does refer to a nightly check with the controller for updates but I don’t think Polisy supports that functionality. Maybe the check in caused the reset to default? The sensor went back to the seller.