You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated the bacnet proxy to use the 0.3.0 boptest API. You should be able to drop most of your changes in the patch to BopTestProxy. You can now give the boptest URL as a commandline option.
The bacpypes.ini file will still need to be to be patched, bacpypes can't take its IP address through a commandline argument or env variable, it's got to be in the .ini file. (Same with the object identifier).
BACpypes can take a commandline argument of where to find the .ini file, though - so maybe it'd be better if the docker-compose setup could at least the object identifier as a commandline/env variable and then maybe a script could write out a .ini file in the container and pass that as a commandline argument to BopTestProxy.
The text was updated successfully, but these errors were encountered:
I updated the bacnet proxy to use the 0.3.0 boptest API. You should be able to drop most of your changes in the patch to BopTestProxy. You can now give the boptest URL as a commandline option.
The bacpypes.ini file will still need to be to be patched, bacpypes can't take its IP address through a commandline argument or env variable, it's got to be in the .ini file. (Same with the object identifier).
BACpypes can take a commandline argument of where to find the .ini file, though - so maybe it'd be better if the docker-compose setup could at least the object identifier as a commandline/env variable and then maybe a script could write out a .ini file in the container and pass that as a commandline argument to BopTestProxy.
The text was updated successfully, but these errors were encountered: