But the PLC only allows for ads connections from a device to which it has a route.Ĭonnect to your plc using TwinCAT and add a route to your hassio server. tpy file to know where the variables are in memory.

At work we use ProFace HMI’s which use a TwinCAT. First it wasn’t working, but something from work reminded me of what might be the cause and in my case it seemed to help. I haven’t got a clue regarding the errors you see but I got my setup (though TwinCAT 2) connected yesterday. Judging by the comments in post one I’m assuming you’re dutch device parameter is specified between quotes, adsvar typically not (in my configuration file, I tried both as a test by the way)Ĭan anyone elaborate on this and point me in the right direction please?

Sometimes string type variable are surrounded by quotes and sometimes not (e.g. Is the prefix for TwinCAT3 ‘GBL’ or ‘GVL’?ĭo yo need to specify the whole variable path or just the variable name?Ĭan you reach any variable defined in the PLC or do you need to define variables in a special way in the PLC environment in order to be exposed to ADS? Some questions concerning the adsvar parameter : Does this mean that the HA instance on QNAP is not responding to ADS traffic? Or is this normal? Is pyADS service running, even if it is installed on HA? Can I check this in some way? It only found the PC from which I am developing. I let the PLC do a search for ADS compliant devices on my network. I also logged in to the PLC via my PC and opened the ‘static routes’ dialog. So, I guess no communication is established with the PLC, or the adsvar names are not formatted as it should, or I am trying to address variables that are not reachable by ADS. The entities that are defined in the configuration file appear in the entities list, but with the indication ‘unavailable’. The HA user interface starts without reporting any visible error. I opened a console terminal and launched the command ‘pip install pyads’ which returned a message that the package was already installed. I also found out that HA needs pyADS installed in order to be able to communicate with a plc. The PLC port is set to ‘851’ by default (so not ‘801’). The ‘device’ tag is set to the ams-id that can be found in the Twincat programming environment, as is the IP address, which is fixed by the way. My configuration.yaml file currently looks like this… # Configure a default setup of Home Assistant (frontend, api, etc)Īdsvar: '.LED_DIM_MIN' In the meantime, I have done some further research and trials.Īs a reminder : I run HA on a QNAP NAS TS-453D, under a docker container.The PLC is a CX-8190 running Windows Embedded 7.

Beckhoff sample plc program