Paul,
A method I frequently use to diagnose problems is to start SIP manually:
SSH into the Pi and cd into the SIP directory and stop sip with
then start sip from the command line:
When sip starts several lines of information will be printed including any error messages. Pay close attention to the first couple of lines which is where any plugin errors usually appear.
Another useful tool is a MQTT monitoring program. I have used mqtt-spy which is a java based app. Unfortunately I recently upgraded the version of Java on my main computer and now mqtt-spy and a couple of other java based programs refuse to load.
With a tool like mqtt-spy or MQTT Explorer you can subscribe to the topic sip is using and see what is being sent.
Dan
A method I frequently use to diagnose problems is to start SIP manually:
SSH into the Pi and cd into the SIP directory and stop sip with
Code:
systemctl stop sip3
then start sip from the command line:
Code:
python3 sip.py
Another useful tool is a MQTT monitoring program. I have used mqtt-spy which is a java based app. Unfortunately I recently upgraded the version of Java on my main computer and now mqtt-spy and a couple of other java based programs refuse to load.
With a tool like mqtt-spy or MQTT Explorer you can subscribe to the topic sip is using and see what is being sent.
Dan
<p><br></p>