JTK – Notes and Ramblings Things we have found …

After getting the Python sorted out to read the Seneye Home it was time resolve a few outstanding issues with the unit. Seneye has only released the partial API discussed previously. This API lacks the ability to 1) register a slide 2) clear the “offline” readings stored in the unit.

Following ideas found online I setup VirtualHere. There is a Raspberry Pi server and a Windows 10 client. The free version will allow for a for sharing a single device. The free version also doesn’t support running the client as a service on Windows 10. Neither of these limitation was a problem for our setup.

I setup a cron job to run every 30 minutes. It calls a shell script which stops the VirtualHere server, runs the Seneye Python code to send reading to Openhab via MQTT and restarts the VirtualHere server.

crontab -e
*/30 * * * * ~/fish.sh

fish.sh
date >>~/Seneye-MQTT/suddriver.log
sudo killall vhusbdarm
sleep 10
python ~/Seneye-MQTT/suddriver.py >>~/Seneye-MQTT/suddriver.log
sleep 10
sudo ~/VirtualHere/vhusbdarm -b

It would be nice not to need sudo in this script but at the moment I haven’t noodled out the permissions required to get the VitrualHere server to run without sudo.

The Seneye Home normally wants to be connected to a Windows PC to log its reading to the cloud. Naturally, I see no reason for the cloud to be involved. {Insert rant about unnecessary cloud connections for home devices here} Fortunately, Seneye has released at least a partial API for reading on a Raspberry Pi.

https://github.com/seneye/SUDDriver

There is a handy page describing compiling and testing the samples from the above: https://raspberrypidiyblog.wordpress.com/2018/01/17/seneye-suddriver-raspberrypi/

Compiling the code required I change line 464 of linux/hid.c from:

tmp = (hid_device_info*)malloc(sizeof(struct hid_device_info));

to

tmp = (struct hid_device_info *)malloc(sizeof(struct hid_device_info));

Over at https://doughall.me/2017/06/30/seneyemqttpt1/ is a discussion on using Python on the Pi to get the device readings. His code can be found at https://github.com/dhallgb/Seneye-MQTT.

Following these instructions I installed python modules pprint, pyusb, paho-mqtt and bitstring(not mentioned but required) using pip install. It was necessary to update the 10-local.rules file to indicate the correct idVendor and idProduct: idVendor=24f7 and idProduct=2204. These need to be in hex in the udev files. They are in decimal in the python source.

I have also updated the python script to not use bitstring and to use struct instead.

def mungReadings(p):
   s = {}
   scrap, scrap, TS, flag1, flag2, scrap, pH, NH3, thermo, scrap  = unpack('<BBLBBHHHL46s', p)
   s['InWater']=bool(flag1 & 0b00000100)
   s['SlideNotFitted']=bool(flag1 & 0b00001000)
   s['SlideExpired']=bool(flag1 & 0b00010000)
   s['pH']=float(pH)/100   # divided by 100
   s['NH3']=float(NH3)/1000  # divided by 1000
   s['Temp']=float(thermo)/1000 # divided by 1000
   j = json.dumps(s, ensure_ascii=False)
   return(j)

Still working on how to register a Seneye slide without the Windows PC. From the Seneye SUDDriver wiki:

Slide codes are retrieved from an API hosted on the seneye cloud. In order to use it, your account will need activating to allow permission. You can request access to this by E-mail by asking for “SUD Developer Access” and we will send you the terms and conditions to be sent to you for agreement.

https://github.com/seneye/SUDDriver/wiki/Activating-a-seneye-slide-for-your-SUD#retrieving-a-slide-code

I added the zwave binding:
sudo apt-get install openhab-addon-binding-zwave

For the Aeon Labs Z-Stick Series 2 which appears as /dev/ttyUSB0 I had to add the openhab user to the dialout group:
sudo adduser openhab dialout

To bind devices I used Habmin – https://github.com/cdjackson/HABmin. I chose the complied release version – https://github.com/cdjackson/HABmin/releases. The alternative is to install source from the git and compile.

So far I have linked a RadioThermostat CT-80 with Z-wave interface and a Aoetec Home Energy Meter(2nd edition).

For the HEM it was necessary to set the mode properly for periodic updates.

The RadioThermostat only sends changes and only works in “dumb” mode when using zwave. I have not yet been able to read the humidity from the thermostat. The definition in the openhab zwave binding is imcomplete.

Radio Thermostat WiFi Module : http://ndgeek.com/ct-50/RTCOAWiFIAPIV1_3.pdf. The radio module I had was very unreliable and disconnected frequently. I did find some interesting discussions on using the WiFi module with Openhab – https://community.openhab.org/t/binding-radio-thermostat/5480 & https://community.openhab.org/t/how-to-return-current-temp-from-my-thermostat/3141

Radio Thermostat zwave Module: http://products.z-wavealliance.org/MarketCertification/File?folder=&filename=MarketCertificationFiles/1046/RTZW-02_module_IB_9jun14.pdf. The Openhab wiki does have some good examples for the zwave interface – https://community.openhab.org/t/collection-of-working-z-wave-configs/1407

Aoetec Home Energy Meter(2nd edition): https://docs.google.com/viewer?a=v&pid=forums&srcid=MDM3NTIwMDUwMTA4OTkyOTEwNDQBMTc2Mjg0MjUxOTM5MzgwNTU2ODABYXZNMEo0RUZVcllKATAuMQEBdjI.