433 MHz ESP 32 MQTT Gateway with proper antenna

Tips for connecting the LoRa Radios:

1. Use de-coupling capacitor on power supplies (as per above other radios).
2. Carefully select: MY_RFM95_TX_POWER_DBM and MY_RFM95_MAX_POWER_LEVEL_DBM as Semtech spec states +20dBm output power is only for 1% duty cycle operations, and some modules (AI-Thinker RA-02) are only rated as +18dbm.
3. If you build a LoRa radio gateway using an ESP32 (for example), take care to provide a separate, low-noise 3.3V power supply to the radio as the on-board voltage regulator may not be able to supply enough current at the higher RF output power levels.

@cloolalang
So I have two KQ-330 on the lab bench.
So far we find:

1. carrier 132.5khz FSK modulation.
2. With two units connected together on 220 VAC mains - im seeing around 45-5- Baud, listening on an AM radio nearby the units it sounds like morse code at around 23WPM without mains, 30WPM with mains.
3. Carrier is about 5v p-p on the scope, not very clean waveform.
4. Uart is 9600 8n1
5. Transmit buffer 253 Bytes

I will test with mysensors RS485 gateway and sensor mode, with the transport time-outs increased to maybe 10000ms!
p

https://www.tindie.com/products/lps/lorawan-megabrick/

Has anyone tried this hardware with mysensors?

Cheers
P

@scalz
Hi yes, thanks for your response.

I see the E70-433NW14S is a sub-GHz 15.4 radio with PHY and MAC built in.
Has anyone taken a look at using this?
I looked at other Ebyte modules (Lora) but this seems pretty cool as its UART and so I think we can use our RS485 with it.
Maybe we finally get the previously costly zigbee-style star/mesh radios for cheaper price?

I would be very interested if anyone here has experience with this.
p

@cloolalang
Update:

1. KQ-330 F AC powerline "Modems" tested working with Mysensors RS485 serial gateway and node.
2. Line Baud rate is 100b, (Half duplex), Needs AC (50/60Hz) to work.
3. Presentation not working due to low speed, but I have entered my own mysensors.json in HA.
4. Using a Master/slave strategy whereby the gateway is polling the node/children.
5. Typical poll/response (req/send) is about 8 seconds. so yeah slow like not really more then 7 nodes/children per minute.
6. Range, you must avoid interference from AC loads, try to use the same AC phase, I have mine working over 60m but I dont know if they are on the same AC phase, Power line modems are plugged directly into wall socket or light fitting (in my garage), no multiplugs, or switch mode PSUs nearby.
7. Why? Just to see if it works.
8. Long-term results will be posted.
   Cheers
   P

@cloolalang

Other parameters not yet tested;

1. sleep or wait between sketch information and presentation messages and/or in other functions
2. MY_RS485_MAX_MESSAGE_LENGTH (40)
3. #define MY_RS485_SOH_COUNT (3)
4. MY_TRANSPORT_WAIT_READY_MS 0
5. MY_TRANSPORT_STATE_TIMEOUT_MS 2*1000ul
6. In mysensors core:

// Wait configuration reply.
	(void)wait(2000, C_INTERNAL, I_CONFIG);

I am trying to see if I can use the KQ-330 Powerline serial modems for Mysensors.
The modems have a 9600 8N1 TTL UART and the Powerline data rate is very much slower at 100 Baud.

I am using mysensors RS485 and Arduino Uno's for both node and serial gateway to Home Assistant.

So far I have managed to get the node and gateway talking however I think that because the powerline data rate is super slow compared with the 112500 Baud Home Assistant-to-Serial Gateway, and the 9600 Baud serial gateway-to-KQ330.
I am seeing issues with collisions and TRX turn around timing during presentation and registration.

As the link is so slow, I may actually just opt to use a master/slave approach with passive nodes in the end, for example a typical node-gateway heartbeat message takes about 4 seconds!

I am looking at the possibility of using Aloha on the bus however as I really don't want to throw out presentation as it really helps with setting up on Home Assistant.

So I am digging around the various transport timers and wondering how I can optimise it better for the super slow 100 baud link speed.

My first question here is regarding the collision control in mytransportrs485.cpp; line 256

while (_serialProcess()) {
		unsigned char del;
		del = rand() % 20;
		for (i = 0; i < del; i++) {
			delay(1);
			_serialProcess();
		}
		timeout--;
		if (timeout == 0) {
			// Failed to transmit!!!
			return false;
		}
	}

Im I correct to say that the 1ms delay is based on 9600 baud and I might increase it to around 100ms for 100 baud?

@cloolalang
So I have two KQ-330 on the lab bench.
So far we find:

1. carrier 132.5khz FSK modulation.
2. With two units connected together on 220 VAC mains - im seeing around 45-5- Baud, listening on an AM radio nearby the units it sounds like morse code at around 23WPM without mains, 30WPM with mains.
3. Carrier is about 5v p-p on the scope, not very clean waveform.
4. Uart is 9600 8n1
5. Transmit buffer 253 Bytes

I will test with mysensors RS485 gateway and sensor mode, with the transport time-outs increased to maybe 10000ms!
p

Re: Has anyone worked with e32-433t30d or any products related to EByte Company

I am looking into using these, but, wait... 1MHz channels:
ISM band 433MHz
Channels that you can use:
433.000
434,000
Thats it!
On no!... Why Ebyte?
P

I wonder who is interested to upgrade RF95 to support the improved Lora chips

https://forum.mysensors.org/topic/10724/which-are-the-preferred-lora-modules-now

I dont think RadioHead is doing anything on it.

So far the only one I see is Radiolib

P

Has anyone tried the mysensors protocol over PLC?
I am looking at using the KQ130/KQ330 150KHz AC power line UART modules to connect over distance without radio or special cables (RS485 etc)
https://www.youtube.com/watch?v=aGlL4eDwM-k
P