MrBill

@JimTurnerThe blue LED is hard to identify if it is unlit without using the flashlight on your phone. A better method: If your ISY has a z-wave board, you will have a z-wave menu at the top of the Admin Console. Check the Z-Wave Version: 4.55.00 = 300 series, the last firmware version compatible is 5.0.16C 6.81.00 = 500 Series, proceed directly to firmware v5.3.4

I believe he will get the license for the balance of the term. Under those instructions you are essentially adding a user, verifying that they can log in, then deleting yourself as an account user. Since they won't be around for there "check if they can log in step" you might just want to create a generic gmail account to add. then you can give the the gmail account, as well as the portal account. That is give the the login information for both the new gmail you created and the portal account it logs into. make both passwords something like Change!Me2 (avoid using 1 as the number because some people can't figure out the difference between 1 and lower case l.

Have you followed the server side instructions? Does an error end up in the ISY error log before the crash? Have you had smtp.office365.com working with the ISY before? Microsoft requires some extra steps to use the outgoing mail server.

spin up a Home Assistant instance and add both the Universal-Devices ISY994 integration and the Homebridge Integration and you're done.

It's really too bad this old thread got bumped, especially since the original post and top of the thread contains incorrect information. I've been using MyQ since 2013 (longer than I've owned an ISY) without issues or monthly cost. The system also works locally without the cloud servers, local buttons, in-vehicle remotes, and outdoor keypads are all local only. The cloud servers only come into play using when using your phone as a remote and/or if you have a home automation system, or subscribe to one of Chamberlain's partners. (Back around 2016 they attempted to charge monthly for some of those connections, the experiment failed and since MyQ only includes integrations from partners with an agreement-- we can only assume that value is exchanged with those agreements, but we don't know if the partner pays in cash or value-added equivalents.) I've found the cloud service to be extremely reliable with 99.9% or better uptime. Chamberlain's API is not published and they don't consider it open. It's been reverse engineered many times for use with every home automation platform, for a time Chamberlain seemed to fight such usage because they don't have a "subscription" based API, instead such systems must poll the servers. The added load likely results in significant cost increases to support the MyQ cloud. NOTE: The use of the word "subscription" two sentences ago has nothing to do the user paying money, in this case the client/server definition applies-- meaning the "client" subscribes to updates from the "server"-- in such systems the "client" doesn't need to poll the "server" every X seconds.

Restart the node server involved. If that doesn't solve it, you'll need to open a ticket so that they can see what's wrong with your cloud instance. support@universal-devices.com

this does work! I think the last time I tried I was too new to HA and didn't yaml very well! thanks for making me revisit it.

There is no "control" equivalent in HA. You can of course use status of a "switch". Or you can set a variable (integer is fine for this, don't use state) via an ISY program and use the variable as a trigger for an HA automation. In the HACS store there is an AppDaemon titled "ISY994 Buttons" that enables "control" type functionality for KPL buttons, not sure if it works for 2477D or 2477S. Note before installing "ISY994 Buttons" from the HACS store you need to visit the Supervisor tab and the main "add-on store" and add "AppDaemon 4" after that install ISY994 from the HACS store. (and YES, at HA they do make add-in, add-ons and "stores" very confusing....)

Yes. With that tight of screenshot I can't tell what controllers you have. but I think your issue is likely what we just discussed the root level, and all Red controller nodes. Also remember that for an ALL On or All Off scene where the switches also are in another scene, that you need to add all node... for Example if Location 1/Button A is the switch that controls the load, and Location 2 button C is the other end of the 3-way Button G on both is All On then you need to have button location 1 A and location 2 C both included in your all on. As far as what happens when all on is pressed you must set the Root level (which is what happens when the ISY sends a scene On, or by Extension also Alexa, Google home, or any remote software), THEN you must also click EACH red controller link and set what happens when an ON is sent from that location. When you make screenshots of scene's please include the tree at the left, so we can see what node you're looking at.

yes.

great noise source, can you turn it off, disconnect it or unplug it? for testing.

How does it interface with the ISY?

From Home Assistant there are many solutions. You could use Custom Devices created with ISY Programs, However i would probably write this program on the ISY side Program RemoteGarageLightOverride If (none) then Set Set GarageLightScene on Disable Program GarageLightOn Disable Program GarageLightOff Enable Program CancelOverride Else Set Set GarageLightScene off Disable Program GarageLightOn Disable Program GarageLightOff Enable Program CancelOverride Then create two button cards one to run_then and one to run_else type: grid cards: - type: button name: Garage Light Override On icon: mdi:lightbulb tap_action: action: call-service service: isy994.send_program_command service_data: command: run_then name: RemoteGarageLightOverride isy: ISY target: {} - type: button name: Garage Light Override Off icon: mdi:lightbulb tap_action: action: call-service service: isy994.send_program_command service_data: command: run_else name: RemoteGarageLightOverride isy: ISY target: {} Into that same grid I'd add button for the switch.garagelight to show the status. You could also change tap_action: to hold_action: if you want to make the button slightly harder to press or even add confirmation: with a text: field below it. There's also a way to do this with a single button card except it would also require an HACS add-in called Lovelace State-Switch which I use alot. with custom buttons for the ISY.

I use a single state variable to called "sAway", it has 5 possible values -1 Home mode, geofence disabled 0 Home mode, geofence enabled 1 Away mode, geofence enabled 2 Away mode, geofence disabled 3 Vacation mode, geofence disabled Essentially using the portal nodeserver this variable mostly automatically changes between 0 and 1, that is If both mine and my wifes phone has left the geofence away mode is automatically set, when the first one of us returns home mode is set. I have a selector in home assistant to set the other modes., -1 has never been used outside of testing purposes, but its purpose is example: out of town relative visiting that stayed home when we went out, etc., likewise for 2 its been mostly used for testing, setting away mode without leaving. Away mode turns off things like inside accent lighting during the daylight hours, and hot water recirculation skips cycles. Evening lighting is the same in away mode for lights that are normally timed everyday. Just remember instead of using = in the if statement to use >= 1 for away mode, or <= 0 for home mode. mode 3, vacation, does all the same things but also adds "random" lighting, like someone going to the bathroom, someone going to the garage for a minute on random evenings. Or someone up late reading. I've even got a random "opps wrong switch" that turns on back yard flood lights for 10 seconds at a random time on a random day. These are just a few examples of about 40 or so "randomness" programs. Away mode also randomizes "bedtime" for the regular evening lighting. Literally all of these "random" vacation lighting programs are contained in a folder with a folder condition... if $sAway = 3 A couple of tips for generating Randomness: you can set variables to a random value, you can also set a variable to [Current day of week], 0=monday, 6=sunday-- I add 1 to this to make it easier to used with random numbers. for a couple of items that I want to occur on multiple random days, I use random numbers that are generated once a week between 1 and 127 to determine days, the math is too confusing to explain in a forum post... but if you understand binary numbers then 1 to 127 is 7 bits, one bit for each day of the week. Another tip for random waits: the wait statement does have a random checkbox that will say turn a wait 10 min into a random wait of 1 to 10 minutes. If you desire a wait between 40 and 50 minutes, then use two waits in a row in the porgram, wait 40 min without random checked followed by a wait 10 min with the random box checked.

depends on the remote platform. From UD mobil you could just add a button to favorites that run the Then block of Program ManualOverrideStayOn. the problem is that would work anytime. Can probably be more help if you say what you're using for the remote platform... I've had them all.. mobilinc, ekeypad, agave, Home Assistant and UD mobile is what I currently use.

That is exactly what this does. The only time "Program ManualOverrideStayOn" becomes enabled is during the 5 minutes timer, otherwise it's disabled. That is not true. Program GarageLightOff If GarageSensor1 status is off <<<---When both doors close. AND GarageSensor1 status is off then Enable Program ManualOverrideStayOn <---- Start listening for someone to hit the switch to On Wait 5 Minutes Set GarageLightScene off <---- If the timer times out turn the light off. Disable Program ManualOverrideStayOn <---quit listening for someone to hit the switch Program ManualOverrideStayOn (disabled) <-- becomes enabled only during the 5 minute timer period If Switch1 is switched on (Control menu, not status) <-- when enabled during the delay someone can press the switch ON or Switch2 is switched on or Switch3 is switched on or Switch4 is switched on then Disable Program GarageLightOn <--the light is already don't listen for door opens Disable Program GarageLightOff <--- the light is on in override and we don't want to restart the timer at this point Enable Program CancelOverride <--- Starts listening for the light to be turned off via switch, at which time the light will go off and normal opartion of the automation will resume because that program runs That is not Correct. the switch can be on and "Control" is switched on, DOES send an ON that the ISY will see and cause the program to run. When "Control" is used it doesn't matter if the light is already on. Use a program like this to test for yourself: aaa Test - [ID 00E6][Parent 0001] If 'Kitchen Recessed#' is switched On Then $stemp_test += 1 Else - No Actions - (To add one, press 'Action') the variable will increment each time you press the up paddle regardless of the state of the switch. Check the programs again... they do EXACTLY what you asked for, and are very similar to what I use in my own garage, the biggest differnce is my lights will turn off anytime they are on, but will on turn on via automation during the period Sunset to Sunrise (next day). (We don't need light during the day because the overhead doors have frosted glass windows for natural light.)

Those are fairly standard "errors" to follow boot. Boot as you noted is "System -5 Start" and then there will always be errors in the next few minutes including the Queue Full messages, then the system will quiet down. Here's my yesterday: Sat 2021/07/31 05:25:25 AM System -50001 -5 Sat 2021/07/31 05:25:28 AM System -50001 -5 Sat 2021/07/31 07:19:33 AM System -100 [DHCP] state=RENEW Sat 2021/07/31 08:22:13 AM System -5006 uuid:233 Sat 2021/07/31 08:22:23 AM System -5012 233 Sat 2021/07/31 10:39:36 AM System -140005 Net Module Rule: 33 Sat 2021/07/31 10:39:44 AM System -50001 -6 Sat 2021/07/31 11:52:43 AM System -170001 [UDSockets] Net Module Rul:43 error:6 Sat 2021/07/31 06:21:16 PM System -100 [DHCP] state=RENEW Sun 2021/08/01 04:59:20 AM System -100 [DHCP] state=RENEW Sun 2021/08/01 05:58:56 AM System -5012 238 Sun 2021/08/01 06:09:36 AM System -5012 237 Sun 2021/08/01 06:19:13 AM System -60006 n/a which is pretty standard. In additon to what you can learn from the wiki the "net module Rule" numbers equal Network Resource table numbers. On the other hand if I back up to last Tueday there are about 3000 lines for that day, I know the cause was the comcastic company kept dropping my internet and my router kept switch back and forth to my backup connection. Another way to test portal connectivity failure is to unplug network cables, like router to modem or modem to outside world, so that the ISY still sees ethernet.

Check Tools > Error Log. The cryptic wiki page to help decode some of the errors is here: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages&redirect=no If that doesn't help and you have an active error log you might want to clear it and then restart the ISY so that the log is small. then either post part or send it into UDI via a support ticket support@universal-devices.net It's normal to have a few errors, my system is large and complicated, typically i'll have 6-12 error log lines a day, when it exceeds that, its usually by 100's of lines, thats the type of error log that you need to start understanding what's wrong.

Two points to help you better understand scenes. The settings are for the "on" version of the scene. sending an scene an "off" turns the scene off. And this trips everyone up at least once with v5.x scenes: The scene that your working with here has 4 controller nodes... The root level of the scene, and the motion and the two red controller nodes. ALL 4 NEED TO BE CONFIGURED. Each controller node can do something different for "on". So if you had a scene with 3 doorway's each with a switch, you could program different "on" commands for each door, additionally the root level is configuration is what happens when the ISY itself controls the scene with an "on" command.

I think you need to move one line up and change the action for button.h to ON

Thanks!

Hi @Javi Got it! I haven't added my ISY on Polisy instance to UD mobile yet, is the note in reference to a version beyond 5.0.3?

Javi, You included a note in test flight release 0.3.7 that is confusing me. @Chris Jahn did post a new firmware release 5.3.4 on 7/30/21 but the only fix it seems to contain seems to be unrelated: Is this the same thing or different?

I get it now... are there plans to create remote access to polyglot via the portal?

I don't actually know, I don't understand default, and I don't have any motion sensors. Prior thread: