Continued on Kilnageer CH temp probes...

This blog will have its detail removed in a few days... I'm just grabbing everything for now :)

(7:15) rad 13,0 / 12.0

Put zone + burner on for an hour

(7:39) rad 35.2 / 12.8

Looking at MQTT.fx no temp/humidity posting from 2x nodemcu probes left at top of hall overnight. But they weren't posting when I left them there at midnight.

(7:45) Examining them one was dead (was it continually trying to get online and so never sleeping?)  and the other was still running but doing what?

So today 1 want to:-
1) Get 3x nodemcu probes running and deployed(Liam living room & bedroom and my kitchen in extension) with spare batteries
2) Program all Sonoffs with correct firmware
3) Get shower pump on a snoff
4) Ensure temp posting script runs on startup
5) Make the MQTT databse secure (username/password)
6) Change over to MQTT based operations

This will mean that the http://192.168.1.4:1880/ui app can still be used internal to the house to control the CH.

(7:54) rad 42.5 / 14.2

Examining the probe that still had power using ESPlorer in the kitchen it it still trying to get on to Wifi (makes sense as it cannot see vodafone-2124 from there)

(8:13) rad 44.2 / 15.8
changed repeater SSID from voadafone_repeater to vodafone-2124 so I can use the same nodemcu code all over the house.

Cannot connect to wifi! Is it because of adc module?

NodeMCU custom build by frightanic.com
branch: master
commit: 4905381c004bdeaf744a60bb940c1906c2e052d4
SSL: false
modules: adc,dht,ds18b20,file,gpio,mqtt,net,node,tmr,uart,wifi
 build created on 2019-04-08 20:52
 powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)
NodeMcu temp/humidity/battery monitor v1.1 09-Apr-19
Configuring WIFI..
nil
>
PORT CLOSED

So let's drop that! If probe doesn't phone home in a hour we can report it dead and so needs battery changing

nodemcu-master-11-modules-2019-04-05-20-53-50-integer.bin

modules: adc,dht,ds18b20,file,gpio,mqtt,net,node,tmr,uart,wifi

non-debug non-adc build? nope still has adc

nodemcu-master-7-modules-2019-03-30-20-05-51-integer.bin

modules: file,gpio,net,node,tmr,uart,wifi

nodemcu-master-10-modules-2019-03-31-09-32-28-integer.bin

modules: dht,ds18b20,file,gpio,mqtt,net,node,tmr,uart,wifi

Hurrah!

Still getting same wifi issue!

NodeMcu temp/humidity/battery monitor v1.1 09-Apr-19

Configuring WIFI..

nil

> 

(8:34) Going back to code without deep sleep.

(8:34) rad 44.6 / 16.9 (my rads in Tola go up to 50+??)

I re-wedges rad temp probe. Burner has hit on/off cycle some time ago.

So after 90 mins the kitchen still isn't at 18 C. Fan heater would have done this in 10 mins!

Using old build original "tmr.alarm(1, 5000, 1, function().." "init.lua.working_kilnageer_2124_SSID" code works which didn't in later one! Happy days. Now lets just add 5 min deep sleep to it an be done!

I think we have a winner! ....

> w([==[print( "NodeMcu Kilnageer probe v1.3 09-Apr-19" )]==]);
> w([==[print( "node ID = "..node.chipid() )]==]);
> w([==[print( "time now = "..tmr.now() )]==]);
> w([==[print( "uptime = "..tmr.time() )]==]);
> w([==[print( "boot reason = "..node.bootreason())]==]);
> w([==[configWifi()]==]);
> file.close();
> dofile("init.lua");
NodeMcu Kilnageer probe v1.3 09-Apr-19
node ID = 2650591
time now = 3917433
uptime = 3
boot reason = 2
Configuring WIFI..
192.168.1.43 255.255.255.0 192.168.1.1
> ESP8266 mode is: 1
The module MAC address is: ee:fa:bc:28:71:df
IP unavaiable, Waiting...
ESP8266 mode is: 1
The module MAC address is: ee:fa:bc:28:71:df
Config done, IP is 192.168.1.43
Instantiating mqttBroker
Setting up callbacks
Making connection to MQTT broker
connected
Publishing to /temperatures/NodeMcu_2650591: 17
Publishing to /humidities/NodeMcu_2650591: 57


NodeMCU custom build by frightanic.com
branch: master
commit: 11592951b90707cdcb6d751876170bf4da82850d
SSL: false
modules: dht,ds18b20,file,gpio,mqtt,net,node,tmr,uart,wifi
 build created on 2019-03-31 09:31
 powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)
NodeMcu Kilnageer probe v1.3 09-Apr-19
node ID = 2650591
time now = 258436
uptime = 0
boot reason = 2
Configuring WIFI..
nil
> ESP8266 mode is: 1
The module MAC address is: ee:fa:bc:28:71:df
IP unavaiable, Waiting...
ESP8266 mode is: 1
The module MAC address is: ee:fa:bc:28:71:df
Config done, IP is 192.168.1.43
Instantiating mqttBroker
Setting up callbacks
Making connection to MQTT broker
connected
Publishing to /temperatures/NodeMcu_2650591: 17
Publishing to /humidities/NodeMcu_2650591: 58

So will deploy in kitchen today with fully charged battery pack and move on to sonoffs :)

(9:03) rad 45.4 / 18.1
Turning off burner and then zone

But MQTT.fx not seeing this still! Huh? As it's not among the 28 topics its seen published in the last 30 mins or so.

(9:40) Programmed 2nd nodemcu print-out all OK on laptop but MQTT.fx sees nothing! Will park up for now and try publishing to a different broker later today

(9:40) rad 31.3 / 17.9

Now to program the sonoffs!..

I have 2 large and 3 small with me (others in hot press)

(10:08) I turned CH zone and burner back on
(10:08) 25.5 / 17.2

(10:21) 33.9 / 17.1

How to program a sonoff with tasmota? I'll check my e-mails,,

12 February 2019 at 09:26:

https://ruclip.com/video/kKtLKjI4wA0/sonoff-s31-smart-plug-flashing-tasmota-and-openhab-mqtt-configuration.html

C:\Users\kilnageer\Downloads\ESPEasy_mega-20190212
In win 10 from file explore run FlashESP8266.exe from this directory
and choose COM6 and ./sonoff.bin blue LED on sonoff will
flashafterwards! :) and webserver up on Wifi as SSID "sonoff-2934"

Get video

Remember to hold button sonoff button when inserting USB dongle!

(10:45) 51.2 / 18.7
turn off CH





(10:56) 45.3 / 19.2

(12:08) My lamp works brilliantly even from MQTT Dash using:
cmnd/sonoff_5604/POWER
and message of "ON" and "OFF" (but I think caps unimportant and 1/0 also works)


(12:11) 24.2 / 17.8

(12:42) 21.2 / 17.0