Generell ist es so, dass nur die virtuellen Taster angezeigt werden, die auch benannt sind. Wenn die Taster noch die Standardnamen haben, werden diese gar nicht erst angezeigt.
Kannst Du prüfen, ob die Taster bei Dir benannt sind? Sollte das weiterhin nicht funktionieren, sag mir bitte welche Plattform und Version der App du verwendest.
Yes, I did the „Refresh“, no effect, btw. I had these virtual buttons in the CCU before installing the Martha App …
How and where can I allow any other ports in CCU Firewall? I only see there (Configure Firewall) only options for API (I have „Full“ there) and „IP addresses for restricted access“.
Where can I enter allowed ports?
Yes, I see them there and they are functional there.
But of course, like every virtual device, they have categories and rooms assigned to them, I don’t see them there :lehce_frowning_face:
ah, the assigments doesn’t work, now I get it. I will check this.
So you’re using CUxD to control your smart TP-link? Do you see the devices in the Smartha App? How does it look on your CCU, could you provide a screenshot?
Yes, this is primarily provided by the TCL script (see the link to the HM forum), TP link sockets are then normally seen in Devices with the help of CUxD, as well as the original HM sockets (see printscreen)! .
Sockets are assigned to Rooms and Categories, in the TinyMatic App they can be seen perfectly as they should.
In Smartha only one of them is displayed (see printscreen), only the first one from the list in Devices,
for others Smartha shows an error (see printscreen).
I am sorry, I was wrong. The problem ist that you are using a CUxD device type (HM-LC-Sw1-Pl) which only have 1 channel in reality. Our definitions are based on real devices - thats why you just see the first one. In your room ‚Pracovna‘ you should see the first channel.
You will need to modify the device definition or create a custom one for this device manually and add the missing channels. The other option is to use a ‚real‘-device type which supports that cound of channels. Currently there is no other way to do that.
Is there an easy way how he could simply copy & paste the channels when he will create his own definition so the changes will be quickly done by him?
Maybe an idea for the future to create in the App „CuxD Delta defintions function“ that will do the necessary changes automatically with a click in the app or open an assistant - the logic should be more ore less always the same?
oh, so that’s bad, I have definitions as described in the TP socket add-on (see link above). Interestingly, there is no problem in the TinyMatic application. Or is it possible to solve it?
I use these smart sockets in larger quantities, although mostly in automated functions. Nevertheless, I need direct access to them, which I will use through their own KASA app. But then Martha loses her meaning for me.
If it will not be possible to add a virtual device (in Rooms and Categories) in the future, it is not usable for me - is it possible to return the money for MARTHA?
In addition, I discovered another problem with the display of HUE devices (CCU Addon to the control of Philips Hue Lichtern by J-A-A-N). Missing power button …
TinyMatic does work differently, it is hard coded UI based on the device. We are defining the devices layout in a separate definition which allows us to 100% customize it and let the user do it himself.
I will look into it if I can workaround and add the additional missing UI definition for CUxD devices by default. This are always the same channels, right?
Since the stores are managing the payments, e.g Google, Apple, Microsoft you can use the refund options in the stores.
Hi, despite several application updates, it is still not functional, the virtual buttons created in CCU2 and assigned to individual rooms and categories are not visible at all.
For example, would it not be possible to manually assign them to individual rooms directly in the Smartha application?
A similar problem is with TPL smart sockets, see above … Nothing has changed there either