Well the CH controller was offline. Not accessible on 192.168.1.4
Found not plugged in properly as it was disturbed when the shower pump plug was pulled in/out.
Once the shower pump is under Sonoff control this won't be necessary :)
http://192.168.1.4:1880/ui/ is now back online and I've started the script to report the temperatures :)
pi@mayo_rpi_zero_logger_3:~ $ ./ds18b20_temp_logger.py > /dev/null &
(I must make this run automatically on power/start up)
And here's the temp in the extension starting to build up..
And it looks like we've been hacked!
So I've turned off remote access as not password protected. Also will be replacing this Node-Red web access by an Android app to control the CH in a few days :)
Now to get NodeMcu working as a thermostat for the extension kitchen.
And to get MQTT server on 192.168.1.4. Already running but no username/password. (Must secure this for MQTT Dash android app use)
So used MQTT.fx to monitor temp reading from NodeMcu. Kitchen rad now (17:53) at 42.4 and room at 14.4 (was 11.5 and 11.8 at 14:58) and heating been on since..? Cannot tell when topic"cmnd/sonoff_5604/POWER" was posted to :(
But examining:
pi@mayo_rpi_zero_logger_3:~ $ vim /home/pi/4ca4.txt
it was around 1554739841089 which is about 17:10 according to:
https://www.unixtimestamp.com/index.php
Just cannot get NodeMcu to obtain an IP address from KILNAGEER_002 SSID :(
Kitchen rad now (18:19) at 49.5 and room at 16.8. This rad has a TRV on it which should kick in after a while keeping the kitchen at a steady temp but at that time I'd like to turn of the zone and if no other zone is active the burner,
Tried the same code in another NodeMcu... but same issue. Tried the 1st one next to the Wifi repeated and monitored Vodafone router to see if it popped up in LAN table or in MQTT.fx traffic. Nope :(
Also Vodafone router is rejecting static IP mappings! Blast!
18:28 turned of burner and zone and went for a walk (rad at 50.2 / 17.4)
So now making a ADC module build
This was built against the master branch and includes the following modules: adc, dht, ds18b20, file, gpio, mqtt, net, node, tmr, uart, wifi.
nodemcu-master-11-modules-2019-04-08-19-27-34-integer.bin
It also have developer's debug turned on. I can now see the issue. It cannot see the SSID "KILNAGEER_002"
stack traceback:
init.lua:32: in function 'configWifi'
init.lua:134: in main chunk
[C]: ?
> Heap size:36304.
EVENT_DBG(wifi_event_monitor_handle_event_cb): was called (Event:8)
scandone
no KILNAGEER_002 found, reconnect after 1s
EVENT_DBG(wifi_event_monitor_handle_event_cb): was called (Event:1)
reconnect
scandone
no KILNAGEER_002 found, reconnect after 1s
EVENT_DBG(wifi_event_monitor_handle_event_cb): was called (Event:1)
reconnect
Found not plugged in properly as it was disturbed when the shower pump plug was pulled in/out.
Once the shower pump is under Sonoff control this won't be necessary :)
http://192.168.1.4:1880/ui/ is now back online and I've started the script to report the temperatures :)
pi@mayo_rpi_zero_logger_3:~ $ ./ds18b20_temp_logger.py > /dev/null &
(I must make this run automatically on power/start up)
And here's the temp in the extension starting to build up..
And it looks like we've been hacked!
So I've turned off remote access as not password protected. Also will be replacing this Node-Red web access by an Android app to control the CH in a few days :)
Now to get NodeMcu working as a thermostat for the extension kitchen.
And to get MQTT server on 192.168.1.4. Already running but no username/password. (Must secure this for MQTT Dash android app use)
So used MQTT.fx to monitor temp reading from NodeMcu. Kitchen rad now (17:53) at 42.4 and room at 14.4 (was 11.5 and 11.8 at 14:58) and heating been on since..? Cannot tell when topic"cmnd/sonoff_5604/POWER" was posted to :(
But examining:
pi@mayo_rpi_zero_logger_3:~ $ vim /home/pi/4ca4.txt
it was around 1554739841089 which is about 17:10 according to:
https://www.unixtimestamp.com/index.php
Just cannot get NodeMcu to obtain an IP address from KILNAGEER_002 SSID :(
Kitchen rad now (18:19) at 49.5 and room at 16.8. This rad has a TRV on it which should kick in after a while keeping the kitchen at a steady temp but at that time I'd like to turn of the zone and if no other zone is active the burner,
Tried the same code in another NodeMcu... but same issue. Tried the 1st one next to the Wifi repeated and monitored Vodafone router to see if it popped up in LAN table or in MQTT.fx traffic. Nope :(
Also Vodafone router is rejecting static IP mappings! Blast!
18:28 turned of burner and zone and went for a walk (rad at 50.2 / 17.4)
19:39 (rad at 24.9 /15.9) Will trying connecting to SSID vodafone-2124 from the hallway :)
and can see the following topics being published:
/humidities/NodeMcu_2650591 59
/temperatures/NodeMcu_2650591 13
and can see the following topics being published:
/humidities/NodeMcu_2650591 59
/temperatures/NodeMcu_2650591 13
So now making a ADC module build
This was built against the master branch and includes the following modules: adc, dht, ds18b20, file, gpio, mqtt, net, node, tmr, uart, wifi.
nodemcu-master-11-modules-2019-04-08-19-27-34-integer.bin
It also have developer's debug turned on. I can now see the issue. It cannot see the SSID "KILNAGEER_002"
stack traceback:
init.lua:32: in function 'configWifi'
init.lua:134: in main chunk
[C]: ?
> Heap size:36304.
EVENT_DBG(wifi_event_monitor_handle_event_cb): was called (Event:8)
scandone
no KILNAGEER_002 found, reconnect after 1s
EVENT_DBG(wifi_event_monitor_handle_event_cb): was called (Event:1)
reconnect
scandone
no KILNAGEER_002 found, reconnect after 1s
EVENT_DBG(wifi_event_monitor_handle_event_cb): was called (Event:1)
reconnect
I can sometime see it a bit. So I moved repeater on CAT-5 cable to kitchen.
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 19:26
powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)
NodeMcu Kilnageer extension kitchen temperature monitor v0.8 02-Apr-19
Use alternate output format: 0
scandone
> Heap size:34848.
EVENT_DBG(wifi_event_monitor_handle_event_cb): was called (Event:8)
scandone
KILNAGEER_OO2 : þÿ?Nu#@xÜþ?
KILNAGEER_OO2 4 -47 e8:ab:fa:b0:c4:44 6
reconnect
scandone
no KILNAGEER_002 found, reconnect after 1s
(21:46) Reprogrammed the repeater. Now SSID is vodafone_repeater same password as vodafone-2124.
NodeMcu now connects but doesn't MQTT publish! Why? Not fully connected? Trying non-debug build
CH on at 21:55 rad 16.4 / 14.4 but I turned all other TRVs to 0. So hopefully hot water goes straight to kitchen rad.
This was built against the master branch and includes the following modules: adc, dht, ds18b20, file, gpio, mqtt, net, node, tmr, uart, wifi.
nodemcu-master-11-modules-2019-04-08-20-53-26-integer.bin
CH on at 22:54 rad 47.2 / 18.9 so turned off zone and burner.
NodeMcu now connects but doesn't MQTT publish! Why? Not fully connected? Trying non-debug build
CH on at 21:55 rad 16.4 / 14.4 but I turned all other TRVs to 0. So hopefully hot water goes straight to kitchen rad.
This was built against the master branch and includes the following modules: adc, dht, ds18b20, file, gpio, mqtt, net, node, tmr, uart, wifi.
nodemcu-master-11-modules-2019-04-08-20-53-26-integer.bin
CH on at 22:54 rad 47.2 / 18.9 so turned off zone and burner.
(23:30) some success using noder.dsleep( 10000000 ) -- 20 sec with wire between D0 and RST.
Left two probes on vodafone-2124 overnight but cannot see any readings on MQTT.fx :(
Giving up for the night.
Left two probes on vodafone-2124 overnight but cannot see any readings on MQTT.fx :(
Giving up for the night.
No comments:
Post a Comment