Jump to content

Home Assistant and ISY Portal Node


pjjameso

Recommended Posts

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.

Link to comment

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

Link to comment

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

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

Link to comment

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..

Link to comment
  • 1 month later...

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...