About CodeShepherd

Which software version is installed on your control (e.g. 1.10)? We had some problems with class C networks in the past. The easiest workaround would be to give your control a fitting IP like 192.168.10.1/24 as well as the PC e.g. 192.168.10.12/24. ... View more

I will check why the the warning is not visible. Normally warnings do acknowledged automatically  as soon as the reason for it gone. To get back to solid green send following command:   PUT/WRITE https://192.168.1.2/automation/api/v1.0/diagnosis/confirm/error payload=null   EDIT: Actual state is visible on the Data Layer:       ... View more

Thank you for the hint with the other thread. The solution in our case was next to sending a message with payload 'null' to recieve this payload as 'value + type(json)' at the request node. node-red-contrib-ctrlx-automation version 1.8.7 ... View more

You have to change the setting of the diagnosis log o persistent, then "old" errors it will be available after reboot: Moved topic to ctrlX CORE.   ... View more

The offline help is still in preparation and will be part of ctrlX WORKS. The online diagnosis is already available but the search function does not seem to work properly. I will get in contact with our R&D. If you search the numbers by hand you will get information (e.g. 090F2002) : Storig system report or only the diagnostic log is possible via the web interface:   EDIT: Moved topic to ctrlX WORKS.     ... View more