I understand that da2pi and envisalink do not use zwave to interface to HA. It uses serial communication via usb or sockets or rs-232.
I was referring to using a zwave sensor monitored by HA to trigger the Vista alarm as opposed to adding a new wireless sensor to the Vista system directly.
But yes Im confused if the HA integration for your da2pi doesn’t support triggering the vista alarm, how do you do it with HA?
Which I can do also.
Why do you need a specific “alarm trigger” parameter to set off an alarm?
I can:
create a fake “sensor” in the alarmdecoder config, and have that set off the alarm
or
use any number of automations, that enable the alarm and forcefully set off a sensor to trigger the alarm
I don’t need a specific alarm trigger. I “set off” my alarm based on all sorts of sensors that aren’t connected directly to the alarm system.
Ahhh… that’s your secret for non-vista connected sensors, adding a virtual sensor to vista.
So the triggered z wave real sensor that is monitored by HA in turn triggers the virtual vista sensor which in turn triggers the vista siren and notifies the monitoring service.
Hope I got that right. Thanks!!
if you’re using a monitoring service.
Personally I just go for the ease of turning on the alarm (if it’s already off), and sending a service call to trip one of the existing sensors.
If the alarm is already armed, then the thing that should be triggering the alarm would be the sensor that was set off. 
LOL… one would think.
Thanks… Now I’ m wondering what the envisalink trigger alarm action really does.
You can trigger an alarm without “setting off a sensor” from the alarm. It’s not that special to me.
Got my Envisalink4 installed and running today with my Honeywell Vista-15p security system!! Yippee
Im making such good progress im now thinking of installing hassio on its own partition.
Im using debian for my base os but for no particular reason other than lots of others use it. Do you have a preference i.e. ubuntu or tinydistro or ???
Is there a windows like remote access (rdp) for linux or am i pretty much stuck with ssl terminal and ftp?
Oh man @flamingm0e, I can’t thank you enough for all your patience and help with my hassio install.
The integration with my hassio and my honeywell vista10p is totally working great!!
Ive got some basic cards set up in lovelace and can arm/disarm the system, monitor/set all my zone sensors, and send keyboard commands to do things like bypass zones, turn on test mode, etc.
Today, I’m including you in my bubble of happiness!!!
I use Alpine Linux as my host OS.
I wouldn’t.
A. You don’t need a desktop on your server.
B. You don’t need to be using ftp. You can use samba. Or any number of ways to access and edit the files.
???
If I want to move my hassio+hostos system off of my hyper-v guest, dont i have to move it to partitions on a disk drive or usb stick? (i.e. the ext4 and user and swap partitions)
The way it was worded, it sounded like you were going to try and install hassio in a dual boot setup. Nobody uses the term “install it on its own partition” to indicate you’re going to install it on a dedicated machine.
That s what I meant. dual boot to either windows or hassio with the default being hassio. Is that a problem?
Yeah, you can’t just dual boot hassos. You could dual boot a debian or Ubuntu system, but why would you?
You’re way overcomplicating it.
Oh i wouldnt try hassos, im happy more or less with debian as hostos. my mini pc has plenty of space so dont need imbedded type compactness. But since i have to do a fresh install i thought i might give alpine a try, cause your using it, and i think hassio is too in its docker.
my rationale for dual boot makes sense to me at least. Right now i have a perfectly good working system and dont want to nuke it until i have a properly working replacement for it. Once thats done, ‘then’ i nuke the windows partition. i sort of think of it as a hot backup while im getting the new system up.
You cannot use hassio with Alpine Linux as the Host OS (at least not without a LOT of work) because the install script and all the configuration of HassIO relies on a systemd based OS.
Yes, home assistant docker is running Alpine Linux, as is the Hassio stack, but trust me, if you aren’t good with Linux, and “need” a desktop, Alpine isn’t for you.
Stick with Ubuntu or Debian (my preference is Ubuntu server).
If you back up your config directory (or use snapshots in Hassio), you really have no need for a “hot backup”.
hmmm… now im a little confused cause earlier i thought you said you were using alpine linux as your hostos. does that mean your using the hassos??
either way… im might try ubuntu, cause i think i read somewhere it supports rdp
I am.
No. I do not use HassIO in any form.
Get out of the “RDP” mindset. You DO NOT need a desktop on a server. The desktop is a waste of resources and does nothing for you. RDP is a Microsoft thing. In Linux we have XRDP or VNC.
lol… ok
i enjoy our discussions. thanks
hmmm… that means you are either running HA on your host or HA in your own docker?
Alpine Linux is the host OS. It does nothing but run Docker, which handles my entire home automation docker stack.
I have no use for hassio. I have a docker stack including Home Assistant that works for me, and I require none of the “features” that hassio offers.