Using Max, I successfully got Crow to talk to Ansible in teletype mode, but had an initially confusing time of it. I think I missed this in the documentation, so figured Iād give a heads up in case others run into this.
Per the ansible docs, the outputs should index from 5 for the first ansible device, but this did not seem to work. For the most part sending messages like āii.ansible.trigger_pulse(5)ā and āii.ansible.trigger(5, 0)ā didnāt cause any harm, but nothing was happening on the device. On the other hand, āii.ansible.cv(5, 0)ā caused the 4th trigger light to glow and the device locked up and a reboot was required.
What I found was Crow indexes the first ansibleās outputs from 0-3 rather than being indexes 5-8 when called from teletype. So the messages that worked were āii.ansible.trigger_pulse(0)ā to cause output on the first trigger. I donāt have a second ansible in my rack currently to test if a second unit picks up at 4-8, but I got Ansible to play nicely using the lower indexes. Can anyone else confirm that out of range ii.ansible.cv commands lock up their unit?
It makes sense to index Ansibleās outputs from Crow at 0 where Teletype picks up after its 4 outputs, but perhaps a note could be added to clarify the distinction between referencing these outputs on Teletype vs. Crow.
