Michael Jacoby

+1 Any updates on the status?

Any progress on this? I just stumbled across the exact same issue and could reproduce it with Moquette version 0.11, 0.13 and 0.14. Actually, my sample scenario is even a...

Thanks for the feedback @bobrowskim ! Your hack works for me, so at least there is a quick workaround. However, it would be nice to have this bug properly fixed....

What's the status on this? Any chance this might be implemented in the near future? Making variables of type boolean and showing them as a checkbox would be really helpful...

This feature is not supported. We are aware that some users would like to have this feature but currently we cannot provide any details on if/when it will be available...

There are several issues with your example - `assetConnection` and `messageBus` config sections are mixed Your example (simplified) was ```js { "core": {...}, "endpoints": [...], "persistence": {...}, "messageBus": { "@class":...

As for now, FA³ST only supports a limited set of OPC UA data types out-of-the-box, namely the ones defined as [built-in datatypes by the used OPC UA client library (Eclipse...

Please have a look at the [API specification](https://www.plattform-i40.de/IP/Redaktion/DE/Downloads/Publikation/Details_of_the_Asset_Administration_Shell_Part_2_V1.pdf), especially Section 10.3 which states > To avoid problems with IRIs in URLs the identifiers shall be BASE64-URL-encoded before using them as...

Yes, it is possible to map an AAS Operation to an HTTP server. For details how to do this, please have a look at the following documents - [AAS specification...

You are mixing configuration properties from OPC UA (`nodeId`) and HTTP (`format`, `path`, and `method`). Are you trying to use OPC UA via HTTPS or just HTTP(S) and forgot to...