brians

I just tried and both cloud and lan work for me on Polisy.

What is a jail?

Reasons I had to exclude/include with IoX. - their zwave implementation is currently beta and often may have issues but I believe is better now. - no OTA - must exclude and do firmware upgrade elsewhere then include - in case or Zen17 you must exclude and include after setting certain parameters to enable feature - reinterview did not work. Since the the name in IoX based on the ZWave node ID, unfortunately have to edit programs and scenes whenever exclude include.

I can't remember how DSC worked in IoX but I did have all the zones able to by bypassed using toggle in UD Mobile so I am sure this is possible somehow. Do you have to use scene to send a bypass command? If you say you cannot delay in a scene, then just use three scenes with only one zone in each, with a delay in between running each one! I think the bypass on DSC is a toggle, not a discrete on/off. In Alexa I think you can set it to turn on a variable which triggers a program using a custom phrase... I did this years ago so cannot remember exactly but it wasn't that difficult.

Note that the enable web page doesn't provide any visual feedback. After that you just let it sit and hope it completes the upgrade. I did this a week or so ago, I just updated from 3.1.27 to 3.1.29 with no issues.

Home Assistant doesn’t have the issue.

I agree, it not good to have ZWave devices mess up programs each time you exclude/re-include. But I guess at the time Z-Wave was added years ago, it was only way due to limitations of ISY and nodes for everything, probably lack of resources so they just used the ZWave node ID to keep track for programs and scenes. If they did it now, I bet they would make it a nodeserver, where you add the devices there and map them to a node/name yourself which gets sent to IoX. If you exclude/include you just make sure it is using the same node slot name. That is a lot of programs!

I successfully got it talking to MQTT server on my Home Assistant. However, not sure how to get it to control Zigbee devices over zigbee2mqtt I added a switch node based on example and I see it added the cmnd topic in there and, added a device/node in IoX. I could see it turning on/off using MQTT Explorer when I pressed the buttons in IoX. However, this seems to be instructions for tasmota devices which use cmnd topic. I wonder if it can control zigbee2mqtt? I messed around a bit and no luck. Wondering if anyone has tried this, or is it even possible? This would be a way to get Zigbee devices into IoX by setting up zigbee2mqtt and a USB coordinator on another server. I also noticed that when I deleted my test device in MQTT nodeserver, it did not delete it in IoX.

Both LAN and Cloud work for me.

Can't you just change the setting in /etc/rc.conf, resolv.conf ?

I just logged into mine and is fine... in fact seems a bit faster than previous version. I am also using a Polisy. Maybe it is doing a query and hung on something... try to disable query on restart and see if that resolves.

I updated mine, got no notification other than some xml parse error but could have been something else. I reconnected, after updating start.jnpl and clearing cache etc. because it was complaining I had an old version... Once I connected I got message that it was updated and requires reboot. Everything is fine now, no issues...

I don’t mention ISY, but rather EISY. The old plug-in which was referenced happens to have isy in name. Homebridge is backwards to how a nodeserver would operate. They could still add it in the same PG3x interface anyway for lack of somewhere else to place.

@SSS the HACS version of the ISY integration for Home Assistant supports node servers a lot better. Maybe setup a HA box, install that and give a try, and give feedback to the developer... go check it out by looking in the Home Assistant forum, I just seen this. Once in Home Assistant, you can use the built-in HomeKit Bridge to being the entities you want over into HomeKit and should work with RR

Michel said earlier in this thread (look up above) that they are investigating using Homebridge inside EISY so they must have some sort of plan/discussion about it if they actually go ahead with this. It would be nice if they would do some sort of support for the integration as well to make sure it works bit better, and stays working, otherwise what is the point of adding Homebridge to EISY then?

The current HomeBridge plugin which seems to be the best is still called Homebridge Isy Js. I am sure it could be renamed with something IoX in it for clarification. This is nothing to do with them updating the ISY994i. Michel said they are investigating using Homebridge inside EISY and did not mention a nodeserver.. not sure why they would take the time to do that when Homebridge already has a UI and they just need to fix up the Isy, (or "Iox") plugin.

What version of ISY integration do you use with Homebridge? The rodtoll one I was using for many years (not developed anymore, and the pradeep one broke pretty much everything on it for me, no longer developed also), until earlier this year, had issues with many zwave device (mentioned elsewhere here). If UD is going to make make Homebridge work on EISY, I wonder if they will be updating/supporting the Homebridge ISY plugin and bringing it up to date.

HomeKit users already are in the HomeKit ecosystem and most likely use the built in Home App. Roomie Remote is mainly an AV remote control with added on HomeKit control which took probably minimal effort since its built into iOS anyways. What my point is, most HomeKit users probably don't have any Insteon or any reason to use EISY and probably just built their HK system around things that work... but if you have older legacy hardware and need an IoX to run Insteon, then that is an issue. (I accidentally deleted part of my previous post above so SSS response didn't make sense reading it by itself, but what I was asking SSS is to tell me why HomeKit user would want an EISY... and answer is RR )

The issue with the HomeBridge ISY plugins is that the are very old and do not work with newer devices in IoX such as Z-Wave binary switches - eg. a Zen32 or a Zen51 would not show up in HomeKit with HomeBridge. I would hope someone fixes it to make work better if gets installed in EISY. Hubitat has HomeKit support, not sure how they could afford it but maybe they sell lots?!? Or maybe that is why it is in Beta.

Ahh yes that worked! Seems to be an issue with Notification server... msg saying can't add in free edition... messed around with it a bit, but still it seemed it needed pushover api key which I didn't bother researching. UD Mobile seemed to sorta work sending a test notification... even though I am sure I could get it all working I removed since I no longer use. My one remaining Nodeserver works perfect now however

Yes thanks, I guess would be too difficult for them to display something on screen Wonder how long it takes, still got this going on after about 20 min...

That link has this error... This XML file does not appear to have any style information associated with it. The document tree is shown below.

You can still add all those nodeservers into eisy and if you make a change using RR it should update and reflect in Eisy and vice versa so you can still automate using iox if all your things are added into it also. This sounds like what you are currently doing and should be fine Curious what you use hoobs for anyways - are you using that old isy Homebridge? Do you have lots of Insteon ?

Roomie remote looks like it’s primarily a media av control remote software and they just added on some other abilities over time like home automation control. They don’t even seem to support home assistant which is very popular. From reading your posts I see you are trying ecobee, hue, and myq. All these support native homekit (myq with HomeKit adapter or hoobs) so what is issue with these and roomie, since you say HomeKit devices automatically appear in roomie? Is there some reason you need to have everything go through eisy for roomie remote?

Hue version of Zigbee on their bulbs is compatible with pretty much all Zigbee coordinators... it is their hub that doesn't work with other Zigbee devices. I run several Hue on my Home Assistant direct to my Sonoff USB Zigbee coordinator using Zigbee2MQTT (ZHA also works). Advantage of Hub is you can use the Hue app and make fancier scenes and stuff... newer Hue bulbs support bluetooth but I don't think has advanced features in the app, and probably limitation of range. I don't use Hue Hub, I just want to change lights different colours and have option to add different devices... there are much cheaper bulbs which are not so bad -I also have like Sengled zigbee about 1/3 the cost. LIFX are WiFi and I don't recommend, but I have a few older ones of those that I use still. The issue people will have with pairing a Zigbee RGB bulb to IoX with ZMatter via Zigbee/Matter is how to change colors easily? Does UD Mobile support color picker/wheel?