General Discussion

@tsunami My setup is max 50m radius and 433MHz standard power RFM69s so a small 1/4 wave whip works reliably even from a below ground pump chamber 10m away. Your 915MHz at 200m SHOULD work on 1/4 wave if obstacle free line of sight, but you could try a 2.4GHz Wifi router at one location and use a mobile at the other to test if you can see the router. I can see at least 3 neighbouring routers identified on my mobile from over 40m away through masonry, 10 on the laptop, so it's a simple enough test. If you can see the router on either, 915MHz should be rock solid with a simple whip and no need of directional antenna.

Perhaps a bit off the wall, but if the objective is an email out, are GSM signals strong enough even at another high point which does afford radio line of sight to the objectives? Used this many years ago for remote monitoring, in one case the GSM atop a 5m pole with a wind generator attached topping up a pair of batteries, so completely self sufficient. Links to the metering points were low power RF, the landowner had no objections. Only problems encountered were vandals climbing the pole, solved by a good coat of Copaslip ;) , and a Stag which regularly danced on a GRP cover to a flow meter chamber, to the great amusement of the gamekeeper :laughing:

@mrhutchinsonmn you're right that the description and the sketch don't add up. They definitely need some work.

This script will be more helpful for beginners. The previous script turns on/off all relays. This one controls only the specified relay. - id: '1562092064918' alias: Power Up Relay_2.1 trigger: - entity_id: switch.relay_4_2 from: 'off' platform: state to: 'on' condition: [] action: - alias: '' data: entity_id: switch.relay_2_1 service: switch.turn_on - id: '1562093186484' alias: Power Down Relay_2.1 trigger: - entity_id: switch.relay_4_2 from: 'on' platform: state to: 'off' condition: [] action: - data: entity_id: switch.relay_2_1 service: switch.turn_off

@mfalkvidd Thank you, this should be the solution I'm locking for. Meanwhile I found the config-description...

@royson84 Hiya. Depending on cost and shipping, I might be interested in your stuff.

Hi, So as I see it I would need to use the hardware serial for the connection to the heatpump and then create a software serial for debug messages. So something like this: #include <SoftwareSerial.h> SoftwareSerial mySerial(10, 11); // RX, TX // Enable debug prints #define MY_DEBUG #define MY_DEBUGDEVICE mySerial #define MY_BAUD_RATE 9600 So the next question is how to present the heatpump to the gateway. Would you create one child id and then define each type of sensor/metric or is there a one-to-one mapping: #define CHILD_HVAC 0 MyMessage msgHvacStatu(CHILD_HVAC, V_STATUS); // Status: ON, OFF MyMessage msgHvacSTemp(CHILD_HVAC, V_TEMP); // Set Temp MyMessage msgHvacRTemp(CHILD_HVAC, V_TEMP); // Room Temp MyMessage msgHvacFanSp(CHILD_HVAC, V_HVAC_SPEED); // Fan Speed or #define CHILD_HVAC_STATUS 0 #define CHILD_HVAC_STEMP 1 #define CHILD_HVAC_RTEMP 2 #define CHILD_HVAC_FANSP 3 MyMessage msgHvacStatu(CHILD_HVAC_STATUS, V_STATUS); // Status: ON, OFF MyMessage msgHvacSTemp(CHILD_HVAC_STEMP, V_TEMP); // Set Temp MyMessage msgHvacRTemp(CHILD_HVAC_RTEMP, V_TEMP); // Room Temp MyMessage msgHvacFanSp(CHILD_HVAC_FANSP, V_HVAC_SPEED); // Fan Speed

MQ are always a bad choice, saturate air around with any gas and they will react ... Mics are used by sensely, but even them aren ot calibrated... and they are a hell to get working even when you have the pins soldered to them.

@yveaux said in MY_RF24_IRQ_PIN on ESP8266 GW: True, and next it doesn't use it? ;-) This could be reformulated as an affirmative sentence. I cut the bridge wiring and continued working as nothing happened.

@skywatch My pleasure

@mfalkvidd Today it did some real testing with the actual setup (not a test node) and it is all working really well so far. I was expecting to have to use limit switches to detect up and down limits, with microswitches to provide emergency power cut out to the motors if it overran. I even considered timing the motion too (done this with Crestron systems and curtains in the past). But I have had two really great surprises...... The little stepper motors, when set within their comfort zone, are very precise. It looks like just counting steps is all that is required. The steppers draw just 77mA when opening the blind. This is such good news for me as solar powered blinds (with li-ion or lead acid battery) will last all year! Big thanks to you all for the hints and finding where I mis-understood. It won't be easy, but I will get there in the end. ;)

@pihome awesome, thanks heaps! I'll check it that video later today 👍

thanks all the design has changed I plan to heat some medium and have the water pass though a head exchanger what way standing water will never be consumed later there is a commercial product called sunamp which is designed for this purpose

Wow! It is interesting! I did not know that this is possible, thanks guys, I'll try in the evening :)

@zboblamont It's not very wasteful if you're not using them for anything else anyway. I'd rather use some extra code than extra hardware.

thanks @Anticimex

@skywatch while i obviously agree with the fact that i we can best change channels, i figured that while we're at it we might as well add encryption too. I don't insist on using any specific channel. I couldn't care less what channel's being used :) That said, i tried recompiling my pi gateway wih the password and one sensor to start with using #define MY_ENCRYPTION_SIMPLE_PASSWD "mypassword" (shut off all other sensors). But i'm seeing all sorts of erroneous messages coming by, the one node is showing up on the gateway as a different ID every time. I'll whip up a simple serial gateway next time i get the chance and try to use #define MY_ENCRYPTION_SIMPLE_PASSWD "mypassword" on both to see if the problem lies with how i configure the pi gateway THanks for all the input everyone so far