It appears that ports with Attribute Ehmi are shown with checkmark for ‚HMI‘ in Engineer, but they are not listed in the REST-API data.dictionary.json?
https://<controller_ip>/ehmi/data.dictionary.json
This file:
but with (for example)
//#port
//#attributes(Output|Retain|Ehmi)
//#name(outBoolean)
I was hoping to generate some live values on the system quickly, but that doesn’t work.
It’s just for testing, so I’ll figure out something else, but I’m still curious if it is supposed to work as I expect?
The REST-API is an easy way to get a list of of variables in the system, and I use it to create subscriptions via gRPC. gRPC doesn’t offer anything like that directly, correct?
You’re right, despite popular demand, only the REST interface currently has anything like a browse feature.
According to this page in the Info Center:
IComponent and IProgram Using the PLCnext CLI (see PLCnext CLI ), Eclipse® Add-in or Visual Studio® extension creates the meta configuration files (*.libmeta, *.compmeta, *.progmeta) required for PLCnext Engineer as well as the following functions with a functional implementation during compiling. … a C++ port variable with the Ehmi attribute should be accessible via the REST interface:
I will try to check this tomorrow, if someone else doesn’t first. 
Which controller and firmware version are you using?
Just reading the question again - am I right in saying that you can read and write C++ ports via REST (when they’re marked with the Ehmi attribute), but they don’t appear in the REST data dictionary?
If that’s the case, then I am fairly sure that is the expected behaviour. I suspect that’s one of the reasons that these variables are not visible in the PLCnext Engineer HMI editor.
I will ask for this information to be added to the Info Center.
Yes, I can read the out ports via REST. I was looking for them in the REST data dictionary.
Seems that is expected and might change in the future.
Thanks for looking into it and clearing it up.