-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bindings mit Doppelpunkt #212
Comments
Das gleiche Problem tritt auch bei dem Adapter ioBroker.unifi auf. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. |
Bestätigung für stale bot: Die Einschränkung besteht auch noch in vis V1.2.11 |
Semicolon is used in the variable definition. So how can I distinguish between |
I think using an escape character would be the most intuitive method:
|
Hi,this also affects the "BLE" adapter. Here's an example of a DP: Would really appreciate if something could be done about this. |
That is crashing the whole instance. I habe this bug also with the BLE adapter which point name have : |
For data-points with ":" I use aliases. So I'm able to create DP without ":" but with the same content. You need one DP-alias for every DP with ":" but it works fine. |
Same problem with data from Swiss-Weather-API @GermanBluefox: Idea on how to distinguish colons used for variable declaration and colons that are part of a datapoint-name:
The proposal from Parodontitis is quite cumbersome in my case. I plan to visualize 100+ such datapoints. Creating for each of them an alias would be an overkill |
I would more propose to allow the OBject ID to be in quotes to identify "this belongs together and should not be split. see #388 (comment) ... wuld that make sense? In fact would be comparable convention as in CSV or such |
Ein typischer Datenpunkt von smartmeter ist: smartmeter.0.1-0:1_8_1_255.value
Wenn ich jetzt im HTML den Wert mit {smartmeter.0.1-0:1_8_1_255.value} ausgeben will, wird immer ein 0 angezeigt. Meine Vermutung ist, dass es an den Doppelpunkten in DP-Namen liegt.
Da Doppelpunkte in Datenpunktnamen erlaubte Zeichen sind, wurde mein issue abgelehnt.
Siehe: Apollon77/ioBroker.smartmeter#16
The text was updated successfully, but these errors were encountered: