Skip to content
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

Wildcards for topics #281

Open
Rushmed opened this issue Oct 21, 2022 · 3 comments
Open

Wildcards for topics #281

Rushmed opened this issue Oct 21, 2022 · 3 comments

Comments

@Rushmed
Copy link

Rushmed commented Oct 21, 2022

Hi.

thanks for your awsome work.

Pls. consider an option in the adapter settings to add wildcards for topics that are expected. The smart processing eliminates for example the "Motion" topic that I am trying to use.
Of course I read the note on the adapter page:
image
I do not want to waste your time implementing my personally named topics.
As a reference have al look into the ioBroker iot adapter.
image

@onkelalex
Copy link

onkelalex commented Jan 5, 2023

Hi Team,
I would like to join @Rushmed 's request. I saw that it is possible to have additional states included in the adapter via pull request.
Currently I am replacing several Zigbee Pir's with ones that are connected directly to the Sonoff Tasmota to reduce the complexity of my iobroker smarthome :D. These send when triggered a mqtt stat to the sonoff broker.

2023-01-05 08:55:47.415 - debug: sonoff.0 (477437) [Sonoff_Gastwclampe] Received: stat/Sonoff_Gastwclampe/PIR1 = ON
2023-01-05 08:55:49.416 - debug: sonoff.0 (477437) [Sonoff_Gastwclampe] Received: stat/Sonoff_Gastwclampe/PIR1 = OFF

so it would be great, if there will be a possibility to add own topics instead of creating for every topic a new request.

@Apollon77
Copy link
Collaborator

@onkelalex Then please also "thumbs up" on first post ... else it might be invisible that you also have interests

@onkelalex
Copy link

onkelalex commented Jan 5, 2023

@Apollon77 missed that... corrected now and thanks for the hint :)

(by the way @Rushmed , editing the "datapoint.js" helped as a quick and dirty fix until next update ;))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants