So far, so good… After that it took me about a week or so working in small bits using a USB-Serial cable and a Null Modem to verify what I was sending and then once I got my carriage return correct, it started working. I hooked it up and the NodeMCU stayed powered up. I spoke to an engineer where I work, and he thought I might need a TTL to RS232 Converter.
Scrivener serial number name amazon serial#
First I noticed that if I hooked up the NodeMCU RX, TX, GND directly to the Integra’s Serial Port, the NodeMCU seemes to power down almost as if there was a short. It took me a while, but I do have this working on an Integra/Onkyo Receiver using a NodeMCU and esphome. Feel free to message me if you have any more problems and I can send you my node red flows. I ended up just calling McIntosh and asking them for the codes and they sent them over happily.
I’m not sure what exact model you have, but this looks like a sheet of commands for your unit. The purpose of the input_booleans being set is to keep track of what state the receiver is actually in and to be able to set one of the inputs via the Lovelace UI.
Scrivener serial number name amazon software#
You will see in search results you will directly see your product keys, copy them, and paste them into your software text field. I did have to set up individual channels/IFTTT commands for each type of command (volume number vs. Nero express 94FBR ) google search results. In a second Node-Red flow I have the incoming MQTT messages from beebotte JSONified in a function node so I can filter the source, set the volume, etc. This only applies to machines running the platform covered by your licence (you cannot use a Mac serial number with the Windows version or vice versa, because the Mac and Windows versions are separate development efforts). I chose to broker the message to MQTT to then send on to HASSIO.
Request - where the settings are [, POST, application/json, body: ). I can control all the receiver variables from my Lovelace UI.įor voice control, I have IFTTT capturing certain commands to my google home (via Google Assistant “IF you say…”, Then Make a Web I ended up having to set those values as global values so my other flows could access them, and so they wouldn’t be reset. In Node-Red I set up a serial port to listen to what was coming out of the receiver, and then set up some function nodes to filter out the commands I wasn’t interested in (like the current surround settings) and used the information I got out of that to set some input_booleans (like which input is currently set). I picked up a serial (RS232) to USB cord and ran it from my RPi 3 to my pre-amp