pjjameso

I can control the ISY with simple control 5 and ISY 5 only in simple control’s home bar. Scenes no longer work nor can I can create buttons to control lights. Believe this is a simple control issue and have raised a ticket with them To be honest I’ve given up on simple control and just moved in the last month to harmony elite. Not as eloquent but at least it works everytime and has a higher waf. At the current rate I don’t think simple control will be around much longer, just doesn’t work consistently. And yes I was one of those idiots that bought their hub looking for more stability, Alexa never worked except for executing the first command which would then lock up the hub requiring a reboot. Do miss the TV guide feature though.

Thanks Stu, have it working using two programs as mentioned above. The real issue is that ISY Portal and Alexa Scenes do NOT talk to one another for use in Alexa routines. Hoping the crew at UDI can address the issue.

Using iOS, to control opening and closing of the curtains. Definitely a bug in the ISY Portal/Alexa interface. Have managed a workaround by using two new programs to trigger the scene. One program then statement to open (turn on the scene) one program to close (turn off the scene). In ISY Portal each program is mapped to a Alexa Device\light category with the spoken word of open curtains and close curtains. These show up in the alexa app as 4 yes four devices/icons. A light, and a house with wifi inside. The house icon's description is the program name eg Family Room Curtains Close (program) with a type of Other. The Light icon description is ISY Program address 0040, type light. From all this I am able to create two routines, Alexa, close curtains; Alexa, open curtains as the spoken phrase. The Alexa will action operates on the Light devices. This works each and everytime to open and close the curtains. Have noticed the light indicator on the keypad does not always follow correctly. Will always turn off correctly but not always turn on. Long and short of the above.... Controlling a scene directly using the ISY Portal combined with Routines does not work, period.

Wow that’s exactly what’s happening with me. Set up Alexa as switch in portal. Can get it to close most of the time but open does nothing. Giving up at this point and reverting to turn on (open) and turn off (close) and not telling the wife about it. Unless the wizards at UDI come up with a solution. Thanks for the sanity check.

There has got to be something a miss in the coding between the ISY Portal and the Alexa App. This is what I am experiencing, In the ISY i have a Scene called Family room curtains which contains a keypad button D In the portal i can select the ISY scene (Family room curtains) and map to an Alexa 'scene' category with spoken name 'curtains'. Alexa app will discover spoken name 'curtain' and list in both the scenes and devices categories. In App 'scenes' settings type is correctly identified as Scene with the correct ISY scene address In App 'devices' settings type is set as 'other', and description is correct as Family Room South Curtain I can voice command to turn on the curtains (open) and turn off (close) When I create a routine and select to control scene, no ISY linked scenes are presented, only my harmony scenes. When I try to create a routine and select control device, the ISY curtain device is presented but an "Alert' message box comes up and says 'This device is not currently supported' and will not let me continue. Should add that I have the family room curtain scene used in a program to open and close each day with sunset and sunrise which is working perfectly. Which rules out that part of the equation. Any help most appreciated.

Okay, making progress... deleted skill v3, deleted all devices and scenes. Now scene comes across and is in Alexa scene tab. Of course when I try to create a routine and and select the curtain scene, NONE of the ISY scenes are presented. Although all show up in both the devices tab and scene tab in the Alexa App. Ugh..

Okay, making progress... deleted skill v3, deleted all devices and scenes. Now scene come across and is in scene tab. Of course when I try to create a routine and and select the curtain scene, NONE of the ISY scenes are presented. Although all show up in both the devices tab and scene tab in the Alexa App. Ugh..

Stu, The issue is that alexa will NOT discover the ISY Portal Scene as a scene in the APP. It always discovers it as Only a device. The ISY Portal shows the ISY Category as a Scene and the Alexa Category as a Scene. But the Alexa app will only recognize as a device.

nope, been using v3 for quite some time. my programs come across as scenes no problem, its just this one true isy scene that i cannot get to come across. Always as a discovered as a device.

Sorry to cross post, but seems to be same topic. For the life of me cannot get Alexa to recognize ISY scene as a scene, always a device. The portal shows isy and Alexa as scene type. Yet Alexa discovers as device each time. Thoughts?

Ok, guess that is my issue. For the life of me cannot get Alexa to recognize as a scene, always a device. The portal shows isy and Alexa as scene type. Yet Alexa discovers as device each time. Thoughts?

Added scene from ISY to portal ISY portal shows Alexa category as device\light Alexa app shows device as curtain Able to execute Alexa turn on or off curtain and ISY executes the scene When trying to creat routine selection of device app says device not currently supported. Thanks for the help in trying to figure this one out.....

Still missing how to do this... I am able to open the curtains via alexa by saying turn off curtains. Curtains are in a scene controlled by keypad D button. When i go to create a routine in alexa app and try to select a device it says ' this device not currently supported'. What step am i missing in the process?

Ummm, does Alexa have the same capability?

Is there a way to have the commands open and close in addition to on off? Use portal to control Curtains and saying turn on Curtains vs close Curtains would help on the wife acceptance factor.

Michel, Any luck with the MIMO2+? On another note will pull out the Fibaro and try to re install and send the results. As mentioned worked great with 4.62, not at all with 5.011b

Unfortunately my curtains require 2 relays.... one to trigger open, one to trigger close, and really a third to have them stop in between but i can live without that one. The motor attaches to a pull cord and contains sensors to tell when fully open or closed, eg no lever setting.

Michel, Any luck with the MIMO2+? Would like to remove the home assistant on rpi asap.

Well good news, all up and running and ISY and Home Assistant with the Aeotec Z Wave Stick are working great. I can press an insteon keypad button and control the zwave device.Gen 5 here we go!. Would still more eloquent when Gen 5 is supported with a new daughter card. But for now I am all set..

Any idea where to find the entity id in the ISY to use in Home Assistant?

Okay think I found the answer and it appears easier than thought. Will let you know how I make out. HANDLING INSTEON CONTROL EVENTS A Home Assistant isy994_control event is emitted for every “control” event in the Insteon network. This allows you to write automations that trigger based on Insteon button presses. You can also trigger off of the unique Insteon events, such as double-presses, long-holds etc. automation: - alias: turn off living room on double tap lightswitch trigger: platform: event event_type: isy994_control event_data: entity_id: light.lr_track_lights_front control: 'DFOF' action: service: light.turn_off entity_id: light.lr_track_lights_rear All isy994_control events will have an entity_id and control parameter in its event_data. You’ll need to refer to ISY994 documentation for the list of every possible control type, but the common ones are: DON: On button DOF: Off button DFON: “Fast On”, usually from double-tapping an On button DFOF: “Fast Off”, usually from double-tapping an Off button FDUP: “Fade Up”, usually while holding down an On button FDDOWN: “Fade Down”, usually while holding down an Off button FDSTOP: “Fade Stop”, when releasing a long-held button BRT: “Brighten”, from controllers that issue a single command to slightly brighten a light DIM: “Dim”, from controllers that issue a single command to slightly dim a light

So I have no clue as to what I’m talking about so bear with me.... On 5.0.11b but still have issues with multi channel zwave devices (MIMO2+) which Michel has kindly indicated he will research. What I am wondering is how one could one go about using Home Assistant to control zwave devices while keeping in sync via isy node server which would allow me to use insteon keypads and programs to control said zwave devices? A bit Rube Goldberg but would solve gen5 zwave device issues till ISY daughter card is available. There are already ISY 994 HA components developed to control devices via the ISY. Figure for 70 bucks it would be worth he effort, just need a bit of direction from someone. Basically I am trying to get control of the two relays on the mimo.

You rock Michel! Thank you so much for debugging the MIMO2+. It will solve a host of issues (automation) for me!

Michel Im on 5.0.11b and FortezZ MIMO2+ ISY only recognizes sensor 1 and relay 1. This is a multichannel device so should be seeing sensor 2 and relay 2 as well. Would be fantastic if you could take a look and see what wrong in the alpha code. Have tried including/excluding multiple times, repairing, syncing etc.

On version 5.0.11b, I have removed by exclusion all the zwave devices, removed leftovers by removing failed nodes, syncronized nodes, healed zwave network. Assume I would be starting from scratch at this point yet when I add new zwave device it starts at a higner number eg ZW 11. Why would it not start at ZW 01?