Alternative software


#21

these are all the relevant logs, errors and warnings

    Oct 16 15:19:30 iothermostat NetworkManager[215]: <info>  [1539699570.1009] device (wlan0): supplicant interface state: disabled -> inactive
Oct 16 15:19:30 iothermostat NetworkManager[215]: <info>  [1539699570.0663] device (wlan0): supplicant interface state: inactive -> disabled
Oct 16 15:19:30 iothermostat NetworkManager[215]: <info>  [1539699570.0013] device (wlan0): set-hw-addr: set MAC address to E6:45:9C:E7:FE:25 (scanning)
Oct 16 15:14:14 iothermostat NetworkManager[215]: <info>  [1539699254.1451] device (wlan0): supplicant interface state: disabled -> inactive
Oct 16 15:14:14 iothermostat NetworkManager[215]: <info>  [1539699254.1425] device (wlan0): supplicant interface state: inactive -> disabled
Oct 16 15:14:14 iothermostat NetworkManager[215]: <info>  [1539699254.0453] device (wlan0): set-hw-addr: set MAC address to 06:A1:C6:1C:26:67 (scanning)
Oct 16 15:08:58 iothermostat NetworkManager[215]: <info>  [1539698938.0814] device (wlan0): supplicant interface state: disabled -> inactive
Oct 16 15:08:58 iothermostat NetworkManager[215]: <info>  [1539698938.0708] device (wlan0): supplicant interface state: inactive -> disabled
Oct 16 15:08:57 iothermostat NetworkManager[215]: <info>  [1539698937.9939] device (wlan0): set-hw-addr: set MAC address to 1A:22:68:69:0C:4E (scanning)
Oct 16 15:03:42 iothermostat NetworkManager[215]: <info>  [1539698622.0903] device (wlan0): supplicant interface state: disabled -> inactive
Oct 16 15:03:42 iothermostat NetworkManager[215]: <info>  [1539698622.0737] device (wlan0): supplicant interface state: inactive -> disabled
Oct 16 15:03:41 iothermostat NetworkManager[215]: <info>  [1539698621.9974] device (wlan0): set-hw-addr: set MAC address to 26:77:11:19:26:0A (scanning)
Oct 16 14:58:26 iothermostat NetworkManager[215]: <info>  [1539698306.0861] device (wlan0): supplicant interface state: disabled -> inactive
Oct 16 14:58:26 iothermostat NetworkManager[215]: <info>  [1539698306.0793] device (wlan0): supplicant interface state: inactive -> disabled
Oct 16 14:58:25 iothermostat NetworkManager[215]: <info>  [1539698305.9994] device (wlan0): set-hw-addr: set MAC address to B6:2B:8B:B7:6D:AC (scanning)
Oct 16 14:53:10 iothermostat NetworkManager[215]: <info>  [1539697990.1461] device (wlan0): supplicant interface state: disabled -> inactive
Oct 16 14:53:10 iothermostat NetworkManager[215]: <info>  [1539697990.1340] device (wlan0): supplicant interface state: inactive -> disabled
Oct 16 14:53:10 iothermostat NetworkManager[215]: <info>  [1539697990.0501] device (wlan0): set-hw-addr: set MAC address to 6A:A1:D9:34:C2:18 (scanning)
Oct 16 14:47:54 iothermostat NetworkManager[215]: <info>  [1539697674.1062] device (wlan0): supplicant interface state: disabled -> inactive
Oct 16 14:47:54 iothermostat NetworkManager[215]: <info>  [1539697674.0915] device (wlan0): supplicant interface state: ready -> disabled
Oct 16 14:47:53 iothermostat NetworkManager[215]: <info>  [1539697673.9992] device (wlan0): set-hw-addr: set MAC address to 4E:F2:73:8A:9C:32 (scanning)
Oct 16 14:42:10 iothermostat NetworkManager[215]: <info>  [1539697330.3687] manager: startup complete
Oct 16 14:42:09 iothermostat NetworkManager[215]: <info>  [1539697329.2512] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Oct 16 14:42:09 iothermostat NetworkManager[215]: <info>  [1539697329.2487] device (wlan0): supplicant interface state: starting -> ready
Oct 16 14:42:09 iothermostat NetworkManager[215]: <info>  [1539697329.2026] sup-iface[0x1d409d0,wlan0]: supports 5 scan SSIDs
Oct 16 14:42:08 iothermostat NetworkManager[215]: <info>  [1539697328.5394] device (wlan0): supplicant interface state: init -> starting
Oct 16 14:42:08 iothermostat NetworkManager[215]: <info>  [1539697328.5372] supplicant: wpa_supplicant running
Oct 16 14:42:07 iothermostat NetworkManager[215]: <info>  [1539697327.9347] ovsdb: Could not connect: No such file or directory
Oct 16 14:42:07 iothermostat NetworkManager[215]: <info>  [1539697327.5126] device (wlan0): set-hw-addr: set MAC address to F2:EC:82:85:14:AD (scanning)
Oct 16 14:42:06 iothermostat NetworkManager[215]: <info>  [1539697326.8564] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 16 14:42:06 iothermostat NetworkManager[215]: <info>  [1539697326.7436] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/2)
Oct 16 14:42:06 iothermostat NetworkManager[215]: <info>  [1539697326.7056] device (wlan0): driver supports Access Point (AP) mode
Oct 16 14:42:06 iothermostat NetworkManager[215]: <info>  [1539697326.6293] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Oct 16 14:42:06 iothermostat NetworkManager[215]: <info>  [1539697326.6051] device (lo): carrier: link connected
Oct 16 14:42:06 iothermostat NetworkManager[215]: <info>  [1539697326.5702] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.14.1dev+13+g0d3234478-1/libnm-device-plugin-wifi.so)
Oct 16 14:42:06 iothermostat NetworkManager[215]: <info>  [1539697326.5387] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.14.1dev+13+g0d3234478-1/libnm-device-plugin-ovs.so)
Oct 16 14:42:06 iothermostat NetworkManager[215]: <info>  [1539697326.5196] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.14.1dev+13+g0d3234478-1/libnm-device-plugin-wwan.so)
Oct 16 14:42:06 iothermostat NetworkManager[215]: <info>  [1539697326.5027] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.14.1dev+13+g0d3234478-1/libnm-device-plugin-team.so)
Oct 16 14:42:06 iothermostat NetworkManager[215]: <info>  [1539697326.0015] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.14.1dev+13+g0d3234478-1/libnm-device-plugin-bluetooth.so)
Oct 16 14:42:05 iothermostat NetworkManager[215]: <info>  [1539697325.8903] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.14.1dev+13+g0d3234478-1/libnm-device-plugin-adsl.so)
Oct 16 14:42:05 iothermostat NetworkManager[215]: <info>  [1539697325.8690] dhcp-init: Using DHCP client 'internal'
Oct 16 14:42:05 iothermostat NetworkManager[215]: <info>  [1539697325.8572] manager: Networking is enabled by state file
Oct 16 14:42:05 iothermostat NetworkManager[215]: <info>  [1539697325.8346] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Oct 16 14:42:05 iothermostat NetworkManager[215]: <info>  [1539697325.8297] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file
Oct 16 14:42:05 iothermostat NetworkManager[215]: <info>  [1539697325.7552] keyfile: new connection /etc/NetworkManager/system-connections/IOTHERMOSTAT (f3241424-ccf5-4180-86de-decf1c7b113b,"IOTHERMOSTAT")
Oct 16 14:42:05 iothermostat NetworkManager[215]: <info>  [1539697325.6541] settings: Loaded settings plugin: NMSIbftPlugin ("/usr/lib/NetworkManager/1.14.1dev+13+g0d3234478-1/libnm-settings-plugin-ibft.so")
Oct 16 14:42:05 iothermostat NetworkManager[215]: <info>  [1539697325.6384] settings: Loaded settings plugin: NMSKeyfilePlugin (internal)
Oct 16 14:42:04 iothermostat NetworkManager[215]: <info>  [1539697324.6650] manager[0x1d73010]: rfkill: WWAN hardware radio set enabled
Oct 16 14:42:04 iothermostat NetworkManager[215]: <info>  [1539697324.6630] manager[0x1d73010]: rfkill: WiFi hardware radio set enabled
Oct 16 14:42:04 iothermostat NetworkManager[215]: <info>  [1539697324.6510] rfkill0: found WiFi radio killswitch (at /sys/devices/platform/soc/20300000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/rfkill0) (driver brcmfmac)
Oct 16 14:42:04 iothermostat NetworkManager[215]: <info>  [1539697324.5959] dns-mgr[0x1d7b800]: init: dns=systemd-resolved, rc-manager=symlink, plugin=systemd-resolved
Oct 16 14:42:04 iothermostat NetworkManager[215]: <info>  [1539697324.5770] hostname: hostname changed from (none) to "iothermostat"
Oct 16 14:42:04 iothermostat NetworkManager[215]: <info>  [1539697324.5679] hostname: hostname: using hostnamed
Oct 16 14:42:02 iothermostat systemd[1]: Started Network Manager.
Oct 16 14:42:02 iothermostat NetworkManager[215]: <info>  [1539697322.5781] manager[0x1d73010]: monitoring kernel firmware directory '/usr/lib/firmware'.
Oct 16 14:42:02 iothermostat NetworkManager[215]: <info>  [1539697322.5465] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Oct 16 14:42:02 iothermostat NetworkManager[215]: <info>  [1539697322.3112] wifi-nl80211: (wlan0): using nl80211 for WiFi device control
Oct 16 14:42:02 iothermostat NetworkManager[215]: <info>  [1539697322.2846] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Oct 16 14:42:02 iothermostat NetworkManager[215]: <info>  [1539697322.2748] NetworkManager (version 1.14.1dev+13+g0d3234478-1) is starting... (for the first time)
Oct 16 14:42:01 iothermostat systemd[1]: Starting Network Manager...





Oct 16 14:42:03 iothermostat systemd[1]: Failed to start Mosquitto MQTT Broker daemon.
Oct 16 14:41:58 iothermostat kernel: brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Crea
Oct 16 14:41:54 iothermostat kernel: [vc_sm_connected_init]: failed to initialize shared memory service
Oct 16 14:41:54 iothermostat kernel: vc_vchi_sm_init: failed to open VCHI service (-1)
Oct 16 14:41:54 iothermostat kernel: Error: Driver 'sdhost-bcm2835' is already registered, aborting...
Oct 16 14:41:54 iothermostat kernel: No CPU information found in DT


Oct 16 14:42:04 iothermostat kernel: kauditd_printk_skb: 25 callbacks suppressed
Oct 16 14:42:03 iothermostat systemd[1]: Failed to start Mosquitto MQTT Broker daemon.
Oct 16 14:42:03 iothermostat systemd[1]: mosquitto.service: Failed with result 'exit-code'.
Oct 16 14:42:03 iothermostat systemd[1]: mosquitto.service: Start request repeated too quickly.
Oct 16 14:42:03 iothermostat systemd[1]: mosquitto.service: Failed with result 'exit-code'.
Oct 16 14:42:03 iothermostat systemd-backlight[225]: Maximum brightness is 0, ignoring device.
Oct 16 14:42:02 iothermostat systemd-udevd[172]: Process '/usr/bin/crda' failed with exit code 249.
Oct 16 14:42:02 iothermostat systemd[1]: mosquitto.service: Failed with result 'exit-code'.
Oct 16 14:42:01 iothermostat systemd[1]: mosquitto.service: Failed with result 'exit-code'.
Oct 16 14:42:01 iothermostat systemd[1]: mosquitto.service: Failed with result 'exit-code'.
Oct 16 14:42:01 iothermostat systemd-udevd[169]: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.
Oct 16 14:42:00 iothermostat kernel: fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned.
Oct 16 14:42:00 iothermostat systemd[1]: mosquitto.service: Failed with result 'exit-code'.
Oct 16 14:42:00 iothermostat kernel: fbtft: module is from the staging directory, the quality is unknown, you have been warned.
Oct 16 14:42:00 iothermostat kernel: ads7846 spi0.1: spi0.1 supply vcc not found, using dummy regulator
Oct 16 14:41:59 iothermostat kernel: kauditd_printk_skb: 1 callbacks suppressed
Oct 16 14:41:58 iothermostat kernel: brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Crea
Oct 16 14:41:57 iothermostat kernel: FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Oct 16 14:41:54 iothermostat kernel: snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
Oct 16 14:41:54 iothermostat kernel: mmc0: host does not support reading read-only switch, assuming write-enable
Oct 16 14:41:54 iothermostat kernel: mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Oct 16 14:41:54 iothermostat kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Oct 16 14:41:54 iothermostat kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Oct 16 14:41:54 iothermostat kernel: mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Oct 16 14:41:54 iothermostat kernel: [vc_sm_connected_init]: failed to initialize shared memory service
Oct 16 14:41:54 iothermostat kernel: vc_vchi_sm_init: failed to open VCHI service (-1)
Oct 16 14:41:54 iothermostat kernel: Error: Driver 'sdhost-bcm2835' is already registered, aborting...
Oct 16 14:41:54 iothermostat kernel: Init: Power Port (0)
Oct 16 14:41:54 iothermostat kernel: Init: Port Power? op_state=1
Oct 16 14:41:54 iothermostat kernel: WARN::hcd_init_fiq:486: MPHI regs_base at 0xf0006000
Oct 16 14:41:54 iothermostat kernel: WARN::hcd_init_fiq:460: FIQ ASM at 0x8085d194 length 36
Oct 16 14:41:54 iothermostat kernel: WARN::hcd_init_fiq:459: FIQ on core 0 at 0x8085ce14
Oct 16 14:41:54 iothermostat kernel: FIQ FSM acceleration enabled for :
                                     Non-periodic Split Transactions
                                     Periodic Split Transactions
                                     High-Speed Isochronous Endpoints
                                     Interrupt/Control Split Transaction hack enabled
Oct 16 14:41:54 iothermostat kernel: WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0x9e114000 dma = 0x5e114000 len=9024
Oct 16 14:41:54 iothermostat kernel: Dedicated Tx FIFOs mode
Oct 16 14:41:54 iothermostat kernel: OTG VER PARAM: 0, OTG VER FLAG: 0
Oct 16 14:41:54 iothermostat kernel: Multiprocessor Interrupt Enhancement - disabled
Oct 16 14:41:54 iothermostat kernel: Periodic Transfer Interrupt Enhancement - disabled
Oct 16 14:41:54 iothermostat kernel: Using Buffer DMA mode
Oct 16 14:41:54 iothermostat kernel: Finished setting default values for core params
Oct 16 14:41:54 iothermostat kernel: Setting default values for core params
Oct 16 14:41:54 iothermostat kernel: Core Release: 2.80a
Oct 16 14:41:54 iothermostat kernel: hw perfevents: no irqs for PMU, sampling events not supported
Oct 16 14:41:54 iothermostat kernel: No CPU information found in DT

i’m not sure it can help


#22

Thanks for the log. Are these the complete contents?

I notice the nl80211 driver being loaded successfully, which didn’t work on my hardware so I assume your Wifi device differs from mine (which uses dkms 8188eu driver with wext).

These log entries actually look fine except for NetworkManager not continuing with “policy: auto-activating connection ‘IOTHERMOSTAT’” after the “state change: unavailable -> disconnected”. I have to look into this. You don’t happen to have another network interface that did make a connection?

Only thing I can think of right now try is changing the mode in /etc/NetworkManager/system-connections/IOTHERMOSTAT from ‘adhoc’ to ‘ap’ or to blank.

edit:
Possibly in the [connection] section the following line

autoconnect=true

is required in

/etc/NetworkManager/system-connections/IOTHERMOSTAT

If that doesn’t work you can try adding a file

/etc/NetworkManager/system-connections/YOURSSID

with

[connection]
id=YOURSSID
uuid=5dda3496-4e8d-49dd-995b-69483bcfc9b8
type=wifi
autoconnect-priority=10
autoconnect=true
permissions=
timestamp=1539698191

[wifi]
mac-address=F2:EC:82:85:14:AD
mac-address-blacklist=
mode=infrastructure
seen-bssids=00:00:00:00:00:00;
ssid=YOURSSID

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=Your password phrase

[ipv4]
dns-search=
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto

and make sure the files in /etc/NetworkManager/system-connections are readwrite only for root, otherwise NM will skip them!


#23

I just tried all these options with no success I might have to try and build it myself manually .I can put all of the Log file on here if that helps ? those were all of the Network manager , errors and warning entries .


#24

That’s unfortunate. Let’s have a look at the complete log.
Can you also post the output of:

sudo ls -la /SDCARDROOT/etc/NetworkManager/system-connections/

Since everything except NM seems to be working, I’d suggest to only reconfigure NM by booting the SD card on a Raspberry Pi with LAN, ssh into the machine, connecting the dongle and going through steps 19-22 outlined in https://github.com/jbaans/iothermostat/wiki/Install-Arch-Linux-ARM-with-Wifi-on-Raspberry-Pi-Zero,B


#25

The limit count on the forum stops me putting more than 1/5 of the log is there another way to get it to you?

output for system-connections

    total 16
    drwx------ 2 root root 4096 Nov  6 21:32 .
    drwxr-xr-x 7 root root 4096 Oct 10 17:36 ..
    -rw------- 1 root root  555 Nov  6 18:58 Harrisons2.4GHZ
    -rw------- 1 root root  375 Nov  6 21:32 IOTHERMOSTAT

I have a Pi 3 lying around I can use that if it will work ?
I dont have a dongle the Pi used for my HestiaPi is the Pi zero W


#26

#27

thanks @HestiaPi

https://pastebin.com/9u0BRdeb

I put a timer of a week on the paste @janbonne

for the sake of Debugging I’ve tried again with a fresh image, edited the files and put my WiFi credentials no such luck . I did start to build it manually until I realized that I cant use the PI3 to use the Os as its different arm architecture . This explains why when I tried to boot the image on the Pi3 with an ethernet cable nothing happened. I’m stumped now as to what to do . I could order a Pi1 I guess.


Want a non-web interface! Can someone help me?
#28

Ok, I’ve examined your logfile and everything really seems fine - except for the wlan0 being inactive:

Oct 16 14:58:26 iothermostat NetworkManager[215]: <info>  [1539698306.0861] device (wlan0): supplicant interface state: disabled -> inactive
Oct 16 14:58:26 iothermostat NetworkManager[215]: <info>  [1539698306.0793] device (wlan0): supplicant interface state: inactive -> disabled

This and reading up on networking in arch makes me think the interface wlan0 requires an explicit activation.
So we’ll have to run at leasr one of the (but lets run both) commands:

ip link set wlan0 up
nmcli -p con up id “IOTHERMOSTAT”

at the appropriate time.

I’m thinking of creating a unit file with timer (see https://unix.stackexchange.com/questions/138281/arch-linux-run-script-a-minute-after-boot) and have that run a little script with the above line. The unit file (and probably timer) can be ‘enabled’ offline (!) manually according to https://unix.stackexchange.com/questions/157816/what-does-systemctl-enable-netctl-service-do#159293

I should have time to implement this later this week, but perhaps you can get it to run.


#29

I will certainly give it a try, If all else should fail I could always install IOThermostat on top of a Raspbian image although it would be interested to get it operation on the Arch install , thanks for all your input so far @janbonne
I’ve not been 100% committed to getting the thermostat working , I’ve spent the last few days flashing a dozen Sonoff’s for my Home automation lighting but I’ll be finished in a few days and back on track .


#30

I obtained a Pi-Zero W and reproduced the problem. Above I was close however incorrect:
The IOTHERMOSTAT profile needs the correct MAC address.
If you know it you can fill it in and reboot.
I’ll work on some script to do this automatically.


#31

This is great news, I will give it a go on monday.


#32

Please see https://github.com/jbaans/iothermostat/issues/1 for a fix.


Integrate IOThermostat with home automation
#33

Ok so I got it up and running and I thought I would give you some feedback from what I did and a few questons I have .

  1. when I followed the fix instructions and

wget https://github.com/jbaans/iothermostat/blob/master/configuration_files/home/setupFallbackWifi.sh

and

wget https://github.com/jbaans/iothermostat/blob/master/configuration_files/etc/systemd/system/setupFallbackWifi.service
but I still couldn’t get the hotspot to work. I then noticed that it didn’t download the contents of the file from github but the html of the page itself I copied the contents from the page manually using nano and finally after power cycling I got the hotspot to work .

  1. when I copied the file into setupfallBackWifi.sh into /home/iothermostat I had to use sudo as I didnt have permission to access the /iothermostat directory, when mounting the SD card on my laptop. I had to then chgrp and chown of files back from root to user 1001 ( aka iothermostat) not sure if this would have affected the outcome but it worked for me .

3)when following the instructions to upgrade it suggests

download and copy iothermostat/* to /home/iothermostat/iothermostat/

on my image it shows the directory as

iothermostat-python

  1. out of interest I have a Mqtt broker on my Openhab but I notice iothemostat has its own broker I take it this is essential for the web interface functionality ? I was wondering whether it is possible to have the client on iothermostat publish the temp/humidity/pressure to the openhab broker ?

5)On the topic of Mqtt , we discussed incorporating external temps sent from openhab connected sensors to the iothemostat I guess this is all related really, is it possible for 2 devices with brokers to publish to each other?

6)when touch the advanced.php icon on the touchscreen its not always responsive it can take several attempts to get it to the advanced page . Is this because of the touchscreen accuracy? all other icons on screen respond perfectly .

  1. I notice commits to the files in

configuration_files/etc/lighttpd is this something that I should copy across as its not something updated in the current image ?

  1. I am using 16Gb Sdcards on the iothermostats , however the system is only using 7.0gb any idea why?

     Filesystem      Size  Used Avail Use% Mounted on
     dev             232M     0  232M   0% /dev
     run             239M  260K  239M   1% /run
     /dev/mmcblk0p2  7.0G  2.1G  4.5G  32% /
     tmpfs           239M  4.0K  239M   1% /dev/shm
     tmpfs           239M     0  239M   0% /sys/fs/cgroup
     tmpfs           239M  8.0K  239M   1% /tmp
     /dev/mmcblk0p1  100M   27M   74M  27% /boot
     tmpfs            48M  4.0K   48M   1% /run/user/1001
    
  2. i have a recurring error

Nov 12 18:22:13 iothermostat python[353]: IOThermostat: [Errno 2] No such file or directory: '/home/YOURUSERNAME/iothermostat.csv'

should I create the log file for it ?

I really impressed so far with the image, its quick to load simple in design and I like the web interface setup for the scheduler . :+1:

now if I can incorporate the temp reading from openhab :arrow_forward: iothermostat and the humidity and pressure readings from iothemostat :arrow_forward: openhab, or even control the thermostat from from my openhab setup (more discussion on that another time on a different thread ) it would be perfect .

thanks again @janbonne for your hard work


#34

Hi,

This is great the feedback. Thanks for trying and for your :+1: :slight_smile:

1-3: I’ve updated the GIT to fix the problems you mentioned, and some more.

4: IOThermostat can use any MQTT broker, but it requires persistence and a few rules are setup for security.
Probably the best way to go is to make python report to the openhab broker in addition to its normal operation (a few simple connect client and publish lines).

5: For external temperature feed, IOThermostat python will have to subscribe to the broker and topic the data is published on, watch changes and update its temperature variable accordingly.

  1. I hoped it was just my device, but apparently it is a more general problem. Not sure if drivers can fix this. Any experience from the HestiaPi staff here?

  2. Yes this improves security

  3. The image has a partition table for 8GB. You can expand it, see for example here:
    https://raspberry-hosting.com/en/faq/how-expand-arch-linux-root-partition

  4. Please edit iothermosat.py DATALOGFILE variable (updated in GIT)

All control signals go via MQTT. So if you can make OpenHAB send (and receive) the right values, it will work. Have a look at mqttconf.js and topics.py. To get a sense of the data, open the web console of your browser when you’re in the webinterface.


#35

Great work on the fixes impressive turnaround time , really like the upgrade script as well. Everything is working great and Ill expand the partition when I get a moment , thanks for all the advice and the improvements .
As for questions 4,5 Ill start a new thread to ask my questions rather than bog down this thread.


#36

In the mean time I’ve put a new image with many bugs fixed online, see github.


#37

how can I can temporarily change the 25°C limit on the schedule web interface, one of HestiaPi’s needs to be set to 27°C minimum or it will turn off before the rooms have had chance to get warm


#38

Edit line 22:

var MAX_TEMPERATURE = 25;

in http/scripts/scheduleUI.js

Note: an iothermostat GIT update will overwrite this. You could do a chmod -w to prevent updates on this file (potentially breaks things in future).


#39

That’s ok I don’t mind having to edit it after every update , until I sort out the external temp sensors

Thanks for help