Comments (21)
GravySeal
commented on June 2, 2024
Hello Hochram,
It seems the Salda HVAC system does not support Read Multiple requests. I made an update for the dev version (1.3.3) that should add a way to deal with this issue. Could you try it for me?
Once the add-on is able to read your device, the integration should be able to be added as well. The integration can't do much when the add-on sends empty data.
from bepacom-bacnet-ip-integration.
Hochram
commented on June 2, 2024
Hi GravySeal,
thanks for the prompt answer!
I updated the dev version, rebooted all but unfortunately the error stands still:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
�[34m-----------------------------------------------------------�[0m
�[34m Add-on: Bepacom BACnet/IP Interface Development Version�[0m
�[34m Bepacom BACnet/IP interface for the Bepacom EcoPanel. Allows BACnet/IP devices to be available to Home Assistant through an API.�[0m
�[34m-----------------------------------------------------------�[0m
�[34m Add-on version: 1.3.3�[0m
�[32m You are running the latest version of this add-on.�[0m
�[34m System: Home Assistant OS 11.5 (amd64 / qemux86-64)�[0m
�[34m Home Assistant Core: 2024.2.1�[0m
�[34m Home Assistant Supervisor: 2024.01.1�[0m
�[34m-----------------------------------------------------------�[0m
�[34m Please, share the above information when looking for help�[0m
�[34m or support in, e.g., GitHub, forums or the Discord chat.�[0m
�[34m-----------------------------------------------------------�[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-interface: starting
[08:29:59] INFO: �[32mRunning init-nginx.�[0m
[08:29:59] INFO: �[32mRunning init-interface.�[0m
[08:29:59] INFO: �[32mAllowed addresses for NGINX: 127.0.0.1 192.168.1.200 172.30.32.1 172.30.232.1�[0m
[08:29:59] INFO: �[32mGenerated ingress configuration successfully!�[0m
s6-rc: info: service init-nginx successfully started
[BACpypes]
objectName: EcoPanel
address: 192.168.1.200/24
objectIdentifier: 420
maxApduLengthAccepted: 1476
segmentation: segmentedBoth
vendorIdentifier: 15
foreignBBMD: -
foreignTTL: 255
maxSegmentsAccepted: 64
loglevel: WARNING
defaultPriority: 15
updateInterval: 60
s6-rc: info: service init-interface successfully started
s6-rc: info: service interface: starting
s6-rc: info: service interface successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[08:30:01] INFO: �[32mRunning interface�[0m
ERROR: Nack error reading device props: device,93300: unrecognized-service
ERROR: exception: KeyError('device:93300')
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/bacpypes3/app.py", line 899, in indication
await helperFn(apdu)
File "/usr/bin/BACnetIOHandler.py", line 164, in do_IAmRequest
services_supported = self.bacnet_device_dict[f"device:{device_id}"][
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'device:93300'
ERROR: An uncaught error occurred: 'IAmRequest' object has no attribute 'apduInvokeID'
NoneType: None
WARNING: Invalid HTTP request received.
[08:30:20] INFO: �[32mRunning NGINX�[0m
2024/02/11 08:30:20 [notice] 285#285: using the "epoll" event method
2024/02/11 08:30:20 [notice] 285#285: nginx/1.24.0
2024/02/11 08:30:20 [notice] 285#285: OS: Linux 6.1.74-haos
2024/02/11 08:30:20 [notice] 285#285: getrlimit(RLIMIT_NOFILE): 1073741816:1073741816
2024/02/11 08:30:20 [notice] 285#285: start worker processes
2024/02/11 08:30:20 [notice] 285#285: start worker process 357
ERROR: Disconnected...
2024/02/11 08:34:59 [info] 357#357: *1 client 172.30.32.2 closed keepalive connection
ERROR: Disconnected...
Regards
from bepacom-bacnet-ip-integration.
GravySeal
commented on June 2, 2024
I see where I made the mistake, I just pushed another update.
After you check for updates in your add-on store you can click rebuild on the add-on page. This should install the latest version for you. Let me know if this works!
from bepacom-bacnet-ip-integration.
Hochram
commented on June 2, 2024
Something changed
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
�[34m-----------------------------------------------------------�[0m
�[34m Add-on: Bepacom BACnet/IP Interface Development Version�[0m
�[34m Bepacom BACnet/IP interface for the Bepacom EcoPanel. Allows BACnet/IP devices to be available to Home Assistant through an API.�[0m
�[34m-----------------------------------------------------------�[0m
�[34m Add-on version: 1.3.3�[0m
�[32m You are running the latest version of this add-on.�[0m
�[34m System: Home Assistant OS 11.5 (amd64 / qemux86-64)�[0m
�[34m Home Assistant Core: 2024.2.1�[0m
�[34m Home Assistant Supervisor: 2024.01.1�[0m
�[34m-----------------------------------------------------------�[0m
�[34m Please, share the above information when looking for help�[0m
�[34m or support in, e.g., GitHub, forums or the Discord chat.�[0m
�[34m-----------------------------------------------------------�[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-interface: starting
[16:27:33] INFO: �[32mRunning init-interface.�[0m
[16:27:33] INFO: �[32mRunning init-nginx.�[0m
[16:27:34] INFO: �[32mAllowed addresses for NGINX: 127.0.0.1 192.168.1.200 172.30.32.1 172.30.232.1�[0m
[16:27:36] INFO: �[32mGenerated ingress configuration successfully!�[0m
s6-rc: info: service init-nginx successfully started
[BACpypes]
objectName: EcoPanel
address: 192.168.1.200/24
objectIdentifier: 420
maxApduLengthAccepted: 1476
segmentation: segmentedBoth
vendorIdentifier: 15
foreignBBMD: -
foreignTTL: 255
maxSegmentsAccepted: 64
loglevel: WARNING
defaultPriority: 15
updateInterval: 60
s6-rc: info: service init-interface successfully started
s6-rc: info: service interface: starting
s6-rc: info: service interface successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[16:27:42] INFO: �[32mRunning interface�[0m
ERROR: Nack error reading device props: device,93300: unrecognized-service
ERROR: Nack error reading device props one by one: device,93300: property: unknown-property
ERROR: Nack error reading device props one by one: device,93300: property: unknown-property
ERROR: Nack error: device,93300: property: unknown-property
WARNING: Invalid HTTP request received.
[16:27:59] INFO: �[32mRunning NGINX�[0m
2024/02/11 16:27:59 [notice] 284#284: using the "epoll" event method
2024/02/11 16:27:59 [notice] 284#284: nginx/1.24.0
2024/02/11 16:27:59 [notice] 284#284: OS: Linux 6.1.74-haos
2024/02/11 16:27:59 [notice] 284#284: getrlimit(RLIMIT_NOFILE): 1073741816:1073741816
2024/02/11 16:27:59 [notice] 284#284: start worker processes
2024/02/11 16:27:59 [notice] 284#284: start worker process 351
ERROR: Disconnected...
2024/02/11 16:29:13 [info] 351#351: *1 client 172.30.32.2 closed keepalive connection
ERROR: Disconnected...
ERROR: Nack error reading device props: device,93300: unrecognized-service
ERROR: Nack error reading device props one by one: device,93300: property: unknown-property
ERROR: Nack error reading device props one by one: device,93300: property: unknown-property
ERROR: Nack error: device,93300: property: unknown-property
ERROR: Disconnected...
2024/02/11 16:44:57 [info] 351#351: *17 client 172.30.32.2 closed keepalive connection
ERROR: Disconnected...
2024/02/11 16:45:45 [info] 351#351: *21 client 172.30.32.2 closed keepalive connection
I can see the device in the add-on page with properties, I can add the integration ( but only using local host (127.0.01) and not using Home Assistant IP) but no devices/entities are created.
Thanks
from bepacom-bacnet-ip-integration.
GravySeal
commented on June 2, 2024
Would you mind trying again? I added some better handling for individual properties.
Hopefully you should be able to see all the data available then.
from bepacom-bacnet-ip-integration.
Hochram
commented on June 2, 2024
It just doesn't want to collaborate it seems
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: Bepacom BACnet/IP Interface Development Version
Bepacom BACnet/IP interface for the Bepacom EcoPanel. Allows BACnet/IP devices to be available to Home Assistant through an API.
-----------------------------------------------------------
Add-on version: 1.3.3
You are running the latest version of this add-on.
System: Home Assistant OS 11.5 (amd64 / qemux86-64)
Home Assistant Core: 2024.2.1
Home Assistant Supervisor: 2024.01.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-interface: starting
[19:22:58] INFO: Running init-nginx.
[19:22:58] INFO: Running init-interface.
[19:22:58] INFO: Allowed addresses for NGINX: 127.0.0.1 192.168.1.200 172.30.32.1 172.30.232.1
[19:23:02] INFO: Generated ingress configuration successfully!
s6-rc: info: service init-nginx successfully started
[BACpypes]
objectName: EcoPanel
address: 192.168.1.200/24
objectIdentifier: 420
maxApduLengthAccepted: 1476
segmentation: segmentedBoth
vendorIdentifier: 15
foreignBBMD: -
foreignTTL: 255
maxSegmentsAccepted: 64
loglevel: WARNING
defaultPriority: 15
updateInterval: 60
s6-rc: info: service init-interface successfully started
s6-rc: info: service interface: starting
s6-rc: info: service interface successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[19:23:11] INFO: Running interface
ERROR: Nack error reading device props: device,93300: unrecognized-service
ERROR: Nack error reading device props one by one: device,93300: max-segments-accepted property: unknown-property
ERROR: Nack error reading device props one by one: device,93300: serial-number property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
I don't know what exactly in the lines missing as it starts to spam in loop the last line and it's difficult to get on the log.
Keep up the god job :)
from bepacom-bacnet-ip-integration.
GravySeal
commented on June 2, 2024
The error lines aren't necessarily an issue, it's just trying to read BACnet properties that don't exist on your device. If you look in the web UI, is there more data?
from bepacom-bacnet-ip-integration.
Hochram
commented on June 2, 2024
Sorry, I missed the important bit.
Unfortunately, still no devices/entities
from bepacom-bacnet-ip-integration.
GravySeal
commented on June 2, 2024
Does the addon Web UI show any objects and properties?
from bepacom-bacnet-ip-integration.
Hochram
commented on June 2, 2024
from bepacom-bacnet-ip-integration.
GravySeal
commented on June 2, 2024
Any objects below the device object?
from bepacom-bacnet-ip-integration.
Hochram
commented on June 2, 2024
Hope you mean here
Can't see anything else
from bepacom-bacnet-ip-integration.
GravySeal
commented on June 2, 2024
Could you perhaps check for updates, rebuild and post the logs again? I made the logging slightly more detailed. Hopefully I can find the issue then.
from bepacom-bacnet-ip-integration.
Hochram
commented on June 2, 2024
Here are the new logs:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: Bepacom BACnet/IP Interface Development Version
Bepacom BACnet/IP interface for the Bepacom EcoPanel. Allows BACnet/IP devices to be available to Home Assistant through an API.
-----------------------------------------------------------
Add-on version: 1.3.3
You are running the latest version of this add-on.
System: Home Assistant OS 11.5 (amd64 / qemux86-64)
Home Assistant Core: 2024.2.1
Home Assistant Supervisor: 2024.01.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-interface: starting
[20:48:59] INFO: Running init-nginx.
[20:48:59] INFO: Running init-interface.
[20:48:59] INFO: Allowed addresses for NGINX: 127.0.0.1 192.168.1.200 172.30.32.1 172.30.232.1
[20:49:02] INFO: Generated ingress configuration successfully!
s6-rc: info: service init-nginx successfully started
[BACpypes]
objectName: EcoPanel
address: 192.168.1.200/24
objectIdentifier: 420
maxApduLengthAccepted: 1476
segmentation: segmentedBoth
vendorIdentifier: 15
foreignBBMD: -
foreignTTL: 255
maxSegmentsAccepted: 64
loglevel: WARNING
defaultPriority: 15
updateInterval: 60
s6-rc: info: service init-interface successfully started
s6-rc: info: service interface: starting
s6-rc: info: service interface successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[20:49:06] INFO: Running interface
ERROR: Nack error reading device props: device,93300: unrecognized-service
ERROR: Nack error reading device props one by one: device,93300: max-segments-accepted property: unknown-property
ERROR: Nack error reading device props one by one: device,93300: serial-number property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
ERROR: Nack error reading object list one by one: device,93300: property: unknown-property
Noticed this when checking supervisor after rebuild, just fyi
from bepacom-bacnet-ip-integration.
GravySeal
commented on June 2, 2024
Would you mind checking for updates and rebuilding again? Seems the update didn't come through this attempt.
Noticed this when checking supervisor after rebuild, just fyi
This seems to indicate there might be something wrong in the configuration. If you want to go back to the default settings you can also just remove and reinstall the add-on.
from bepacom-bacnet-ip-integration.
Hochram
commented on June 2, 2024
Uninstalled and installed again, here is the log:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: Bepacom BACnet/IP Interface Development Version
Bepacom BACnet/IP interface for the Bepacom EcoPanel. Allows BACnet/IP devices to be available to Home Assistant through an API.
-----------------------------------------------------------
Add-on version: 1.3.3
You are running the latest version of this add-on.
System: Home Assistant OS 11.5 (amd64 / qemux86-64)
Home Assistant Core: 2024.2.1
Home Assistant Supervisor: 2024.01.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-interface: starting
[22:16:13] INFO: Running init-nginx.
[22:16:13] INFO: Running init-interface.
[22:16:13] INFO: Allowed addresses for NGINX: 127.0.0.1 192.168.1.200 172.30.32.1 172.30.232.1
[22:16:14] INFO: Generated ingress configuration successfully!
s6-rc: info: service init-nginx successfully started
Using enp0s18 as address: 192.168.1.200/24
[BACpypes]
objectName: EcoPanel
address: 192.168.1.200/24
objectIdentifier: 420
maxApduLengthAccepted: 1476
segmentation: segmentedBoth
vendorIdentifier: 15
foreignBBMD: -
foreignTTL: 255
maxSegmentsAccepted: 64
loglevel: WARNING
defaultPriority: 15
updateInterval: 600
s6-rc: info: service init-interface successfully started
s6-rc: info: service interface: starting
s6-rc: info: service interface successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
[22:16:14] INFO: Running interface
s6-rc: info: service legacy-services successfully started
ERROR: Nack error reading device props: device,93300: unrecognized-service
ERROR: Error PDU error reading device props one by one: device,93300: max-segments-accepted property: unknown-property
ERROR: Error PDU error reading device props one by one: device,93300: serial-number property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 present-value: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 status-flags: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 out-of-service: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 units: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 event-state: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 reliability: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 cov-increment: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 state-text: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 number-of-states: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 notification-class: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 min-pres-value: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 max-pres-value: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 active-text: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 inactive-text: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 polarity: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,0 relinquish-default: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,1 present-value: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,1 status-flags: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,1 out-of-service: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,1 units: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,1 event-state: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,1 reliability: property: unknown-property
ERROR: Error PDU reading object list one by one: device,93300 analog-input,1 cov-increment: property: unknown-property
this goes up to analog-input,10
No news on webui, errors in supervisor went away.
from bepacom-bacnet-ip-integration.
GravySeal
commented on June 2, 2024
To me it looks like there are no properties at all in the BACnet objects. Do you know YABE? What results do you get if you try to read it with YABE?
https://sourceforge.net/projects/yetanotherbacnetexplorer/
from bepacom-bacnet-ip-integration.
Hochram
commented on June 2, 2024
Hi,
it seems Yabe is able to read all the properties as are also reported on the Salda interface
For example:
Anyway, thanks for the YABE tip, didn't know it or maybe tried with no luck years ago..
from bepacom-bacnet-ip-integration.
Bepacom-Raalte
commented on June 2, 2024
Hello,
I think I found the issue. Could you check for updates and rebuild the add-on?
from bepacom-bacnet-ip-integration.
Hochram
commented on June 2, 2024
Bingo!!
Great work, thanks!
If you need to test something, count on me ;)
from bepacom-bacnet-ip-integration.
Bepacom-Raalte
commented on June 2, 2024
Wonderful, great to see! If there are any other problems, please feel free to create a new issue here on GitHub!
from bepacom-bacnet-ip-integration.
Related Issues (20)
- Unable to add integration - Bepacom BACnet/IP Interface HOT 32
- Unknown error when adding integration HOT 5
- 401: Unauthorized - Cannot access API from Home Assistant via RESTful Sensor HOT 2
- Wrong presentValue is send in entity (select) HOT 8
- Need more detailed instructions HOT 4
- TypeError: 'NoneType' object is not subscriptable HOT 8
- Unable to add new devices HOT 2
- Error setting up entry BACnet Interface for bacnet_interface HOT 75
- Replace domain of the integration so it can be added to brands repository
- Entities to Bacnet Objects HOT 5
- Values are not getting updated in HomeAssistant HOT 96
- Configuration HOT 126
- Integration & Add-On are not restoring the operational state after a HA restart HOT 4
- Two different types of decimal separators in my BACnet Integration HOT 3
- request to add units HOT 9
- Can't get integration to work HOT 4
- Size of home assistant backup HOT 8
- adding points in the devices HOT 5
- HA Bacnet update killed communications HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bepacom-bacnet-ip-integration.