ERROR: Nack error reading device props: device,93300: unrecognized-service - Githubissues

Bepacom-Raalte / Bepacom-BACnet-IP-Integration

Bepacom BACnet Integration Repository

Apache License 2.0

12 stars 2 forks source link

ERROR: Nack error reading device props: device,93300: unrecognized-service #14

Closed Hochram closed 4 months ago

Hochram commented 5 months ago

Hi, I have a Salda HVAC system that seems not to be recognized by the add-on, you can see the error in the log down here:

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[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.2[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:27:16] INFO: [32mRunning init-nginx.[0m
[08:27:16] INFO: [32mRunning init-interface.[0m
[08:27:16] INFO: [32mAllowed addresses for NGINX: 127.0.0.1 192.168.1.200 172.30.32.1 172.30.232.1[0m
Using enp0s18 as address: 192.168.1.200/24
[08:27:17] 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: 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
[08:27:17] INFO: [32mRunning interface[0m
s6-rc: info: service legacy-services successfully started
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 162, in do_IAmRequest
    await self.read_object_list(device_identifier=apdu.iAmDeviceIdentifier)
  File "/usr/bin/BACnetIOHandler.py", line 353, in read_object_list
    for obj_id in self.bacnet_device_dict[f"device:{device_identifier[1]}"][
                  ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'device:93300'
ERROR:    An uncaught error occurred: 'IAmRequest' object has no attribute 'apduInvokeID'
NoneType: None
WARNING:  Invalid HTTP request received.
[08:27:47] INFO: [32mRunning NGINX[0m
2024/02/10 08:27:47 [notice] 273#273: using the "epoll" event method
2024/02/10 08:27:47 [notice] 273#273: nginx/1.24.0
2024/02/10 08:27:47 [notice] 273#273: OS: Linux 6.1.74-haos
2024/02/10 08:27:47 [notice] 273#273: getrlimit(RLIMIT_NOFILE): 1073741816:1073741816
2024/02/10 08:27:47 [notice] 273#273: start worker processes
2024/02/10 08:27:47 [notice] 273#273: start worker process 364
2024/02/10 09:39:48 [info] 364#364: *1 client 127.0.0.1 closed keepalive connection
2024/02/10 09:40:10 [info] 364#364: *3 client 127.0.0.1 closed keepalive connection
ERROR:    Disconnected...

2024/02/10 09:41:47 [info] 364#364: *5 client 172.30.32.2 closed keepalive connection

There is an add-on specific for this unit but unfortunately has stopped working after some updates as the add-on was no more serviced. So after a while I noticed your addon and tried to use the HVAC through Bac net but since now I' wasn't able to.

This are the settings of the unit, basically Bac net address 47808, device ID 93300, address 1

immagine

Integration can't be set up, I imagine because of the error in the log

Bepacom1

Thanks Regards

GravySeal commented 4 months ago

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.

Hochram commented 4 months ago

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

GravySeal commented 4 months ago

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!

Hochram commented 4 months ago

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.

Bepacom Bepacom2 Bepacom3

Thanks

GravySeal commented 4 months ago

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.

Hochram commented 4 months ago

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 :)

GravySeal commented 4 months ago

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?

Hochram commented 4 months ago

Sorry, I missed the important bit. Unfortunately, still no devices/entities

Bepacom

GravySeal commented 4 months ago

Does the addon Web UI show any objects and properties?

Hochram commented 4 months ago

bepacom bepacom2

GravySeal commented 4 months ago

Any objects below the device object?

Hochram commented 4 months ago

Hope you mean here

bepacom bepacom2

Can't see anything else

GravySeal commented 4 months ago

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.

Hochram commented 4 months ago

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

immagine

GravySeal commented 4 months ago

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.

Hochram commented 4 months ago

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.

GravySeal commented 4 months ago

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/

Hochram commented 4 months ago

Hi,

it seems Yabe is able to read all the properties as are also reported on the Salda interface

immagine

For example:

immagine

Anyway, thanks for the YABE tip, didn't know it or maybe tried with no luck years ago..

Bepacom-Raalte commented 4 months ago

Hello,

I think I found the issue. Could you check for updates and rebuild the add-on?

Hochram commented 4 months ago

Bingo!!

immagine

Great work, thanks! If you need to test something, count on me ;)

Bepacom-Raalte commented 4 months ago

Wonderful, great to see! If there are any other problems, please feel free to create a new issue here on GitHub!