Hack a "normal" thermostatic valve and make it WiFi, or RF or similar

Third party integrations
23

yes yes. I mean makes no sense to buy ONE thermostatic valce and put in the cold room … (grandma’s room, and she is always home)

24

you use the bluetooth model also with homegear?

25

No, I think the bluettoth model is something else. Won’t be compatible with homegear but can be use directly with home-assistant.

26

Ok clear.

And you can use automations in HA with data from homegear?

27

Yes you can control homegear from home-assistant

29

also this GGRRRR

pi@raspberrypi:~ $ echo 'deb https://homegear.eu/packages/Raspbian/ jessie/' >> /etc/apt/sources.list.d/homegear.list
-bash: /etc/apt/sources.list.d/homegear.list: Permission denied
pi@raspberrypi:~ $ sudo echo 'deb https://homegear.eu/packages/Raspbian/ jessie/' >> /etc/apt/sources.list.d/homegear.list
-bash: /etc/apt/sources.list.d/homegear.list: Permission denied
pi@raspberrypi:~ $
30

do a sudo su before

if you do: wget https://homegear.eu/packages/Release.key && apt-key add Release.key && rm Release.key
only the first wget is executed as root!

If you want, you can also do:

sudo wget https://homegear.eu/packages/Release.key && sudo apt-key add Release.key && sudo rm Release.key
31

pi@raspberrypi:~ $ sudo su apt install apt-transport-https
No passwd entry for user ‘apt’
pi@raspberrypi:~ $

32

also this, first is ok, second no

pi@raspberrypi:~ $ sudo wget https://homegear.eu/packages/Release.key && sudo apt-key add Release.key && sudo rm Release.key
–2017-01-18 15:30:37-- https://homegear.eu/packages/Release.key
Resolving homegear.eu (homegear.eu)… 138.201.146.201, 2a01:4f8:172:19a5::3
Connecting to homegear.eu (homegear.eu)|138.201.146.201|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 3125 (3.1K) [application/pgp-keys]
Saving to: ‘Release.key.7’

Release.key.7 100%[=====================>] 3.05K --.-KB/s in 0s

2017-01-18 15:30:37 (8.00 MB/s) - ‘Release.key.7’ saved [3125/3125]

OK
pi@raspberrypi:~ $ sudo su echo ‘deb https://homegear.eu/packages/Raspbian/ wheezy/’ >> /etc/apt/sources.list.d/homegear.list
-bash: /etc/apt/sources.list.d/homegear.list: Permission denied
pi@raspberrypi:~ $

33

Why not just do “sudo su” then press enter? That will put you into root directly

34

Because I am newb :smiley:

35

Yes, either you do sudo su -> enter and then the command.
Or you add sudo in front of each command.

36

Got it.

Installing now.

Then I add this in configuration

homematic:
  hosts:
    wireless:
      ip: 192.168.1.239

Can I check how it works withoiut having devices?

37

Hello gentleman
Interesting topic I see, I was solving the same problem. There are few really nice projects like tado, with open api, but they are a bit pricey for me now. So I was thinking of making dumb thermo valve smart by adding RF to it, there are some German project with quite poor documentation so I chosen another way of accomplishing our goal.
I bought thermo electric actuator for floor heating system, one like this
http://s.aliexpress.com/JZjya6JJ
And I am simply switching it on and off with relay board attached to gpio pin on Raspberry where Hass is running. There are few downsides with this solution there are no chance to do analog setting of valve, it is either on or off, on the other hand, it takes about 3 minutes to go from on to off so it would be possible to switch it in intervals for keeping it desired state as actuator is pushing the radiator.
If you will find something smart to use with Hass with good price tag I would be interested :slight_smile:

38

my dumb valve arrived.
It shows the sign INS (not sure what that means, in the manual no good instructions, no sign of INS).

WHat to do next, how to integrate in homegear (I installed it) …

39

no idea what to do now

root@raspberrypi:/lib# cd /var/lib
root@raspberrypi:/var/lib# cd homegear
root@raspberrypi:/var/lib/homegear# homegear -r
02/02/17 14:30:02.855 Could not connect to socket. Error: No such file or directory
02/02/17 14:30:02.856 Could not connect to socket. Error: No such file or directory
root@raspberrypi:/var/lib/homegear#
40

I did this, not sure what I am doing

pi@raspberrypi:~ $ sudo homegear
02/02/17 14:37:36.146 Loading RPC server settings from /etc/homegear/rpcservers.conf
02/02/17 14:37:36.147 Loading RPC client settings from /etc/homegear/rpcclients.conf
02/02/17 14:37:36.149 Starting Homegear...
02/02/17 14:37:36.149 Homegear version 0.6.14-874
02/02/17 14:37:36.149 Git commit SHA of libhomegear-base: -
02/02/17 14:37:36.149 Git branch of libhomegear-base:     -
02/02/17 14:37:36.149 Git commit SHA of Homegear:         -
02/02/17 14:37:36.149 Git branch of Homegear:             -
02/02/17 14:37:36.150 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
02/02/17 14:37:36.150 Info: Core file size now is "4294967295".
02/02/17 14:37:36.150 Info: Setting maximum thread priority to "95" for user with id 0 and group with id 0.
02/02/17 14:37:36.150 Info: Maximum thread priority now is "95".
02/02/17 14:37:36.181 Info: Backing up database...
02/02/17 14:37:36.307 Initializing database...
02/02/17 14:37:36.310 Info: Loading family module mod_kodi.so
02/02/17 14:37:36.314 /etc/homegear/families/kodi.conf
02/02/17 14:37:36.314 Info: Loading family module mod_enocean.so
02/02/17 14:37:36.319 /etc/homegear/families/enocean.conf
02/02/17 14:37:36.319 Info: Loading family module mod_intertechno.so
02/02/17 14:37:36.323 /etc/homegear/families/intertechno.conf
02/02/17 14:37:36.324 Info: Loading family module mod_homematicwired.so
02/02/17 14:37:36.330 /etc/homegear/families/homematicwired.conf
02/02/17 14:37:36.330 Info: Loading family module mod_max.so
02/02/17 14:37:36.337 /etc/homegear/families/max.conf
02/02/17 14:37:36.338 Info: Loading family module mod_homematicbidcos.so
02/02/17 14:37:36.349 /etc/homegear/families/homematicbidcos.conf
02/02/17 14:37:36.350 Info: Loading family module mod_philipshue.so
02/02/17 14:37:36.355 /etc/homegear/families/philipshue.conf
02/02/17 14:37:36.356 Info: Loading family module mod_knx.so
02/02/17 14:37:36.361 /etc/homegear/families/knx.conf
02/02/17 14:37:36.362 Info: Loading family module mod_insteon.so
02/02/17 14:37:36.368 /etc/homegear/families/insteon.conf
02/02/17 14:37:36.369 Info: Loading family module mod_sonos.so
02/02/17 14:37:36.374 /etc/homegear/families/sonos.conf
02/02/17 14:37:36.375 Info: Loading family module mod_miscellaneous.so
02/02/17 14:37:36.378 /etc/homegear/families/miscellaneous.conf
02/02/17 14:37:36.378 Info: Loading family module mod_ipcam.so
02/02/17 14:37:36.382 /etc/homegear/families/ipcam.conf
02/02/17 14:37:36.383 Info: Loading family module mod_beckhoff.so
02/02/17 14:37:36.388 /etc/homegear/families/beckhoff.conf
02/02/17 14:37:36.388 Warning: Running as root. The authors of Homegear recommend running Homegear as user.
02/02/17 14:37:36.388 Warning: Running as root. The authors of Homegear recommend running Homegear as user.
02/02/17 14:37:36.389 Starting script engine server...
02/02/17 14:37:36.419 Initializing licensing controller...
02/02/17 14:37:36.419 Loading licensing controller data...
02/02/17 14:37:36.419 Loading devices...
02/02/17 14:37:36.419 Info: Not initializing device family HomeMatic BidCoS, because no physical interface was found.
02/02/17 14:37:36.419 Info: Disposing family module mod_homematicbidcos.so
02/02/17 14:37:36.420 Info: Not initializing device family HomeMatic Wired, because no physical interface was found.
02/02/17 14:37:36.420 Info: Disposing family module mod_homematicwired.so
02/02/17 14:37:36.420 Info: Not initializing device family Insteon, because no physical interface was found.
02/02/17 14:37:36.420 Info: Disposing family module mod_insteon.so
02/02/17 14:37:36.420 Info: Not initializing device family MAX!, because no physical interface was found.
02/02/17 14:37:36.420 Info: Disposing family module mod_max.so
02/02/17 14:37:36.420 Loading XML RPC devices...
02/02/17 14:37:36.427 Loading device 1
02/02/17 14:37:36.427 Loading XML RPC devices...
02/02/17 14:37:36.440 Loading device 2
02/02/17 14:37:36.441 Loading XML RPC devices...
02/02/17 14:37:36.442 Loading device 3
02/02/17 14:37:36.443 Loading XML RPC devices...
02/02/17 14:37:36.444 Loading device 4
02/02/17 14:37:36.445 Info: Not initializing device family Beckhoff, because no physical interface was found.
02/02/17 14:37:36.445 Info: Disposing family module mod_beckhoff.so
02/02/17 14:37:36.445 Info: Not initializing device family KNX, because no physical interface was found.
02/02/17 14:37:36.445 Info: Disposing family module mod_knx.so
02/02/17 14:37:36.445 Info: Not initializing device family EnOcean, because no physical interface was found.
02/02/17 14:37:36.445 Info: Disposing family module mod_enocean.so
02/02/17 14:37:36.446 Info: Not initializing device family Intertechno, because no physical interface was found.
02/02/17 14:37:36.446 Info: Disposing family module mod_intertechno.so
02/02/17 14:37:36.446 Loading XML RPC devices...
02/02/17 14:37:36.448 Loading device 5
02/02/17 14:37:36.448 Start listening for packets...
02/02/17 14:37:36.449 Module Sonos: Event server "My-Sonos-1234": Info: Started listening on address 192.168.1.239 an                                     d port 7373
02/02/17 14:37:36.449 Initializing RPC client...
02/02/17 14:37:36.449 Starting XML RPC server RPCServer1 listening on 0.0.0.0:2001...
02/02/17 14:37:36.452 Starting XML RPC server RPCServer2 listening on 0.0.0.0:2002, SSL enabled...
02/02/17 14:37:36.452 RPC Server (Port 2001): Info: RPC Server started listening on address 0.0.0.0 and port 2001
02/02/17 14:37:36.481 Starting XML RPC server RPCServer3 listening on 0.0.0.0:2003, SSL enabled, authentication enabl                                     ed...
02/02/17 14:37:36.481 RPC Server (Port 2002): Info: RPC Server started listening on address 0.0.0.0 and port 2002
02/02/17 14:37:36.509 Starting CLI server...
02/02/17 14:37:36.509 RPC Server (Port 2003): Info: RPC Server started listening on address 0.0.0.0 and port 2003
02/02/17 14:37:36.509 Initializing event handler...
02/02/17 14:37:36.510 Loading events...
02/02/17 14:37:36.510 Starting flows server...
02/02/17 14:37:36.513 Startup complete. Waiting for physical interfaces to connect.
02/02/17 14:37:36.513 All physical interfaces are connected now.
02/02/17 14:37:36.513 Starting UPnP server...
02/02/17 14:37:36.514 Info: UPnP server: Binding to address: 192.168.1.239
02/02/17 14:37:36.514 Error: A core file exists in Homegear's working directory ("/var/lib/homegear/core"). Please se                                     nd this file to the Homegear team including information about your system (Linux distribution, CPU architecture), the                                      Homegear version, the current log files and information what might've caused the error.
02/02/17 14:37:36.514 Error: A core file exists in Homegear's working directory ("/var/lib/homegear/core"). Please se                                     nd this file to the Homegear team including information about your system (Linux distribution, CPU architecture), the                                      Homegear version, the current log files and information what might've caused the error.02/02/17 14:37:36.514 UPnP Se                                     rver: Info: Started listening.

02/02/17 14:37:37.512 RPC Server (Port 2001): Info: Connection from 192.168.1.239:47028 accepted. Client number: 7
02/02/17 14:37:37.513 RPC Server (Port 2001): Info: RPC server client id for client number 7 is: 0
02/02/17 14:37:37.514 RPC Server (Port 2001): Info: Client number 7 is calling RPC method: getServiceMessages (1) Par                                     ameters:
02/02/17 14:37:37.553 RPC Server (Port 2001): Info: Connection to client number 7 closed.
41

how to connect the dumb one to homegear/HA/pi3 … ???

42

hi! Did you manage?

43

I understood tha (some) options are

  • use the Max! Cube component (but is not working well now)
  • flash a new firmware on the Max!Cube and then use homegear, and then use homematic on HASS

is it not possible to use homegear/homematic, without flashing a new firmware on the Max!Cube?