Best posts made by DirkB19

Hi,

Great news !
I've tested the DaikinHeatpumpIR library and I can report that it works with my Daikin Heatpump, type RXS25G2V1B
FVXS25FV1B
the remote is ARC452A1

I'm really happy that it works and would like to say thank you to the dev's !
Finally I will be able to start some real energy saving by controlling the Daikin heatpump based on conditions like presence, outside temp, (google)-calendar, and heath generated from a second central heating system (allowing me to choose most economic heathing source).

I already have a Nano based sensor node (near the Daikin unit) for PIR motion detection and DHT22 temp/humidity, so hopefully I can manage to integrate the simple ON/OFF via IR into the same sketch.
If not, another dedicated node will be needed.
@ ToniA, do you expect problems when integrating this into the same Mysensors sketch as PIR + DHT22 ?

Bye,
DirkB

@mbj

Aha !! Finally, it WORKS
mbj gave me the right hint about using the development libraries !!!

So for others to learn from my mistakes, to get a UNO&W5100 shield to work with this MQTT Client Gateway sketch, you need your nRF24 radio connected to these pins nrs. on the W5100 shield ;
SCK -- Pin 13
MISO -- Pin 12
MOSI -- Pin 11
CS -- Pin 6
CE -- Pin 5

AND (!) you need to install the libraries from the development branch.
(I first removed the 1.5 libraries)

I just hope that installing the libraries from development branch will not get me into trouble with my the rest of my nodes (upladed with 1.5).

Is there an easy way to switch between 1.5 & development branch libraries when uploading sketches ?

Anyway, thanks to all those who responded and special thanks to mbj.

Some things are so obvious, but for newbies (like me) it can be a struggle ...

@mfalkvidd
aha ! That trick worked ! Thanks a lot !
I guess 'newbie' is the word for me

But coming back to my second question about this MQTT Client Gateway without radio and with local sensors and actuators ... will it work ?
If I have the time I will find out by trial-and-error tonight.

Bye

Ok, so I tried MQTT Client Gateway without radio and with local sensors and actuators and it works !!

The MQTT topic shows the node-id as 0, which makes sense as it is a gateway.

One thing I noticed, is that the Gateway occasionally seems to loose connection with the MQTT broker and then it shows "Attempting to connnect to MQTT broker ..." in the serial log.

I suspect that my heavy void loop() occupies the CPU too much ?
(I'm debouncing 16 contact inputs without the debounce library, without waits, without interrupts)

Also sending a relais change status from OpenHab takes a few seconds before it actually gets changed on the Mega.
OpenHab publishes right away (I see it on the MQTT monitor), but then it seems to take time before the
void receive(const MyMessage &message) picks it up and changes the relais.

I will do some more testing to see where the problem lies.
Grtz,
DirkB