farcouet

Hello, I finally went with Home Assistant. That works perfectly fine and so much better than few years ago! In fact I am migrating everything out of HomeBridge to go with Home Assistant as it can do so much more. I tried it few years ago and it was quite painful but now wow! And it seems to work really well with the EISY so far! Cheers!

Hello, For the support I opened the ticket and updated it but still waiting since more than a week after my last update (I have checked to see if there was any update and checking from time to time). For Homebridge this is true that there is not much update since a while. I was thinking that it will be just a matter of updating the port number (as it changed) and that the API would be the same. So I guess that somewhere when a new firmware was released the REST API might have changed. I am not sure if it's only the URL. Thanks for the reply and you are right I have sent the URL seen from my logs and not the URL @MrBill sent so my fault. With the result it really seems that the URL changed. So I guess that I will have no choice to look into the Home Assistant. I just really like the Homebridge because there are few integration available but I can also run both. Here's the result. <Subscriptions> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> </Subscriptions> Thanks, Fred

Hello, I have been able to specify the specific port so it connects. It's more like if the REST API is not working anymore. I did not planned to go with Home Assistant because I have multiple other integration done with Home Bridge and it works very well. Is Home Asssitant using the same rest api? Because even if I try manually I get an error so I am thinking there might be something missing on mine (when I got it there was some issue updating the packages as I was getting a message every time to upgrade packages even if I left the ESIY up few hours). I am trying to get some support from Universal devices but I don't know how to get a response. I opened a ticket almost 3 weeks ago and to get a reply it takes a week. I also emailed and my last reply is 10 days ago. So how do people contact support normally? Cheers, Fred

Hello, So has anyone integrated the EISY with Homebridge? It seems that files are missing on mine. Thanks, Fred

Yes I have the proper IP address and port so that is good. I tried first with https and get an error like this. Initially I was prompted to authenticate. Seems like something is missing. This XML file does not appear to have any style information associated with it. The document tree is shown below. <RestResponse succeeded="false"> <status>426</status> </RestResponse> And if I try with ws instead of https: The webpage at ws://192.168.12.31:8443/rest/subscribe might be temporarily down or it may have moved permanently to a new web address. ERR_UNKNOWN_URL_SCHEME

Hello, I searched for Homebridge and have not found anything on the forum before so hopefully it's new topic. I had the ISY994 from which I migrated. I had the ISY integrated with Homebridge plugin https://github.com/pradeepmouli/homebridge-isy-js and everything was working. After the migration I changed the port on the homebridge plugin (because for a unknown reason the option is greyed out in the Eisy configuration) and I am still not able to get this to work with the Eisy. The number of accessories is 41 but this is probably cached from when it was working with ISY. I think that the URL is not valid / working anymore in EISY. Anyone has integrated with Homebdrige with the EISY? Cheers, Fred [2/16/2023, 7:57:04 AM] [isy-nodejs] Error initializing ISY: {} [2/16/2023, 7:57:04 AM] [isy-nodejs] Connecting to: ws://192.168.12.31:8443/rest/subscribe [2/16/2023, 7:57:04 AM] [ISY] Accessories to configure: 41 [2/16/2023, 7:57:04 AM] [ISY] ISY has 0 devices and 0 scenes [2/16/2023, 7:57:04 AM] [ISY] Filtered device list has: 0 devices [2/16/2023, 7:57:04 AM] [ISY] ISY API Initialized [2/16/2023, 7:57:04 AM] [ISY] Homebridge API Version 2.7 [2/16/2023, 7:57:04 AM] [ISY] Homebridge Server Version 1.6.0 [2/16/2023, 7:57:04 AM] [ISY] ISY Host Address 192.168.12.31:8443 [2/16/2023, 7:57:04 AM] [ISY] ISY Model undefined [2/16/2023, 7:57:04 AM] [ISY] ISY Firmware Version undefined [2/16/2023, 7:57:04 AM] [ISY] Total Accessories: 41 [2/16/2023, 7:57:04 AM] [ISY] Total Accessories Identified: 0 [2/16/2023, 7:57:04 AM] [ISY] Accessories to Register: 0 [2/16/2023, 7:57:04 AM] [ISY] Orphan Accessories: 41 [2/16/2023, 7:57:05 AM] [ISY] platform config saved to : /var/lib/homebridge/effectiveConfig.json

Hi, I would suggest to reconsider that software. Support is terrible! First I bought their software for Windows and it was showing and "out of bound" error every time it was starting (that was in Septembre 2011). I sent them and email on October 2011. Never got any reply. Yesterday the software was running in demo mode (even if I paid)! I contacted them asking for a fix specially that I felt ripped off (even if cheap)... So they could not accept the fact that a customer can be unhappy when they don't get any reply... Then they refused to provide support! They even lied saying I have not sent any email... So think about going with a company with that kind of support! Terrible!!!! Fred ---- Answer received: Dear Frederic, We did not receive a prior email from you. The first email we received from you was the one we replied. I understand your system does not supported by the app, which is unfortunate. However, we will not send you a fix for the issue because of your attitude. You don't get to yell us because you are not satisfied with the product. We rather not have you as a customer. We refuse to service you and we have refunded your 99 cents. We will not reply to your further emails. This conversation is over. Best, Ozan Eren Bilgen