Closed vafgoettlich closed 2 months ago
internally the check is actually not using the name but the fhem inform id. which unfortunately is based on the name :(. i could probably use the fuuid for this check, but the inform id is used in several other places as well and is actually what fhem sends in its events. so i'm not sure if there would be any other side effects but i will think about a possible change.
i would suggest renaming the devices to Alle_Rolllaeden_OG or something similar and then use an alias in fhem if you want to see the old names in the web ui.
out of curiosity: why do you use two instances for different floors? this prohibits any automations that are linked to both floors and i would think some duplication in other places as well.
Thanks for the fast response. About your question why I am operating 2 fhem-instances I would like to describe the setup a bit:
Now the reason:
that makes sense :) thanks
Dear Maintainer,
first of all I like to thank you for your work. I am running 2 fhem-instances (each on a different floor). I'm having a dummy-devices on both of them called Alle_Rolllaeden (all_shutters in english) to close / open all of them at the same time.
I have added a alexaName Attribute but unfortunately I cannot add the second one because:
Maybe the connection-Name or something like that should be added to identify the device, or am I doing things wrong?