larryllix

In this case, using auto-pilot, the driver is supposed to be behind the steering wheel, with his/her hand(s) on it, ...but Telsa advertises a driverless, one-button-push, command that will park your one-upmanship-car in your garage, and then shut the garage door when parked. See what 4.3 $billions of your tax dollars can do?

That is just so wrong opening your vehicle to any successful hacker on the Internet too. It is bad enough when all these paranoia security freaks open up their door locks to cloud services. Meanwhile, the auto manufactirers have been approached to isolate CPUs between car functions, and convenience functions, due to hackers being able to wash your windows and disable your brakes if you have ABS,, from any WiFi access point.

It was suggested a while back to implement something like this in the variable substitution for notifications and Network Resources: subText(${var.2.13},"one","two","three","four","five","six","seven",......,"twenty two") Since the ISY core engine can't and proabably never will handle string processing the next best thing would be to substitute text for the human to read upon output only. I think UDI liked it, but some confusion taking it further into 0-15 = "Low", 16-37 = "Medium", 38-99 = "High" and other greedy advancement thoughts got in the way of any commitment from UDI. I know it will be considered for V6.

Thanks Teken but my ISY doesn't hang, only the admin console gui. It stops being updated automatcally from ISY but responds to Refresh anytime I need it. I mostly ignore it unless I want to do dynamic program testing and get tired of hitting refresh to see the updates. This is the same problem for a dozen different ISY firmware versions since 2014, and by many users reporting it. At times I had months were it never happenned at all. At times this was thought to be when Windows wnet to sleep or when the Admin Console ran as a background task. Now it began happenning totally at randowm, sometimes immediately upon booting AC. I was instructed in 2015 to try the secure port but that was a flop after months of trial. AFAIC it is just some misunderstanding of java code implementation.

LOL The secondary button triggers programs just fine. I use mine for combination locks wit several different combinations to do different things like reset water leak responses, turning the well pump or washing machine back on or turning on/off the notification system. But yes the primary LED brightness can be controlled day/night with program control.

I have no real need to see any events I didn't already set up to notify me in a program. I spent some time with HomeSeer 2 and found I was disappointed by some limitations in logic and felt too "homebrewed" for me. For some events I want to see, I use a logger written on the ISY.

There are several threads on this back about a year ago. People blamed it on google but I never used google anything. My ISP doesn't even accept a password on a tight input channel from me but it stopped working without a domain that matches the other field with a domain in it. I changed everything to match and it started working again. AFAIC this was all ISY upgrades in security and nothing to do with ISPs or google.

My admin console has started hanging again with the greyed out icons to indicate it quite frequently again. This didn't happen for months and suddenly can happen from the first second to hours after I boot it now. I run Win 7 and 10 with ISY v5.0.4. It is very annoying at times but has been ahppenning since v4

I didn't know there was a log in ISY for the first year and a half. What do I need a log for when every device has status on it's own page and the device summary shows them all at a glance. If you want to see HA process traffic, display the Event Viewer on your same page.

Keypad lights only work from scenes.

This is good news. I wasn't successful with this in previous attempts. They seem to snoop my stats from my google account everytime. I had to use a virgin computer with no registered accounts at all to make it work.

What is your latest firmware? Does your UI and firmware version match? What OS are you running the Admin Console on?

I use the sms conversion link my mobile phone provider provides. Some time back things changed and I now have to make domain names match and accounts match in the field parameters.

Do a search for email to SMS conversion services. Most of them are open for anybody's use.

If you can control ISY from whatever then ISY can control all it's paraphernalia. I like to keep it as the central clearing house for the control and logic I can get. However most stats come with a free cloud service that can sidetrack the control should your ISY, router or whatever gadget fail. Usually, in that case other equipment won't be accessible either, anyway.

Not the same boat. Portal is a "hook" that can make another computer, particularly a RPi, into an extension of the ISY. This is like running dual CPU system connected by Ethernet. The Network Module allows you to send out Ethernet packettes in almost any protocol you will find, allowing you to inject into Philips Hue, MiLight bridges thermostats, etc.. No feedback is possible so it's a one way interface feature. EDIT: My comments were based on the Android MobiLinc that works differently, but lacks a lot of features of the iVersion and doesn't use any Portal for ISY.

V5.0.4 is the latest but in alpha. Some bugs but mainly GUI stuff, like statuses missing on devices pages, screen only and some too big for screens etc.. No program bugs I have found. Find the developer's forum in the UDI forum. There is a thread labelled V5 with the usual instructions. Backup...backup...backup. If you have severe problems you can go back and no one will ever know you were there. Make sure your password is more than 8 characters???? first! You will need the Network Module to write to files as if they are SMS or emails. If you have a programming/hacker background you won't be bothered by any quirks found. If you have little experience you should probably wait for v5.0.5 but it will be alpha or beta, also

And ISY has a lot more.... Taking ISY V5.xx, have a read of this thread. http://forum.universal-devices.com/topic/7269-logging-variables/?hl=%2Blogging+%2Bvariables All code contained on ISY but a browser to interpret and run the script.

IIRC people have reported that the PLM Link count doesn't work properly as Insteon traffic will stop the count process mid-stream.

Just to further the same stat model discussion... I do not have a humidifier on my central air system so I use a floor humidifier, all run for the T7900, via Rpi/NodeLink to the floor model humidifier. The stat controls the setpoint and ISY controls the cycles based on that. ISY also co-ordinates my HRV ventilation system, T7900 stat running the fan, along with the humidifier so that fans are run simultaneously to conserve energy usage. (HRV needs air handler to distribute outside air). ISY can sense how long to run HRV based on outside air being beneficial. ISY also cycles fans when needed based on a time cycle synchronised for the last time they were run, not just a straight timer overlapping heating usage cycles.

I sometimes have a few seconds of delay for confirmation. I expect that going from a mobile phone network, through many bridges to the Internet , through my router conversion, operate the light, Insteon report status back and all the way back again.

"Insteon Hub" is a completely unrelated product???? You can't use both without lots of trouble and understanding to avoid system confusion.

I have two Insteon 2441ZTH units, The older one works both ways perfectly. The newer one reports perfectly but I cannot control it. Most of the problems are not understanding the reporting method. It gives many people problems looking for statuses that ISY can't know yet. I also have two Venstar ColorTouch stats and many 1Wire probes and CAO Tags. I like the CAO Tags best. Accurate, stable, and can report 25 different ways, but cloud dependant for allowing operation, despite local operation.

Not complete. The MS will have at least three links to PLM/ISY. There is a Light/Dark link, a Motion Link, and a few others.

MS units are notorious for having really strange things happen if not Factory Rest before linking to ISY. I have ten MS units and half of them dod things that shouldn't be possible until factory reset and then restored with proper links from ISY. I recommend you do this by removing the battery for ten seconds, reconnecting while you hold the linking button down, until it totally stops buzzing. Tap the link button twice to take out of Linking mode. Now put the MS back into linking mode and right click on the MS in the device tree and select restore. Back to normal mode again. After that tap the linking button several times and watch your ISY status page. Doing this you can send alternating On and Off signals to test the pathway to the status indication.After that the rest is programming.