dbwarner5

@Goose66 is this all that is needed to get it running and nodes showing in the AC? I guess it would be good to get someone to do a quick simple bullet point of hte steps for those of us that dont know / understand or have ever worked with the MQTT side of things. thanks

Was running 5.7.1.1. Just upgrade by pressing Upgrade packages. Usual message of four beeps (got six), eventually asked to reboot by pressing the reboot button in AC. Reboot just completed. All is perfect 5.7.1.7....Thanks @Michel Kohanim and UDI!

From goose above, it looks like you would set the ratgdo MQTT IP as follows: If your are using the public MQTT broker on Polisy/eISY, it is the local IP address or hostname of your Polisy/eISY and port 1334

I have the same need but havent tried to address it yet. The simple question @Javi is, if I have a geofence set up in UDM on my phone and also set one up on my wife's phone which starts from the same backup, will these be considered two different geofences? My guess is yes if I name them differently, then I can accomplish the above, but to your point if I replace her version with an updated backup on mine, it will replace her geofence with mine and wipe hers out since it wont exist on my phone. Currently I have been using Alexa's geofence to trigger a vairable in ISY and was going to do that for my wife's phone as I know those would be separate.

forgot to mention, that under the Configure tab of that icon, I have set the following. This makes it green. I have all my favorites display green if they are in the state I like them in, and red if not. Also for the colors, they have to be inputed currently in ASCI format. here a web site with the codes: https://www.ascii-code.com/html-color-names

very easy.. set up your Favorites screen in UD Mobile. Here is my main page with my ELK security system highlighted on top. If I click on it I can adjust it anyway I want.. The second shot is the setup of that icon.

Thanks @Goose66. Am not familiar with the MQTT broker on Polisy, or what it even means. How does that connection take place? Do I need special knowledge to set that up within the Polisy? Thanks.

Goose, can you clarify that I understand this correctly: Ratdgo hardwired to GDO, and then configured to connect to Pollisy over LAN which needs to have the MQTT plugin running and then the MQTT plug in will report the Ratdgo nodes in the ISY? Thanks. By the way , according to the developer, RATDGO stands for Rage Against the Garage Door Opener. Brilliant!!!

probably has battery sensors that after reboot report a blank until their state is changed.

this is exactly how I do it for three doors.. wired sensors to elk for door closed sensor and elk output to an extra remote, soldered to provide the closed contact as controlled by ISY.Works well, but not at well as the myQ NS did. Challenge for me is at a pole barn where I dont have elk wires and insteon signal is not always dependable, z-wave too far away but I do have wifi so may explore other options that are wifi related.

has anyone tried this? looks like it has broad compatibility.. I have their light switches in a second home connected to smartthings / Alexa.. for an ISY install, it would be controlled through Alexa then ISY. https://www.amazon.com/meross-Compatible-Assistant-SmartThings-Notification/dp/B084Z5QZR2/ref=sr_1_3?keywords=meross%2Bgarage%2Bopener&qid=1700526837&sr=8-3&th=1

I am not sure on that particular device and which to choose for Alexa.. A simpler method may be to write a program to do what you want with your security system and then make that a spoken to Alexa so that when you say turn on "House security" it runs the program Then statement.. no IF statement needed. this is how I do a lot of Alexa related things.. Where I may have complex programs in ISY, I will have a simple one that is only for Alexa to initiate the complex programs. In this manner you can keep things really simple between the two interfaces. Here is an example for controlling my awning.

easiest way is to simply create a routine in Alexa with the trigger being voice "open living room blinds" which then turns the isy device on.

@Khouse I you simply changed the spoken in the portal in question #2, then you need to go to the Alex app, find that spoke / device and delete the old one. Since that spoken is still in the Alexa app, the only way to get it to go away is to delete it. Changing it in the portal wont do that nor will discover new devices. As for point #1, I have never had that problem as long as I follow these steps, in order and hit save after each one. -go to portal as shown above, - create your link by selecting the ISY device / scene or program etc -Add the spoken or multiple spokens (each one will show up as a separate device in Alexa) -When done, be sure hit save and back all the way out of the portal to the main screen -Ask Alexa to discover new devices. Good luck!

Same here ... polisy.

Would be nice to have most of the features available on one screen, but to continue to make them Hideable for users that dont need to see them all etc.. (like spouses ) When I use the app I either get what I want quickly from my favorites or else I am almost only going to one of three things: programs, variables or devices... all the other stuff and any extra steps to get to these three items is just a pain. Thanks!

Same here! Thanks Javi!!!

Am on 1.1.37... all my formatting, which I spent hours on through different screens is now all messed up.. Cells that are two wide, wont let a one wide appear next to it. so everything is now offset and pushed down. I hope you un fix whatever has happened.

I have found for my application on my main level that scenes work much faster and more efficient. Downside, is you cant easily ask a scene to dim etc. Roughly thirty lights are included in the scenes, insteon, hues and kasa. Scenes include: evening, mood, dim, nightlight, dinner, supper, cooking etc. Alexa is the initiator that either runs the scene directly or in the case of dinner or supper, first plays music and then an ISY program that turns on the right music zone to the right volume (russound NS) and turns on the scene. I do have a few programs to control these for all on / all off, but they are significantly slower to turn all the lights on / off etc. Each light can also be accessed via Alexa separately so if someone desires the island cans to be brighter they can easily do that independent of the preset scenes. The nice thing about this is that while watching tv in an adjoining room, Alexa can trigger programs that set scenes in that room while also dimming the lights in the rest of the area simply by calling one of the above scenes.

@greensha The closest thing to a batch add is to highlight all the devices you want to add to the scene by option (Mac) clicking on them if they are non-contiguous or Shift clicking first and last item if they are contiguous in the list. Then you can add them all at once, but will still have to decide controller / responder and settings for each. Often I find I am creating different scenes with same devices. that makes it very easy once you have the first scene to select all the items in that scene and drag it to the next scene that you have established for it , but which is empty.

So how does the Polisy actually communicate to the Ratdgo? via LAN wifi? Just trying to understand if I installed two in a remote pole barn, how the "link" would work. I have wifi there but too far for zwave etc. thanks.

Its actually pretty easy.. Here is an example where I have the ISY control an Amazon light in my garage: 1) create a variable in ISY: mine is called Garage_light_yellow 2) go to your portal and create an Alexa spoken by selecting: Select Tools / Connectivity / Amazon Echo as shown below 3) Next, create a new Spoken and select type Variable. You should see your variable in the drop down list, and select it. Since I dont want Alexa to ever actually recognize the spoken, I make the spoken a bit of gibberish. Then you can select the variable value you want for that spoken. Below is my example. 4) after saving the above, go to Alexa and ask it to "discover new devices". It should come back with one new device found after a 30-60 second delay. 5) In the Alexa app, set up a routine that looks for this motion as the trigger for your shades. It will look something like this. 6) write your ISY program to change the variable to a 1 when you want that routine to trigger and then back to zero for the next triggering event. Here is mine for this simple example. Garage Party light yellow Summer - [ID 036E][Parent 0207] If $Garage_Party is 1 And $Season is 3 And ( 'Garage Door Middle' Door State is Open Or 'Garage Door North' Door State is Open Or 'Garage Door South' Door State is Open ) Then $Garage_light_yellow = 1 Wait 15 seconds $Garage_light_yellow = 0 Feel free to reach out via DM if you having issues. This is the most simplest form of using ISY to trigger Alexa routines. For shades you may want to use the following syntax instead of a motion sensor as you can have more control of using different variables values in ISY to have alexa run different routines. I dont have any shades so I have never used this feature. Good luck

But if handy, you can connect the I/O to an extra remote such that it closes the appropriate contacts and then mount the remote close enough to operate the doors via the ISY. Monitoring the Door status can be done with many options including insteon open close contacts, Elk contacts or as mentioned the YoLinc contacts. The I/O can be any device that you get to talk to ISY such as insteon I/O, the Zoos I/O etc. This is what I had been using before MyQ for three main garages doors: elk outputs soldered to an extra remote, and elk hardwired open/close sensor. Luckily I held off deleting all of the programing I had for the Elk system when I went to MyQ. Now I test to see if MyQ service is true and if so use that system, if not, use the Elk system. The problem I have is a pole barn where the Insteon signal is questionable for two doors. I have tried insteon I/O to sense the doors but it was always sketchy in accuracy and because it's cold, the batteries drained quickly . I havent done the remote wiring as of yet because MyQ was working so well. Am not sure if the YoLink sensors will travel far enough and using zwave wont work with a zoos because again its too far from the ISY zwave to work. So MyQ was a great solution.

Well that is disappointing.. I. see they still allow IFTTT. May try to figure out this path out and run IFTTT through ISY. Just another winter project.....

I took an extra three button garage door opener remote and soldered wires to each switch and the common and have my ELK outputs via the ISY trigger the buttons. The remote is mounted in my garage. Works reasonably well but needs appropriate timing / delays when opening / closing multiple doors. Still have it as back up to the MyQ app which I prefer because I have two pole barn doors that I cannot do the above to and have only fair ISY communications with so an I/O module which could do the same, would only work sporadically. Currently I had to set up a trigger variable such that if the MyQ service is TRUE, then the ISY will use the system, and if false, it will use the Elk / remote system above.