How to get "echo" to valid property ?

---

@Gleno0h With the new Version it will add this to all devices with the value “false”, thats for “white- / blacklist” because alexa has device limits. So its okay that its there…

@tehmilcho hmm i dont know then. If i understand the changes correctly, a device without the echo value will be active true, if you define echo, it would turn false…

if !device.config.hasOwnProperty('echo')
           device.config.echo = {}
        device.config.echo?.active = false

But i suck at coffeescript so not sure :-d

@Gleno0h i had to change via Config the Devices that i want to use to “true”… but thats not Topic

Pimatic must know from anyware whats a vaild property or whats not… so if i change this… my problem is mostly solved.

Maybe someone from the Deployment-Team of the Pimatic Core can help here? @developer

@tehmilcho said in How to get "echo" to vaild property ?:

i dont know whats “metar-taf” is … maybe something from the Ikea Plugin.

It is one of your devices.

@tehmilcho said in How to get "echo" to vaild property ?:

Maybe someone from the Deployment-Team of the Pimatic Core can help here?

Feel free to issue is a feature request on providing an extended schema for device to allow for 3-rd party extensions. I roughly remember we had similar case in the past (possibly also related to pimatic-echo.

As this is not critical error what is your concern about this? Just getting a bunch of error messages on pimatic startup and when a new device is created should not be much of an issue.

@mwittig “metar-taf” is a device from the “metar-weather” Plugin.

Strange thing is it will work fine with Dummyswitches… in a Dummyswitch i also get the “echo Plugin” options in the Webgui and can setup them, in the other Device i will get this error and cant change the Options over Webgui.

And if i understand @michbeck100 right, then everything work fine with his pimatic… so there is maybe a cache or i dont know something that i can overwrite to fix this…

Same with me: I am unable to set any echo options for a HomeduinoRFSwitch via the Webgui and have the same log messages („error [pimatic]: Invalid config of device “00100B”: Property “echo” is not a valid property“)

As a work-around use the configuration editor

@mwittig Here I’m extending the plugin configuration schema. Seems that this doesn’t work properly for plugins, but only for dummy devices.

@mwittig I think i know why it doesn’t work for plugins. _validateConfig gets called for each plugin and for every “built-in” device. So here is a difference in handling dummy devices and plugin devices.
pimatic-echo just extends the cofig schema of the dummy devices. When implementing this i was thinking that this also works for all other devices.
I guess that this is also the reason why the config editor gui doesn’t work.
Now that i checked my own setup, i must say that everything works as expected! Maybe it’s the order of the plugins.
@tehmilcho Could you try to move the echo plugin to the top of the plugin list?

@michbeck100: Putting the echo-plugin as the first plugin in the config-file solved the problem and made the echo options reappear in the Webgui. Thank you so much for investigating.

Works also for me… first Start with Echo plugin as top i get 24x " Missing property “echo”", second reboot … now all works fine… no errors, in every device the echo-options in the Webgui

ps: sad that my heatings not supported at the mom

@tehmilcho not sure but I think heating will never be supported without Alexa skills.

@michbeck100 sad… maybe i will change later from max q3 heatings to zwave heatings… for zwave.me is already a skill but first i will wait and hope