-
Notifications
You must be signed in to change notification settings - Fork 13
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
RPC Event Node: No autocomplete #18
Comments
Should be repaired with RedMatic 1.3.0 respectively node-red-contrib-ccu 1.4.1 |
Many thanks for the quick reaction. I might be wrong but I think the old behavior was that the subsequent entries have been filtered according to the previous selection. For example, now all available If I'm wrong call it a feature request ;-) |
And there is a second issue: |
Should be fixed in node-red-contrib-ccu 1.4.2 (you can update it via the node-red palette manager)
I think that's a feature request, that's implemented in the |
Well, I would exclude the RegExp from the filter. If you are able to properly setup the RegExp, you anyway know what you are doing. |
ok. will do asap ;) can i remove the bug label from this issue (are the select values remembered in 1.4.2?) |
Um, I don't want to be a pain in the back, but after updating to 1.4.2 the autocomplete again stopped working :-S |
narf :) |
next try: v1.4.3 :) |
The same thing we do every night, @hobbyquaker - try to take over the world! Works 👍 |
The autocomplete of the RPC event node stopped working for me. For the other Nodes it is still working. Tested in Redmatic v1.2.1
The text was updated successfully, but these errors were encountered: