Michel Kohanim

Hi Fred, It's not a rabbit hole. Just trying to see what the event viewer shows. With kind regards, Michel

@maxnorth, Apologies, it's gen.mosquitto.ud This is a plain mqtt broker. There are no documentations above and beyond those you can get from: man mosquitto With kind regards, Michel

Hi John, Based on what you are saying, I think it's signal/noise related. i.e. ISY retries 3 times during which time GH times out. The next experiment: 1. Open Event Viewer, change the Level to 3 2. Issue the commands again 3. What do you see in the Event Viewer? With kind regards, Michel

@Lore, Is it just the Hue or other node servers too? Also, does it come back on its own? With kind regards, Michel

@johnstonf, What's common between these devices? For instance, are they all dimmers or switches? What if you create a program that controls these devices and then call the program (using a differnet name). Does this work? With kind regards, Michel

@maxnorth, If you have the latest version of isy/udx, then the generic mqtt already comes with it and gets started automatically. It's called mosquitto.gen (as in generic) You can do whatever you want to configure it. You can also start/stop it using: sudo service mosquitto.gen start/stop/restart With kind regards, Michel

@737simguy, What error do you get? We have tested these units and they should work. With kind regards, Michel

@Irakandjii, We do not have any tickets from you. With kind regards, Michel

@DualBandAid, No. Please respond to the ticket. With kind regards, Michel

Here? Regarding the name change, with increasing demand for eisy and integrations with other things, I just got tired of explaining what a node server is. So, apologies for the change. With kind regards, Michel

@DualBandAid, It's best to submit a ticket. With kind regards, Michel

I followed up with one more email and then submitted an official request through their website, alas I have not heard back. With kind regards, Michel

@RichTJ99, Did you remove the above 3 lines from your program????? With kind regards, Michel

ISY can handle 100s of events per second. So, that's not the issue. Scene support in HA depends on the integration and not HA. So, that's not the issue either. Based on the programs, there are only 3 lines that "may" contribute to the delay. And that's the network resources lines. With kind regards, Michel

Hi @RichTJ99, Please remove the above 3 lines and retry. With kind regards, Michel

Hello all, We did send an emai to MyQ developer/integrator mailbox 10 days ago but haven't heard back. With kind regards, Michel

@Pmool, If 2nd and 3rd light are blinking simultaneously, please be patient. The unit is upgrading itself and it might take up to 1 hour. With kind regards, Michel

@Goose66, The issue is that, once setup, IoX would need to be able to communicate with those devices. So, commissioning has to be done at both ends. For the most part, Matter use Zigbee cluster library for app layer communications. So, that's really not an issue. With kind regards, Michel

@nadler, I want to say today alas we currently have too many bugs mostly related to how commissioning works. For most Matter devices, commissioning is done via Bluetooth Low Energy (BLE) which then sets up the device for communications either through WiFi or Zigbee. The library for BLE GATT server is mostly Linux based and thus the delay. This is our top priority. With kind regards, Michel

@gschoffstall, 1. You can return the ZMatter USB dongle within 30 days, so you are not stuck with it. 2. You can install plugins/node servers (Hue) and they show up as nodes just like INSTEON devices. Here are the instructions: - Go to PG3 Dashboard (Admin Console | Node Servers | PG3 Dashboard) - Follow the instructions here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#NodeServer_Store_Menu. In short, go to the store, find the Hue plugin, click on the Install button, and the follow the instructions on the screen to link it to your Hue Hub. I am assuming that you already know how 994 programming works. But, in case you don't and want to start from scratch, you need to start from our Wiki. Or you can read the Cookbook. We would be delighted to answer specific questions via Tickets, alas we do not have the resources for soup-to-nuts education. Apologies. With kind regards, Michel

Which? With kind regards, Michel

@PGannon, As I mentioned in the ticket, the first thing you should try is to move the PLM to a different outlet. With kind regards, Michel

@gschoffstall, Perhaps this will help: https://docs.isy.io | click on Some Definitions. With kind regards, Michel

@larryllix, The reason the links goes nowhere is because you are on a firmware from more than a 1 year ago. Most probably, you are still on PG3 (or PG2) neither of which are maintained. We are on PG3x with major improvements. Regarding NRs, the whole purpose of plugins/node servers is to make NRs less relevant. What exactly do you use these NRs for? If you wish, I can do a remote session and see whether it's possible to upgrade your OS and everything else. But, I definitely don't want to force you to do anything you don't want to. With kind regards, Michel

@larryllix, Do you know what version OS you have (https://polisy.local:8443/desc). There are many bug fixes and enhancements especially for Z-Wave/Zigbee and node server communications + stability. With kind regards, Michel