One of the most requested features is a ad-hoc method for pimatic. You can allmost do anything withe API to acomplish some sort of ad-hoc network. But is a second pi/pimatic allwaus needed ?
At the moment I’m fiddling with the homeduino-esp8266-node, but need to solder my level shifter first.
Then it crossed my mind. If we could ad a RF sender to the current homeduino-esp8266-node, setup a TCP server on the ESP it should be possible to let pimatic talk to the ESP module.
Currently the homeduino-esp8266-node will detect RF network and when it looks like a valid protocol it is transmitted over the API to the homeduino plugin. The homeduino plugin will analyze the bits to determine if it is a known protocol and if so … do some stuff.
How about reversing this?
Add a option to the homeduino that some sort of device is handled by the homeduino-esp8266-node. When this device is triggered (for example: ON) it is not passed to the arduino (connected to the pi) but the bits are passed to the ESP through the TCP server. The ESP receives the entire protocol in bits and all it has to do is blast it in the air with the connected RF sender.
Whenever a new protocol is added to the homeduino plugin , you can send it to the homeduino-esp8266-node, because same as receiving : it doesn’t need any knowledge about the protocols.
I don’t have the skills to accomplish this, but perhaps someone can start with this idea ?