Version 4 Testing

[theyosh]

There is a early release of version 4. So you can test it and play around. All issues, questions or other things can be discussed here.

The installation is a bit different, so please take an extra look at the installation link below.

Release: https://github.com/theyosh/TerrariumPI/releases/tag/4.0.0-alpha.1
Installation: https://github.com/theyosh/TerrariumPI/tree/4.x.y.z#installation
Discussion: #539
Features: https://github.com/theyosh/TerrariumPI/projects/3

Below is a list of tested hardware. If you have tested some hardware which is not bold, please inform here that the device is working. I am not able to test all hardware.

Updating code after changes:

• sudo service terrariumpi stop (this can take a while...)
• cd TerrariumPI
• git pull
• sudo service terrariumpi start

Clear browser cache, or reload the page with 'Shift' key pressed

Manual starting:

• ssh to the pi
• cd TerrariumPI
• source venv/bin/activate
• python terrariumPI.py

Now the software is running. You can stop it with Ctrl-C command. If you want to keep it running in the background, use screen.

Known issues:

• Notification center is not working yet.

Tested relay hardware:

• BrightPI (dimmer) @theyosh
• DC Dimmer
• Denkovi Relay v2 (16 sockets) @PhoenixNP
• Denkovi Relay v2 (4 sockets) @PhoenixNP
• Denkovi Relay v2 (8 sockets) @PhoenixNP
• Energenie LAN @theyosh
• Energenie RF
• Energenie USB @theyosh
• External script switch @wolli1234
• FTDI devices @theyosh
• GPIO devices @theyosh
• GPIO devices (inverse) @theyosh
• IRF520 Dimmer @theyosh
• Kasa Smart @ntfd0
• Meross power switches @theyosh
• NextEVO Universal AC MAINS Dimmer (MPDMv4.1) @theyosh
• PCA9685-dimmer
• Remote power switch (API)
• Sequent Microsystems 4 Relay Card @morrell7
• Sequent Microsystems 8 Relay Card Ver. 1 - 2
• Sequent Microsystems 8 Relay Card Ver. 3
• Sonoff (Tasmota) @theyosh
• WEMO Smart plug @theyosh

Tested sensor hardware:

• 1-Wire sensor @theyosh
• AM2302 sensor @morrell7
• AM2320 sensor
• AMG8833 Grid-Eye IR Thermometer sensor
• BH1750 LUX light sensor @wolli1234
• BME280 sensor @theyosh
• CCS811 sensor
• CHIRP sensor @theyosh
• COZIR CO2 Sensor
• DHT11 sensor @theyosh
• DHT22 sensor @theyosh
• HC-SR04 ultrasonic ranging sensor @theyosh
• HC-SR04P ultrasonic ranging sensor
• HTU21D sensor
• Honeywell HumidIcon HIH8000 @mikenorgate
• JSN-SR04T ultrasonic ranging sensor
• K30 CO2 Sensor @5point0
• MH-Z19 CO2 Sensor @theyosh
• MH-Z19B CO2 Sensor
• MLX90614 IR Thermometer sensor @theyosh
• Meross MS100 @theyosh
• MiFlora bluetooth sensor @theyosh
• MiTemperature bluetooth sensor @5point0
• One-Wire File System @theyosh
• Remote sensor (http/https) @theyosh
• SEN0161 PH Probe sensor (analog)
• SI7021 sensor
• Script sensor @wolli1234
• Sensirion SHT2X sensor @theyosh
• Sensirion SHT3X sensor
• VEML6075 UVA and UVB light sensor @theyosh
• YT-69 sensor (digital) @theyosh

Tested button hardware:

• Light sensor @theyosh
• Magnetic (door) button @theyosh
• Motion sensor @theyosh

Tested webcam hardware:

• Live HLS Stream
• Live Raspberry PI camera @theyosh
• Local file webcam
• Raspberry PI camera @theyosh
• Remote file webcam @theyosh
• USB camera @theyosh

[cyber-shifter]

Thanks for putting this up for us to play with! I'm going to try to check it out tonight!

[theyosh]

The installation is a bit different. So have a good look at the needed installation steps.. https://github.com/theyosh/TerrariumPI/tree/4.x.y.z#installation

[cyber-shifter]

Yeah, I saw that. The clone string was changed. I was actually going to ask about that, but then I read the installation instructions, and that answered the question.

[cyber-shifter]

might want to note that the git pull doesn't work unless you are in the TerrariumPi directory.

[morrell7]

Looks really good so far.

I had to manually install apispec after the ./install.sh
May be worth adding some clearer guidance for venv for noobs.
ie. source venv/bin/activate

I'm struggling to add the 4relay switch, the address on my l2c is 3F which in decimal is 63.
It doesn't like a non-integer and when I set it as 63 it warns the following:
Relay could not be added. Unknown attribute 'dimmer_offset'

Am I doing something wrong? Or is that not yet working?

Many thanks

[morrell7]

Will email you details this evening.

[morrell7]

Is the idea behind the weather to be a target temp/humidity for the enclosure?

Showing weather now thanks

[theyosh]

No, it is used for timers. And you could use the temperature with some tricks. But mainly to simulate sunrise and sunset when it happens. My gecko has 10 hours of light in the winter and 16 hours of light in the summer. And is done automatically based on the sunrise and sunset times during the year. So every day, the daylight period grows with 3 minutes.

[morrell7]

That's awesome, I want to set mine to somewhere in Africa so it goes with what he would have naturally.

[morrell7]

A good idea would be to allow streaming of rtsp as a webcam input.

[wolli1234]

Hey,
I'm exited to test the new version! Installer script was running without errors, but after reboot I can't ssh into the pi or reach the web interface.

Connecting the pi to a monitor it stops in the terminal when a login is required. But I can't login with pi user, it just stops after entering the password, with no further error message.

Reinstalled, and setup autologin in raspi-config before reboot, still not working.

There is an error message:

run-parts: failed to stat component /etc/update-motd.d/05-terrariumpi/05-terrariumpi: No such file or directory

[theyosh]

Is this still the case? What is the logging saying in TerrariumPI/log ? And/or /var/log/syslog ?

This is a strange behavior. Could it be that it is somehow in a reboot/restart loop?

Also, the code is changing a lot, so maybe do an update as described in the original post. Making sure you have the latest code.

[cyber-shifter]

I had this happening as well, so I tried to do the update as you described up there. It brought the system down completely. Does it initiate a restart when you tell it to start the service? Because I couldn't even SSH into it.

[cyber-shifter]

I'm still getting the offline thing happening after update. I can't check the logs right now, because it's offline and I can't connect physically.

[theyosh]

Please look at #544 especially: #544 (comment)

[cyber-shifter]

Got it! I'll do it after work.

[wolli1234]

I will just add my results in this post here:

BH1750 -> error, right now not working.

ERROR - __init__ - Sensor BH1750 LUX light sensor light named 'light bh-1750' at address '23, 1' has exception: read_i2c_block_data() missing 1 required positional argument: 'length'

ERROR - __init__ - Error updating sensor BH1750 LUX light sensor light named 'light bh-1750' at address '23, 1'. Check your hardware! Object bh1750 light named 'light bh-1750' at address '23, 1' cannot be stored in the database. IntegrityError: UNIQUE constraint failed: Sensor.id

Script Sensor -> I tried using BH1750 sensor with script instead, which is working in TP3. While adding the sensor and saving as script, a popup window shows an error like this:

"Sensor could not be added, hardware does not have a light sensor"

---

BME280 -> Working fine so far

---

CCS811 -> warning, error

WARNING - terrariumEngine - Could not take a new measurement from sensor css811 co2 named 'co2' at address '5a, 1'. Tried for 1.49 seconds. Skipping this update.

ERROR - __init__ - Error updating sensor CCS811 sensor co2 named 'co2' at address '5a, 1'. Check your hardware! Invalid reading from sensor CCS811 sensor co2 named 'co2' at address '5a, 1'

WARNING - api - Invalid reading from sensor CCS811 sensor co2 named 'co2' at address '5a, 1', retrying in 0.5 seconds...

---

External script switch -> could not be added

Using a script which is working in TP3 can't be added as external script switch in Relays.

Popup error message something like "Relay could not be added. unknown attribute dimmer ofset"

[theyosh]

The script sensors and relays should work now. Also added a script dimmer as new type. So could you test that for me?

The BH1750 could work now. As I cannot test it.

The CCS811 I want to fix after the BH1750 and script sensor/relays are working for you. One problem at a time :)

[wolli1234]

Hi theyosh!

BH1750 has new error:

ERROR   - __init__             - Error updating sensor BH1750 LUX light sensor light named 'Light Test' at address '23, 1'. Check your hardware! Invalid reading from sensor BH1750 LUX light sensor light named 'Light Test' at address '23, 1'
2021-04-13 14:43:47,427 - ERROR   - __init__             - Sensor BH1750 LUX light sensor light named 'Light Test' at address '23, 1' has exception: list indices must be integers or slices, not str

---

Using BH1750 as script instead error:

2021-04-13 14:50:52,666 - ERROR   - __init__             - Error updating sensor Script sensor light named 'light test script' at address '/home/pi/customScript/bh1750-smbus.py'. Check your hardware! Invalid reading from sensor Script sensor light named 'light test script' at address '/home/pi/customScript/bh1750-smbus.py'

WARNING - terrariumEngine      - script light named 'light test script' at address '/home/pi/customScript/bh1750-smbus.py' had problems reading a new value during startup in 1.33 seconds. Will be updated in the next round.

---

Using LED-script for relay:

2021-04-13 14:58:00,421 - ERROR - __init__ - Error changing state for relay Script relay relay named 'led test' at address '/home/pi/customScript/LED.py' to 0.0 :Error changing relay Script relay relay named 'led test' at address '/home/pi/customScript/LED.py' to state 0.0. Error: name 'subprocess' is not defined

---

Using LED-script for dimmer (not sure if I can test this for you, as I used my LED-script only as a switch in TP3:

2021-04-13 15:06:32,739 - WARNING - terrariumEngine      - Could not take a new measurement from relay script-dimmer dimmer named 'LED dimmer script' at address '/home/pi/customScript/LED.py'. Tried for 1.40 seconds. Skipping this update.
hardware.relay.terrariumRelayUpdateException: Error getting new data from relay Script dimmer dimmer named 'LED dimmer script' at address '/home/pi/customScript/LED.py'. Error: unknown
    raise terrariumRelayUpdateException(f'Error getting new data from relay {self}. Error: unknown')
  File "/home/pi/TerrariumPI/hardware/relay/__init__.py", line 159, in __get_hardware_value
    return f()
  File "/home/pi/TerrariumPI/venv/lib/python3.7/site-packages/retry/api.py", line 33, in __retry_internal
    logger)
  File "/home/pi/TerrariumPI/venv/lib/python3.7/site-packages/retry/api.py", line 74, in retry_decorator
    return caller(func, *(extras + args), **kw)
  File "/home/pi/TerrariumPI/venv/lib/python3.7/site-packages/decorator.py", line 231, in fun
    new_data = self.__get_hardware_value()
  File "/home/pi/TerrariumPI/hardware/relay/__init__.py", line 237, in update
Traceback (most recent call last):
2021-04-13 15:06:32,736 - ERROR   - __init__             - Error getting new data from relay Script dimmer dimmer named 'LED dimmer script' at address '/home/pi/customScript/LED.py'. Error: unknown
2021-04-13 15:06:32,733 - ERROR   - __init__             - Error getting new data from relay Script dimmer dimmer named 'LED dimmer script' at address '/home/pi/customScript/LED.py'. Error: name 'subprocess' is not defined
2021-04-13 15:06:32,106 - WARNING - api                  - Error getting new data from relay Script dimmer dimmer named 'LED dimmer script' at address '/home/pi/customScript/LED.py'. Error: unknown, retrying in 0.5 seconds...
2021-04-13 15:06:32,104 - ERROR   - __init__             - Error getting new data from relay Script dimmer dimmer named 'LED dimmer script' at address '/home/pi/customScript/LED.py'. Error: name 'subprocess' is not defined
2021-04-13 15:06:31,509 - WARNING - api                  - Error getting new data from relay Script dimmer dimmer named 'LED dimmer script' at address '/home/pi/customScript/LED.py'. Error: unknown, retrying in 0.5 seconds...
2021-04-13 15:06:31,507 - ERROR   - __init__             - Error getting new data from relay Script dimmer dimmer named 'LED dimmer script' at address '/home/pi/customScript/LED.py'. Error: name 'subprocess' is not defined

[theyosh]

Ok, I just made another update. So update the code as mentioned in the original post. This will hopefully fix the BH1750 native support. Found a code error.

For the script version, I do not know how your code does look like, but could it be that it needs libraries that are now not installed? Because I changed the installation so that I do not install all the python code system wide. This means that it could be that you need to install some extra os packages. So what happens if you run as normal user the script: /home/pi/customScript/bh1750-smbus.py?

And for your script-relays, the code has to change a bit. Because I now also try to read the state of the dimmer. This was in the TP3 not the case. An working example is here: https://github.com/theyosh/TerrariumPI/blob/4.x.y.z/contrib/external_switch.py
There is now an if statement, which detects an action to switch or to return the state. When you cannot provide a state back, return -1 which tells TP4 to use the existing state.
So, I would make a copy of the LED Dimmer script and try to adjust it a bit based on my example script.
And here is also, I do not know how you made your code, but try it on the console as the pi user. If that does work, we know that the scripts are ok.

[theyosh]

What is also an option, if you are handy enough, is to create a ssh port forwarding on your router to the Pi. So that I can do some remote testing. If you trust me enough, you can send login information to; [email protected]

[wolli1234]

Hi Yosh, I was busy, now I'll continue testing. If there is no progress, remote testing would be okay for me. But I would like to prevent putting my pi to the internet, so let's see how it goes first :).

See my posts below for each issue.

[wolli1234]

BH1750 as sensor:
I updated the code. Now there are no more error messages, but TP4 does not take the value. It's always 0 lux.

BH1750 as script sensor:
I tried running the script, smbus module was missing. After installing, the script is working. It is also working within TP4 now!

Here is the script for reference:

  GNU nano 3.2                                                                  bh1750-smbus.py                                                                            

#!/usr/bin/python3
import smbus
import time

DEVICE     = 0x23
POWER_DOWN = 0x00
POWER_ON   = 0x01
RESET      = 0x07
bus = smbus.SMBus(1)

def convertToNumber(data):
  result=(data[1] + (256 * data[0])) / 1.2
  return (result)

def readLight(addr=DEVICE):
  data = bus.read_i2c_block_data(addr,0x20)
  return convertToNumber(data)

def main():
  lightLevel=readLight()
  print (format(lightLevel,'.2f'))

if __name__=="__main__":
   main()

[theyosh]

Nice. The difference between your script and my code is that I use smbus2 package. That is a replacement package which has couple of nice features I like. And it should be a drop-in replacement for smbus. Apparently it is not.

So if you are a bit handy with coding, you could try to make it work with smbus2 package. But needs some tweaking with the code. And that was the thing I would try on your PI.

Do you think / have time / willing to try to make your script work with smbus2?

[wolli1234]

I will try to google myself to a solution and report back if i succeed or fail ;).

[wolli1234]

okay, that here works in terminal for me with smbus2:

  GNU nano 3.2                             bh1750-smbus2-3.py                                       

#!/usr/bin/python3
from smbus2 import SMBus
import time

DEVICE     = 0x23
POWER_DOWN = 0x00
POWER_ON   = 0x01
RESET      = 0x07
bus = SMBus(1)

def convertToNumber(data):
  result=(data[1] + (256 * data[0])) / 1.2
  return (result)

def readLight(addr=DEVICE):
  data = bus.read_i2c_block_data(addr,0x20,2)
  return convertToNumber(data)

def main():
  lightLevel=readLight()
  print (format(lightLevel,'.2f'))

if __name__=="__main__":
   main()

One question:
data = bus.read_i2c_block_data(addr,0x20,2) here a third argument was necessary compared to old script, number of bytes. But while testing it didn't matter if 2 or 32 bytes were taken as argument. Can you explain me, what this means, or which value makes most sense for you here?

[theyosh]

Hmm, this is the same code that I use... strange that mine does not produce a correct output. If you want to try/play around, the code is here: https://github.com/theyosh/TerrariumPI/blob/4.x.y.z/hardware/sensor/bh1750_sensor.py . I just made one change. So if you are able to do a git pull and restart. Maybe I got it right now.

data = bus.read_i2c_block_data(addr,0x20,2)

My guess is that you specify the max amount of bytes you want to read. And I expected that 2 should be enough, as the data variable has only index 0 and 1 (2 elements). And a higher number does not matter, as you only use the first 2 bytes of the read out of the sensor.

[wolli1234]

Great, did a git pull, removed sensor and added again, now it's working fine!

[wolli1234]

Script Relay / Script Dimmer:

I tried running the script as relay or dimmer. I could not add them in TP4.

WARNING - api - Could not load hardware for relay Script relay relay named 'script relay test' at address '/home/pi/customScript/LED_TP4.py': Script /home/pi/customScript/LED_TP4.py for relay Script relay relay named 'script relay test' at address '/home/pi/customScript/LED_TP4.py' is not executable.

WARNING - api - Could not load hardware for relay Script dimmer dimmer named 'script dimmer test' at address '/home/pi/customScript/LED_TP4.py': Script /home/pi/customScript/LED_TP4.py for relay Script dimmer dimmer named 'script dimmer test' at address '/home/pi/customScript/LED_TP4.py' is not executable.

The script is working in raspberry console and I used your example code, here is the script:

#!/usr/bin/env python

# This is just an example script to test the functionality for TerrariumPI. It is also a reference for implementing your own scripts

import sys
import random
import pigpio

RED_PIN   = 17
GREEN_PIN = 22
BLUE_PIN  = 24

pi =pigpio.pi()

bright = 255

def setLights(pin, brightness):
  realBrightness = int(int(brightness) * (float(bright) / 255.0))
  pi.set_PWM_dutycycle(pin, realBrightness)

# When there is no extra arguments, TerrariumPI expect a float value to return the current state.
# Return -1.0 when not supported.
if len(sys.argv) == 1:
  # Provide a fake dimmer readout...
  #print(random.randint(0,100))

  # Or no readout test
  print('-1.0')

else:

  try:
    value = int(float(sys.argv[1]))
  except Exception as ex:
    raise ValueError('Invalid input value. Should be a number between 0 and 100 including')

  if not (0 <= value <= 100):
    raise ValueError('Invalid input value. Should be a number between 0 and 100 including')

  if value == 0:
    print('Toggle power switch to state OFF')
    # Call your code here....
    setLights(RED_PIN, 0)
    setLights(GREEN_PIN, 0)
    setLights(BLUE_PIN, 0)
  else:
    print('Toggle power switch to state ON or dimming value: {}'.format(value))
    # Call your code here...
    setLights(RED_PIN, 255)
    setLights(GREEN_PIN, 128)
    setLights(BLUE_PIN, 128)

[theyosh]

Not sure how you run the script, but it needs to be executable. So you should do chmod +x /home/pi/customScript/LED_TP4.py

Because then you should be able to run it as: ./home/pi/customScript/LED_TP4.py as normal pi user.

[wolli1234]

chmod did the trick, now I can add it in TP4. I'm testing with a spare PI, and will setup some LEDs on a breadboard. Will report back if the PWM is working wit the percentage.

For script relay, the button is not changing color to green if pushed. I did not test yet if the GPIO is hot after pushing the button, will report back. According to TP4 it is toggling on and off.

Update: Button is changing color to Green, GPIO is hot, working.

[cyber-shifter]

Which dimmer are you using for the LED's? I'm trying to figure out one to get for my LED strips to dim them for sunrise/sunset.

[cyber-shifter]

Had an issue with my test Pi, had to do a new one. You guys seem to have tested all the hardware I have. Is there anything else we want to test operationally?

[cyber-shifter]

No, no, you were clear. I'm just going off what I've seen around all the discussions. Sometimes there is a reinstall involved, sometimes not. I just wanted to make sure I was doing the right thing. Thank you for the specific directions though too! I like having a procedure to follow, because I'm not always the best at remembering. I'll do this and get back to you.

[cyber-shifter]

So I did this, and it fixed it. I took out the part you mentioned (&units=metric). So, my TerrariumPi is set to use Imperial (I know, it's terrible, but familiar) but what is happening is, the numbers on the weather page are the Celsius numbers, but labelled as Fahrenheit.

[theyosh]

YESH!!!! That is it... you can test Fahrenheit values..... As I have not tested that well....

So I suggest to test that in a separate thread. #539

[cyber-shifter]

About dimmers, it is still a bit off guess work. I think I will have to open another issue where I collect all working Dimmer hardware. And add that to the documentation.

Leds dimming is another story. I do have some testing hardware over here, but that does not work well. What I have seen is that somebody made a small python script that accepts values from 0 till 100. And then I made the decision what the to with the leds. But these are those small WS LEDS https://www.amazon.com/ws2811-led/s?k=ws2811+led

A single led bulb, I have not found a working solution for that. As the bulbs work on 220Volt, and have internal power converters for low voltage. So not sure how that works with dimmers...

I'm trying to dim a strip of LED's not a bulb. So I need to dim DC, as opposed to my dimmers that work for my heating panels. Should I just try getting a DC Dimmer? I'm just not sure a good one to go with as "DC Dimmer" is kinda ambiguous.

[cyber-shifter]

There's an aluminum shortage here, so my last heat panel is just being made. I should be getting it in the next couple weeks. Then I will be able to set up a mock setup that mirrors my current ones. I even have the dimmer pack and IR sensor. I'll let you know how it goes once it is set up.

[Specialmias]

Way more stable start and shutdown on the Pi Zero W.
Miflora and Wemo switches were detected and added quickly. RPI_live used to crash the pi zero. Now it just works.. seemlessly.
Although I am aware you are not supporting those officially in the future. With the new venv how would we go about starting as root?
Thank you

[theyosh]

Nice... that it works on Pi Zero W.

In order to change the user for running, you have to edit the file /etc/systemd/system/terrariumpi.service and change the lines with

• User=pi
• Group=pi

To root. And then you need to reload the systemd: systemctl daemon-reload and then if you start it with the service command sudo service terrariumpi start it should start up as root.

Keep in mind, this terrariumpi.service fill will be overwritten every time you run the installer.

[Specialmias]

Hey there!
That did it, I have full access to the GPIO ports now. My door sensor was picked right up and it's been running a day now zero issues on the Pi Zero. The DHT11 sensor I was using is now unhappy with life with the error:

2021-04-23 14:29:36,300 - WARNING - api                  - Unable to load sensor DHT11 sensor humidity named 'test' at address '3': 'NoneType' object has no attribute 'send', retrying in 0.5 seconds...
2021-04-23 14:29:35,716 - WARNING - api                  - Unable to load sensor DHT11 sensor humidity named 'test' at address '3': 'NoneType' object has no attribute 'send', retrying in 0.5 seconds...

but I may just dump the whole wired sensor thing for this package. It's neatly tucked into a tripod.

Thanks as always for your time. Super appreciated.

[theyosh]

Which part does not work well with Fahrenheit values and other values that should be converted based on the settings

[cyber-shifter]

If you're talking to me, That data was in the "Weather" dashboard under "Home"

[cyber-shifter]

I just saw your response

[cyber-shifter]

Did I correctly see that there was planning to allow a reset of the power counter on the front dashboard? I thought I saw mention of that in an issue for the current version, but I wanted to check. To clarify, I'm talking about this one.

[theyosh]

The issue I currently have is that I cannot use the old switch data from TP3. So with TP4, you will start at 0 again for total relay usage. Because I have 3 years of power data, that is not directly converted to TP4 relay data.

So that means that the total power usage info (the screenshot above) will be reset if you upgrade to TP4.

In the mean time I am testing a way of converting this relay data between TP3 and TP4

[cyber-shifter]

I am ok with the reset, I want to be able to reset the counter.

[5point0]

Hi @theyosh,

So I have decided to load version 4 as I started having some issues with an older version.

The install went fine on a fresh SD card and I managed to setup all of my sensors manually. Im not sure if the scan for sensors function works yet but my MI Temperature and Humidity bluetooth sensor had to be added manually too.

I added some areas and they are working as expected(lights, humidity, CO2) but this morning when I checked the webpage wasn't available and this is what I see in the log.

2021-05-05 07:20:49,446 - INFO - terrariumEngine - Starting TerrariumPI 4.0.0 ...
2021-05-05 07:20:49,505 - INFO - terrariumEngine - Loaded 27 settings in 0.06 seconds.
2021-05-05 07:20:50,219 - INFO - terrariumEngine - Loading existing sensors from database.
2021-05-05 07:20:50,271 - INFO - terrariumEngine - Loaded sensor bme280 humidity named 'Hum Light' at address '76' with value 36.55% in 0.05 seconds.
2021-05-05 07:20:50,778 - INFO - terrariumEngine - Loaded sensor k30co2 co2 named 'CO2' at address '/dev/ttyS0' with value 496.00ppm in 0.51 seconds.
2021-05-05 07:20:50,781 - INFO - terrariumEngine - Loaded sensor bme280 temperature named 'temp light' at address '76' with value 26.94C in 0.00 seconds.
2021-05-05 07:20:50,814 - INFO - terrariumEngine - Loaded sensor bme280 humidity named 'Humidity BME' at address '77' with value 38.73% in 0.03 seconds.
2021-05-05 07:20:50,817 - INFO - terrariumEngine - Loaded sensor bme280 temperature named 'Temperature BME' at address '77' with value 25.97C in 0.00 seconds.
2021-05-05 07:20:54,895 - INFO - terrariumEngine - Loaded sensor mitemp temperature named 'Auto Temp' at address '58:2d:34:35:16:da' with value 28.30C in 4.08 seconds.
2021-05-05 07:20:54,898 - INFO - terrariumEngine - Loaded sensor mitemp humidity named 'Auto Hum' at address '58:2d:34:35:16:da' with value 39.30% in 0.00 seconds.
2021-05-05 07:20:54,899 - INFO - terrariumEngine - Scanning for new sensors ...
2021-05-05 07:20:55,008 - INFO - merros_sensor - Meross cloud is not enabled.
2021-05-05 07:21:01,098 - INFO - terrariumEngine - Loaded 7 sensors in 10.88 seconds.
2021-05-05 07:21:01,100 - INFO - terrariumEngine - Loading existing relays from database.
2021-05-05 07:21:01,320 - INFO - terrariumEngine - Loaded relay gpio-inverse relay named 'CO2' at address '35' value 0.00 in 0.21 seconds.
2021-05-05 07:21:01,375 - INFO - terrariumEngine - Loaded relay gpio relay named 'Dehumidifier' at address '22' value 100.00 in 0.05 seconds.
2021-05-05 07:21:01,427 - INFO - terrariumEngine - Loaded relay gpio relay named 'Fan' at address '11' value 100.00 in 0.05 seconds.
2021-05-05 07:21:01,434 - INFO - terrariumEngine - Loaded relay gpio-inverse relay named 'FanOUT' at address '36' value 0.00 in 0.01 seconds.
2021-05-05 07:21:01,440 - INFO - terrariumEngine - Loaded relay gpio-inverse relay named 'FanSCR' at address '37' value 0.00 in 0.01 seconds.
2021-05-05 07:21:01,446 - INFO - terrariumEngine - Loaded relay gpio-inverse relay named 'Heater' at address '33' value 0.00 in 0.01 seconds.
2021-05-05 07:21:01,452 - INFO - terrariumEngine - Loaded relay gpio-inverse relay named 'Humidifier' at address '38' value 0.00 in 0.01 seconds.
2021-05-05 07:21:01,525 - INFO - terrariumEngine - Loaded relay gpio relay named 'Light' at address '40' value 100.00 in 0.07 seconds.
2021-05-05 07:21:01,534 - INFO - terrariumEngine - Loaded relay gpio-inverse relay named 'Pump 1' at address '31' value 0.00 in 0.01 seconds.
2021-05-05 07:21:01,541 - INFO - terrariumEngine - Loaded relay gpio-inverse relay named 'Pump 2' at address '29' value 0.00 in 0.01 seconds.
2021-05-05 07:21:01,549 - INFO - terrariumEngine - Loaded relay gpio-inverse relay named 'Spare' at address '32' value 0.00 in 0.01 seconds.
2021-05-05 07:21:01,552 - INFO - terrariumEngine - Scanning for new relays ...
2021-05-05 07:21:07,177 - INFO - meross_relay - Meross cloud is not enabled.
2021-05-05 07:21:07,185 - WARNING - init - Error sending through socket 19
Traceback (most recent call last):
File "/home/pi/TerrariumPI/venv/lib/python3.7/site-packages/zeroconf/init.py", line 2969, in send
bytes_sent = s.sendto(packet, 0, (real_addr, port))
File "/home/pi/TerrariumPI/venv/lib/python3.7/site-packages/gevent/_socketcommon.py", line 703, in sendto
return self._sock.sendto(*args)
OSError: [Errno 126] Required key not available

This is similar to the issue I was having with 3.x.x so its probably something on my side, hopefully you could point me in the right direction. After a reboot I can access the webpage as usual.

Something else I noticed after the reboot the main light area is off even though it should still be on. Heres a screen shot.

[theyosh]

Hi,

thanks for testing... And you did found some new issues, which I hope to have fixed now except 1. Make sure you have up to date code: git pull

1. Scanning for MiTemp should work again. I made a small typo in the code. So, you could delete a MiTemp sensor, and then do a rescan from the web interface. That should than return the delete sensor back as a newly found sensor. Or just delete the database terrariumpi.db and restart. Then they should be found during startup.
   But you could add them manually, and they do work... so we can confirm for 90% that they are working.
2. The ZeroConf error during relay scanning. I had not seen this issue, and it will be hard to debug. So I just added some extra code to try to catch this error and just continue. Not sure how to test... but if you do not see this message anymore, we could say it is fixed.
3. Terrariumpi does auto restart if the engine could not update withing 120 seconds. I have seen some bluetooth hanging and that stops the software. And I have even a Pi restart when the my software restarts in 10 minutes. Mostly that is caused by bluetooth problems or camera. But these errors are hard to debug with not the surrounding logging. Because I cannot see what the restart caused. Only that it restarted... Also in /var/log/syslog should also contain some logging.
4. Light timmer is strange. I need to test that as I have not tested that scenario.

I hope this explains it a bit... and if you can do an update an try to see if the issues are gone.

[5point0]

Hi @theyosh

Thanks for helping out with this.

I have deleted the MiTemp sensor, updated the code and it now automatically adds the sensor as expected.

2021-05-05 23:07:13,949 - INFO    - terrariumEngine      - Starting TerrariumPI 4.0.0 ...
2021-05-05 23:07:14,007 - INFO    - terrariumEngine      - Loaded 27 settings in 0.06 seconds.
2021-05-05 23:07:14,730 - INFO    - terrariumEngine      - Loading existing sensors from database.
2021-05-05 23:07:14,777 - INFO    - terrariumEngine      - Loaded sensor bme280 humidity named 'Hum Light' at address '76' with value 66.72% in 0.04 seconds.
2021-05-05 23:07:15,284 - INFO    - terrariumEngine      - Loaded sensor k30co2 co2 named 'CO2' at address '/dev/ttyS0' with value 1170.00ppm in 0.51 seconds.
2021-05-05 23:07:15,286 - INFO    - terrariumEngine      - Loaded sensor bme280 temperature named 'temp light' at address '76' with value 24.17C in 0.00 seconds.
2021-05-05 23:07:15,319 - INFO    - terrariumEngine      - Loaded sensor bme280 humidity named 'Humidity BME' at address '77' with value 71.05% in 0.03 seconds.
2021-05-05 23:07:15,321 - INFO    - terrariumEngine      - Loaded sensor bme280 temperature named 'Temperature BME' at address '77' with value 23.40C in 0.00 seconds.
2021-05-05 23:07:15,322 - INFO    - terrariumEngine      - Scanning for new sensors ...
2021-05-05 23:07:15,426 - INFO    - merros_sensor        - Meross cloud is not enabled.
2021-05-05 23:07:24,940 - INFO    - terrariumEngine      - Added new sensor mitemp temperature named 'MiTemperature bluetooth sensor measuring temperature' at address '58:2d:34:35:16:da' to database with value 25.80C in 3.44 seconds.
2021-05-05 23:07:24,945 - INFO    - terrariumEngine      - Added new sensor mitemp humidity named 'MiTemperature bluetooth sensor measuring humidity' at address '58:2d:34:35:16:da' to database with value 66.50% in 0.00 seconds.
2021-05-05 23:07:24,962 - INFO    - terrariumEngine      - Loaded 7 sensors in 10.23 seconds.

I will keep an eye to see if the rest runs smoothly now.

[5point0]

Hi @theyosh

So the error has returned but this time there is some info about the camera.

2021-05-06 18:44:16,201 - INFO    - terrariumEngine      - Starting TerrariumPI 4.0.0 ...
2021-05-06 18:44:16,282 - INFO    - terrariumEngine      - Loaded 27 settings in 0.08 seconds.
2021-05-06 18:44:17,305 - INFO    - terrariumEngine      - Loading existing sensors from database.
2021-05-06 18:44:17,359 - INFO    - terrariumEngine      - Loaded sensor bme280 humidity named 'Hum Light' at address '76' with value 70.16% in 0.05 seconds.
2021-05-06 18:44:17,868 - INFO    - terrariumEngine      - Loaded sensor k30co2 co2 named 'CO2' at address '/dev/ttyS0' with value 449.00ppm in 0.51 seconds.
2021-05-06 18:44:17,871 - INFO    - terrariumEngine      - Loaded sensor bme280 temperature named 'temp light' at address '76' with value 24.52C in 0.00 seconds.
2021-05-06 18:44:17,905 - INFO    - terrariumEngine      - Loaded sensor bme280 humidity named 'Humidity BME' at address '77' with value 74.74% in 0.03 seconds.
2021-05-06 18:44:17,908 - INFO    - terrariumEngine      - Loaded sensor bme280 temperature named 'Temperature BME' at address '77' with value 23.70C in 0.00 seconds.
2021-05-06 18:44:21,862 - INFO    - terrariumEngine      - Loaded sensor mitemp temperature named 'MiTemperature bluetooth sensor measuring temperature' at address '58:2d:34:35:16:da' with value 26.20C in 3.95 seconds.
2021-05-06 18:44:21,866 - INFO    - terrariumEngine      - Loaded sensor mitemp humidity named 'MiTemperature bluetooth sensor measuring humidity' at address '58:2d:34:35:16:da' with value 69.60% in 0.00 seconds.
2021-05-06 18:44:21,868 - INFO    - terrariumEngine      - Scanning for new sensors ...
2021-05-06 18:44:22,020 - INFO    - merros_sensor        - Meross cloud is not enabled.
2021-05-06 18:44:28,144 - INFO    - terrariumEngine      - Loaded 7 sensors in 10.84 seconds.
2021-05-06 18:44:28,145 - INFO    - terrariumEngine      - Loading existing relays from database.
2021-05-06 18:44:28,458 - INFO    - terrariumEngine      - Loaded relay gpio-inverse relay named 'CO2' at address '35' value 0.00 in 0.29 seconds.
2021-05-06 18:44:28,468 - INFO    - terrariumEngine      - Loaded relay gpio relay named 'Dehumidifier' at address '22' value 0.00 in 0.01 seconds.
2021-05-06 18:44:28,565 - INFO    - terrariumEngine      - Loaded relay gpio relay named 'Fan' at address '11' value 100.00 in 0.10 seconds.
2021-05-06 18:44:28,574 - INFO    - terrariumEngine      - Loaded relay gpio-inverse relay named 'FanOUT' at address '36' value 0.00 in 0.01 seconds.
2021-05-06 18:44:28,583 - INFO    - terrariumEngine      - Loaded relay gpio-inverse relay named 'FanSCR' at address '37' value 0.00 in 0.01 seconds.
2021-05-06 18:44:28,591 - INFO    - terrariumEngine      - Loaded relay gpio-inverse relay named 'Heater' at address '33' value 0.00 in 0.01 seconds.
2021-05-06 18:44:28,600 - INFO    - terrariumEngine      - Loaded relay gpio-inverse relay named 'Humidifier' at address '38' value 0.00 in 0.01 seconds.
2021-05-06 18:44:28,716 - INFO    - terrariumEngine      - Loaded relay gpio relay named 'Light' at address '40' value 100.00 in 0.12 seconds.
2021-05-06 18:44:28,724 - INFO    - terrariumEngine      - Loaded relay gpio-inverse relay named 'Pump 1' at address '31' value 0.00 in 0.01 seconds.
2021-05-06 18:44:28,733 - INFO    - terrariumEngine      - Loaded relay gpio-inverse relay named 'Pump 2' at address '29' value 0.00 in 0.01 seconds.
2021-05-06 18:44:28,741 - INFO    - terrariumEngine      - Loaded relay gpio-inverse relay named 'Spare' at address '32' value 0.00 in 0.01 seconds.
2021-05-06 18:44:28,743 - INFO    - terrariumEngine      - Scanning for new relays ...
2021-05-06 18:44:34,403 - INFO    - meross_relay         - Meross cloud is not enabled.
2021-05-06 18:44:34,413 - WARNING - __init__             - Error sending through socket 18
Traceback (most recent call last):
 File "/home/pi/TerrariumPI/venv/lib/python3.7/site-packages/zeroconf/__init__.py", line 2969, in send
bytes_sent = s.sendto(packet, 0, (real_addr, port))
 File "/home/pi/TerrariumPI/venv/lib/python3.7/site-packages/gevent/_socketcommon.py", line 703, in sendto
return self._sock.sendto(*args)
OSError: [Errno 126] Required key not available
2021-05-06 18:44:44,441 - INFO    - terrariumEngine      - Loaded 11 relays in 16.30 seconds.
2021-05-06 18:44:44,442 - INFO    - terrariumEngine      - Loading existing buttons from database.
2021-05-06 18:44:44,448 - INFO    - terrariumEngine      - Loaded 0 buttons in 0.01 seconds.
2021-05-06 18:44:44,449 - INFO    - terrariumEngine      - Loading existing webcams from database.
2021-05-06 18:44:44,533 - WARNING - api                  - Unable to load webcam Raspberry PI camera named 'Main View' at address 'rpicam': Failed to create MMAL component b'vc.camera_info': I/O error., retrying in 0.5 seconds...
2021-05-06 18:44:45,035 - WARNING - api                  - Unable to load webcam Raspberry PI camera named 'Main View' at address 'rpicam': Failed to create MMAL component b'vc.camera_info': I/O error., retrying in 0.5 seconds...

You mentioned previously that it could be the bluetooth or camera. Should I try deleting the camera to see if it solves it?

[5point0]

Hi @theyosh

So I deleted the camera 3 days ago and I haven't seen the issue since.
Do you think the camera could be faulty?

[theyosh]

I am not sure... I also get the feeling that this is related: gevent/gevent#1735 (comment) which is hard to fix. Because it could be that the code for the camera itself is not 100%. Not sure.

I have at home 2 setups with different camera's. And I have no error messages, but just hanging and causing timeouts. So, I am not sure what this is....

But then I wonder.... the error with the zeroconf package and the webcam error happens on the same time??? That is a bit strange... Maybe the Pi is then busy with something?

[V687862]

Hi @theyosh
First time posting here
I've managed to install 4.0.0 alpha with no issues
When it comes to setting the sensors up I get this:

ERROR - init - Error updating sensor Sensirion SHT3X sensor humidity named '31DRH' at address '44'. Check your hardware! Invalid reading from sensor Sensirion SHT3X sensor humidity named '31D at address '44'

I'm using the SHT31D sensor, and I know the sensor always runs at 0x44. For the sensor address, I've tried, 44 and 0x44. And I also noticed that in the code it was setup to only be setup on temperature and not humidity, I believe all that missing was to add 'humidity' in the class type. But as of now I can't setup the sensor to continue. TIA

[theyosh]

Hi,

sorry for the late reply. But this is something hard to debug without the actual hardware. And I see that I have merged two sensors in one. So the SHT3X and SHT3xD are now combined. But apparently it does not work.

I made a fix for adding humidity, but at this point in time, you need to remove the terrariumpi.db after a git pull As I have changed the database structure and added a migration path to the software. So it is only this time.

But how to fix this.... Do you have some programming experience in Python? Or are you able and willing to make a port forward to your pi for SSH. Then I can login into your PI, and do some testing. That is the fastest way to fix this sensor. If you can and will make a port forward, then you can send the login details to [email protected]

[killwater]

Hello,
I noticed two issues with 4.0.0:

1. After adding a second DHT11 sensor tagged as Exclude Average the average graph alarm max and min value have been adjusted even though they shouldn't. The current vaule seems to be fine:
   
2. All sensor tab does not show all sensors, only the first one. And it does not show the value:
   
3. In temperature and humidity sensor tab it is the same as point 2.

Seems to look fine when I open TheYosh's terrariumPI website so I do not think the issue is with browser settings.

Also there seem to be spikes in averages over long term:

[theyosh]

Hi,

sorry for the late reply. You are right that the exclude average is not working correctly. That has been fixed in code. But that also involves a database reset. This is a one time reset, as it will also add a migration path for future updates.
So after a git pull remove the terrariumpi.db file and restart. That should fix the exclude average bug.

All sensors will not show up all sensors in the beginning. This is a HTTP caching issue. So it could take at max 1 minute to show all the sensors on that page. The same is when you just views your temperature sensors, and add a new one. This is due to caching in the browser. That needs some more fine tuning in the code.

And the spikes in the graphs are the result of a slow or faulty sensor. My software tries to make 2 measurements per minute. And if there are errors, it attempts 3 times to read. And that could result in that a measurement will take up more then 30 seconds. And probably even more then 60 seconds. And then you will miss data points. As you will not get enough data. As you mentioned you are using a DHT sensor. And I guess that is the problem. DHT sensors are not that stable.

[killwater]

Thank you very much. The gauges and charts seem to work fine right now thank you. I am not sure about the average though as right now for example the average is 34.4 and my DHT22 sensor is 33,7 but DHT11 is 35.

[binksinjapan]

Hi,

First want to say this is a great setup and you have done well with this project. Have been using this for my boy's Bearded Dragon Terrarium. One of the issues I have is having to wire sensors into the tank. It is hard to position the sensor to get the best reading due to the cabling restraints.

Just wanted to make a suggestion of a possible feature for remote sensors. If a REST server could be implemented to accept a put/post method with sensor data (payload in JSON format), it would allow more custom remote sensors to send data instead of being polled. This would also allow the sensor to be put into low power mode to save battery life instead of having to be online to receive the poll from the TerrariumPI. Being wireless, this would also allow you to position the sensor in the optimum location and wont have the wiring constraints.

My idea is to have an ESP32 connected to some sensors which can take reading, send the data back to the TerrariumPi via REST put/post commands, then go into sleep mode to conserve power.

Regards.

[theyosh]

Hi,

I see you wish, but I am afraid it is not that easy. In order to support push data, I have to create a system with:

• Authentication
• Rate limiting
• Different fields in post data
• And maybe more...

So I think it is better to make your own REST server that accepts the push data from your sensors. And then, your REST API can serve a JSON file where the sensor data is stored. And then use: https://github.com/theyosh/TerrariumPI/wiki/Remote-data

That way, you control your sensor network, and my software will poll your own REST API server.

[killwater]

Hello,
I am trying to use a DC dimmer option in relays to drive an AC dimmer. How it works is I have white LED connected through 5 Ohm resistor to pin 32. It iluminates a photoresistor controlling a simple desk lamp AC dimmer. The only behaviour I get is full power but once I go under 2% it turns off completely. Any help would be appreciated.

[AndrejWeber]

It seems, it works good!
To stay off is normal, because not all dimmer can work with that nearly zero light.
I do not use the new version right now, so I cannot tell you, if there is a "zero-correction" in code, you can edit. For real "off" you always should use a Relais, to cut off the current.

[killwater]

The problem is there is no light between 0-2% setting but when I get over 2% it goes full power straight away up to 100%.
0-2% No power at all
2%-100% Full power
What I expected was:
0-90% No power (as the LED would not be iluminated at such low voltage)
90-100% Variable power from 0-100%

Is there any reason why we there is a limit of frequency between 100-10000Hz?

[morrell7]

Running solid for almost 10 days now. Upgraded to the BME280 sensor as you suggested and it's working great.

Thanks again for all you hard work sir. I hope one day I could contribute something so awesome.

I will post some pictures soon, my monitor is loving it. And I do have a live stream from time to time.

Some recordings on my channel. - Species Varanus niloticus

https://www.youtube.com/watch?v=p6T9IKzuXYM

Around one hour in he grabs the eggs :)

Best regards

[morrell7]

Where do you want us posting photos? Got some pics of the enclosure I built as well.

[theyosh]

Nice!. You can post pictures at: #210

[chrRtg]

Today I tried to set up OpenWeatherMap but my URL is not accepted.
I had a look into the .py files in weather/ .
How does look like a working SourceURL?

[theyosh]

Sorry for the late reply. The url should look like: https://api.openweathermap.org/data/2.5/weather?q=[CITY],[CountryCode]&appid=[YOUR_API_KEY]

That is all. Remove other url parameters from the url if the Openweather api give them

[chrRtg]

I wonder about possible configurability of the views, in particular the Dashboard. Is it possible to set the sort order of the elements, to have e.g. two measures in a row or to group them. I also wonder how to hide unused elements from the main menu.

[theyosh]

at the moment this is not possible. UX is not my best part. And is at low priority.

[Dave0408]

Hello @theyosh ,
in TP4 there is still a TerrariumPI/contrib/toggle_switch.py file.
But i couldn'f find the settings.cfg to determine the switch id's.

I have some external scripts for my misting system and fans and i would like to use them in TP4 as well.
Misting system should only run 15 or 20 seconds multiple times a day. I couldn't manage to configure a second intervall thorugh the website. For my fans we had an other disuccion here.

So far I was fine using my scripts and managed them with crontab.

Is it still possible to get the ids?

Thanks.

[theyosh]

Hi,

yes, this is still possible. Just update the code git pull and there should be an updated version contrib/toggle_switch.py. There is also the info to find your new IDs.