Platform for component doesn't match its purpose

[tinglis1 (Tim)]

I made a custom component that uses the notify platform as its base for sending serial commands over ip.

Support for IP IR Bridges

I put something together to be able to send IR commands using my Global Cache iTach. I created it as a ‘notify’ component as I felt this would be a good place to start due to its similarities to what I was trying to do and it existing HA integration/documentation. I have uploaded the component to my GitHub below: A summary of how it works. It allows for the sending of onetime commands to an IP socket. In the example below and the configuration that I have is sending “sendir” commands to …

Should I create its own platform or leave it using the notify platform?
In the help section its category is probably ‘automation’.

It is working correctly (so far) and has been tested by a few others so in the near future would like to move to the next phase of tidying up code and submitting a pull request.

[fabaff (Fabian Affolter)]

For me it’s look like that this should be it’s own component and exposing a service to send the data. The persistent_notification is creating notification but is not a notify platform.

[tinglis1 (Tim)]

That what I thought. I will make the change.

[koying (Chris B)]

Sorry to necropost, but I’m exactly trying to understand the reasoning behind the fact that persistent_notification is not a notify platform. Or maybe why there is not an equivalent “plain” notify platform to show notifs on the webui.

My use case is to be able to send notifications to my phone even when internet is down (to notify that internet is down ) and 99% of the existing ones uses internet…

Not a technical problem, ofc, but rather a conceptual interrogation…