Is your feature request related to a problem? Please describe.
Sometimes, especially with small shops, there is not always send out a official DHL/UPS/FedEX etc. Email, but instead a shop-mail with the tracking number.
Describe the solution you'd like
Would be great to have this sensor work with multiple attributes and styles of emails, with something like "custom_attribute"
User being able to put a regexp in configuration.yml to extract all sorts of special types from emails.
Additional context
This way, if one knows the style of an email from a small shop, one could regex that style and search for the tracking-number.
companion request for my One-Time-Password request, because probably OTP needs changes on sensors.py anyways in a way of accepting different types of numbers e.g. tracking_numbers and otp_numbers (or needs a more open/global approach; using "numbers" instead of "tracking_numbers") ; if this gets implemented, a more flexible option like "custom_attribute" would be appreciated (this request).
Is your feature request related to a problem? Please describe. Sometimes, especially with small shops, there is not always send out a official DHL/UPS/FedEX etc. Email, but instead a shop-mail with the tracking number.
Describe the solution you'd like Would be great to have this sensor work with multiple attributes and styles of emails, with something like "custom_attribute"
User being able to put a regexp in configuration.yml to extract all sorts of special types from emails.
Additional context This way, if one knows the style of an email from a small shop, one could regex that style and search for the tracking-number.
companion request for my One-Time-Password request, because probably OTP needs changes on sensors.py anyways in a way of accepting different types of numbers e.g. tracking_numbers and otp_numbers (or needs a more open/global approach; using "numbers" instead of "tracking_numbers") ; if this gets implemented, a more flexible option like "custom_attribute" would be appreciated (this request).