ERROR: 500 - Internal Server Error

Hello,

i installed this ebus binding.

After i add my Configuration URL and try to add my VRT392 setting i got in Paper UI this Error:

ERROR: 500 - Internal Server Error

what could be the problem?

That is a web server error, likely related to your configuration URL. Have you tried accessing that URL in a web browser? I expect you will get a similar error.

Could you provide some log details and your configuration file?

1 Like

i use this Configuration URL:

  • vaillant_template.json
  • 39200.15.392_configuration.json

i take the files form this site

i got this log:

0:00:51.047 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Auto-SYN byte received
20:00:51.096 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Auto-SYN byte received
20:00:51.104 [TRACE] [sdev.ebus.core.EBusLowLevelController] - Receive buffer still not empty, skip ...
20:00:51.112 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SYN to SRC_ADDR
20:00:51.126 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SRC_ADDR to TGT_ADDR
20:00:51.136 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from TGT_ADDR to PRIMARY_CMD
20:00:51.147 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from PRIMARY_CMD to SECONDARY_CMD
20:00:51.156 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Master data length: 1
20:00:51.167 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SECONDARY_CMD to LENGTH1
20:00:51.184 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from LENGTH1 to DATA1
20:00:51.193 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Master CRC correct
20:00:51.200 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from DATA1 to CRC1
20:00:51.210 [TRACE] [sdev.ebus.core.EBusLowLevelController] - waiting for slave answer ...
20:00:51.218 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from CRC1 to ACK1
20:00:51.227 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Slave data Length: 9
20:00:51.235 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from ACK1 to LENGTH2
20:00:51.245 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data 8
20:00:51.257 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data 7
20:00:51.266 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data 6
20:00:51.275 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data 5
20:00:51.285 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data 4
20:00:51.293 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data 3
20:00:51.302 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data 2
20:00:51.308 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Data 1
20:00:51.315 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from LENGTH2 to DATA2
20:00:51.325 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from DATA2 to CRC2
20:00:51.332 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from CRC2 to ACK2
20:00:51.339 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from ACK2 to SYN
20:00:51.346 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - fireTelegramAvailable ...
20:00:51.354 [TRACE] [sdev.ebus.core.EBusLowLevelController] - Receive buffer still not empty, skip ...
20:00:51.362 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from SYN to UNKNOWN
20:00:51.372 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Update state from UNKNOWN to SYN
20:00:51.379 [TRACE] [sdev.ebus.core.EBusLowLevelController] - Receive buffer still not empty, skip ...
20:00:51.389 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Auto-SYN byte received
20:00:51.400 [TRACE] [sdev.ebus.core.EBusLowLevelController] - Receive buffer still not empty, skip ...
20:00:51.408 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Auto-SYN byte received
20:00:51.416 [TRACE] [sdev.ebus.core.EBusLowLevelController] - Receive buffer still not empty, skip ...
20:00:51.425 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Auto-SYN byte received
20:00:51.440 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Auto-SYN byte received
20:00:51.489 [TRACE] [dev.ebus.core.EBusReceiveStateMachine] - Auto-SYN byte recei

it don’t look like there you can find the error

i tried it on my raspbian which is installed on my rpi3.
there i can’t find any problem to get access to the file

Can someone help me to solve the problem?

I doubt that either of those is a valid URL.

i use this JSON File.
With a order version of ebus Binding, i haven’t this problem.