I started having problems with node red and Hubitat recently. I noticed that when I restarted the HA core, node red was broken.
After experimenting a bit I discover that when the core is restarted the Maker API Post URL was getting set to a seemingly random port number. Simultaneously I was trying to figure out why Lovelace dashboards were working fine upon the restart and would misbehave if I restored the webhook for node red.
Turns out that I confirmed that lovelace is using the Maker API Post for its own purposes and is overwriting the node red URL. I can readily use either but not both.
I suppose the simplest solution from a Home Assistant point of view would be for the Hubitat Maker API to accept multiple URLs. I'm currently thinking about making a flow that "discovers" this problem and restores the URL for node red and to receive and forward all events to the lovelace URL in the same format they are received from Hubitat. I suppose the first issue is whether the event objects received by node red are exactly as sent by Hubitat or have been manipulated before the application gets them.
I'll be experimenting because I would like a working lovelace interface without breaking my automations in node red. The sticky point at the moment is uncertainty about whether there is a race condition for multiple integrations initializing the URL or if it is deterministic. Currently it SEEMS deterministic, and that I can use the existing URL to forward all events to lovelace.
Any suggestions or solutions already implemented?