Recent content by mantorok

I installed PC Access and was able to get it to communicate with my Omni LTe via both TCP (OmniLink II) and UDP (OmniLink). So UDP seems to be working fine. I'm not sure why I can't programmatically get a response via UDP though. I'm using NodeJS and its "dgram" package which handles UDP comms...

Thanks for that info. I suspect OmniLink II may have been introduced in a late version of 2.X as there's an older version of that document you attached labelled "Rev 2.16". I'm not sure if that number refers to the firmware version or not though. The Rev 3.0 version you attached mentions that...

My understanding is that the OmniLink protocol is used for communicating with the Omni controller via its serial ports (RS-232 & RS-485) and OmniLink II is used to communicate via its ethernet port using TCP. However I’ve also read in this forum that UDP over ethernet is also supported but I can...

That's great news.   I was going to suggest if that works then you can add the zones back one (or a few) as a time to try to determine which zone is causing the issue.  Just start with the lowest number and add them in order as the plugin will request the status of the zones between the lowest...

Hi @highlyAuto,   I had another idea that may help you use the plugin if you don't mind having no zones. In the homebridge folder there will be a subfolder named OmniLinkPlatform and it contains a file named Omni.json. In that file you should see something like: ...,"zones":[...],... Can you...

One thing you can try is remove the name of the thermostats. The plugin ignores objects that have no name (with the exception of Areas).   If I had to guess which zone is causing the issue I'd say it was zone 15 as it's related to the thermostats. Again you could try removing it's name.   As for...

In the SnapLink app did you go into settings and "Retrieve Setup" again? This will sync the app with the current config of the Omni   Likewise for the plugin you'll need to set forceAutoDiscovery to true and restart so that the plugin can retrieve the latest config.   BTW, its not necessarily...

I had a bit of trouble getting PC Access up and running at first but its not that hard when you get the hang of it. You first create the account file and then connect to the Omni controller which should load your config into that account file. I think the rough steps were:   1. Start PC Access...

I see you're getting quite a number of TCP connection errors. This is what I think is happening but could be wrong:   When the plugin attempts to request the status of the zones the Omni controller generates a fault and restarts. This will drop the connection to the plugin. The plugin detects...

Hi @highlyAuto, could you please attach an updated log file. Ensure showOmniEvents, showRequestResponse are set to true. I just need the logs from the first time you get the timeout.   Also can you capture the log when you try to control the bulbs.   There may be a few more improvements I can...

I've released version 1.4.5 of the plugin which contains the following changes: Add timeout to requests that take more than 10 seconds to respond Remove deprecated settings from config.schema.json and README files   Note that some settings are being removed in the next version of the plugin...

Hi @highlyAuto,   I might try to add a timeout to the requests so that the plugin doesn't wait indefinitely for a response from the Omni controller. This should hopefully allow you to then use the plugin. The only impact I can see is that the status of the zones won't be initialised but that...

I'm not exactly sure but I think you need to use the PC Access app to do it.  Have a look in https://github.com/mantorok1/homebridge-omnilink-platform/issues/5 (near the bottom) if you need to download a copy.   If you can't figure it out try posting in this forum as there's a few knowledgable...

Version 4.0b is the latest version so that should be fine.   The temperature (ie. auxiliary) sensors are also zones so that is very likely the issue. I think the temp sensor could be used by the thermostat. However, the thermostats themselves (and buttons) are seperate to zones so they shouldn't...

I'm not really sure. It could be a faulty zone that's not returning its status. Does the SnapLink app show a problem with any of the zones?   Do you know what firmware version your Omni controller is on? Maybe the version you have has a bug that affects the OmniLink API?