Yes, you can use this for creating a PR as you have already done. I don't have any COVR-C1200 devices so I can't test firmware.
I am using the COVR-P2500 with OWRT Snapshot.
When restarting services or rebooting, plc looses connection until I reconnect using pbc.
Does someone has an idea how the connection could be established automatically. With DLink firmware it worked.
(AVM Powerline Apdapter paired with COVR 2500.
Looks like the information is not stored in the config)
Would be glad for some advice.
Official OpenWrt builds typically will not touch any PLC configuration by default.
For most PLC devices with OpenWrt, this means the PLC setup is done by the user prior to flashing OpenWrt, and the settings are no longer touched afterwards. This works for devices with a dedicated SPI NOR flash for the PLC chip, which stores the firmware and configuration.
With COVR-P2500 devices, the PLC firmware and config is sent to the PLC chip by the Wireless SoC each time PLC is being reset (there is no dedicated non-volatile memory), this is done by an init script and the utilities from the plc-tools package.
An example for such a script and further instructions can be found in the wiki:
[OpenWrt Wiki] D-Link COVR-P2500 A1
Another more simple example would be something I made for experiments with gluon long time ago (here the passphrase is hardcoded to "hannover.freifunk.net" rather than being stored in uci, you can change it there in the script; you still need the firmware blob though):
openwrt/target/linux/ath79/generic/base-files/etc/init.d/plc at c823fd737cf17418417019452a1fba1f10de383e · s-2/openwrt · GitHub
If your other devices are setup using the same passphrase (either by the manufacturer utility, or by using the default from the device label, which looks something ike XXXX-XXXX-XXXX-XXXX), you don't need push button connect anymore.
1 Like
Great! Thank you so much. This helps a lot.