2019 May 02, 09:10 AM
@WPB,
Not exacltly what you are planning to do but I use mqtt to "interface" with SIP (yeah, name could be better) and other stuff like home automation and sensor integration. Interfacing is done via Node-Red to route MQTT messages to and from the SIP API and Home automation API. The sensors, actuators and other stuff is done via MySensors with a MQTT gateway.
I also considered doing it the way you described and recently started to run SIP in a (docker) container. Using containers with the current SIP architecture is a bit of a challenge but we will get there.
Maybe Dan can answer this, how about Python3? Are there any thoughts on making SIP future proof? I ask this because I think there have to be made some changes to the code to make SIP suitable to run in a container like Docker of Podman. Of course no problem but I preferably make the changes to a long term version :-)
To be continued.....
--Gerard
Not exacltly what you are planning to do but I use mqtt to "interface" with SIP (yeah, name could be better) and other stuff like home automation and sensor integration. Interfacing is done via Node-Red to route MQTT messages to and from the SIP API and Home automation API. The sensors, actuators and other stuff is done via MySensors with a MQTT gateway.
I also considered doing it the way you described and recently started to run SIP in a (docker) container. Using containers with the current SIP architecture is a bit of a challenge but we will get there.
Maybe Dan can answer this, how about Python3? Are there any thoughts on making SIP future proof? I ask this because I think there have to be made some changes to the code to make SIP suitable to run in a container like Docker of Podman. Of course no problem but I preferably make the changes to a long term version :-)
To be continued.....
--Gerard