Hello together,
I’m dealing with the same problem since months (but it took a long time before I’ve got some spare time to scrutinize the KM200 vs. the binding).
1st of all, I’ve been able to verify the AES private key by using the PHP scripts provided by Andreas. With help of a slightly modified script, the verification of the AES key calculation succeeded: The password is correct and the gateway is responding.
2nd step was to enter this AES private key into the binding configuration (tried both ways either via PaperUI or via textual configuration) resulting in the same error messages … therefere, the bindung seems to do same strange things.
3rd with help of a network sniffer, I’ve been observing the request URLs from bindung to KM200:
Most of them are answered with valid JSON (after decryption), but the registration query leads to weired results:
contacting MB-LAN for /gateway/DateTime
>>>{"id":"/gateway/DateTime","type":"stringValue","writeable":1,"recordable":0,"value":"2022-08-10T16:31:02"}
DateTime is 2022-08-10T16:31:02:
contacting MB-LAN for /gateway/uuid
>>>{"id":"/gateway/uuid","type":"stringValue","writeable":0,"recordable":0,"value":"207060676"}
uuid is 207060676:
contacting MB-LAN for /gateway/versionFirmware
>>>{"id":"/gateway/versionFirmware","type":"stringValue","writeable":0,"recordable":0,"value":"01.10.03"}
versionFirmware is 01.10.03:
contacting MB-LAN for /gateway/userpassword
userpassword is :
contacting MB-LAN for /gateway/instPassword
instPassword is :
contacting MB-LAN for /gateway/instAccess
>>>{"id":"/gateway/instAccess","type":"stringValue","writeable":1,"recordable":0,"value":"off","allowedValues":["on","off"]}
instAccess is off:
contacting MB-LAN for /gateway/instWriteAccess
>>>{"id":"/gateway/instWriteAccess","type":"stringValue","writeable":1,"recordable":0,"value":"off","allowedValues":["on","off"]}
instWriteAccess is off:
contacting MB-LAN for /gateway/registrations
>>>'??b?ȝ˓Wdul
registrations is :
The recent communication is leading to the initialization failure.