NorthernM

And a PS before I get started. Instructables is awful for managing issues, if you use GitHub I see the comment almost immediately versus here where days go by.Yes the original pattern was killed with iOS 13, but I worked with the homebridge developers on a workaround with almost the same functionality. The plugin behind this now exposes a dummy switch to trigger the motion sensor,

Wow, lots of questionsAnd a PS before I get started. Instructables is awful for managing issues, if you use GitHub I see the comment almost immediately versus here where days go by.1 - On - I had pressed both buttons and captured the 'on' code, as its a unique code2 - 'double tab' - no as their wasn't a matching HomeKit command3 - 'state' - The plugin assumes that on is 100% and works from their.

They recently updated the Homebridge-camera-ffmpeg package and dropped support for Google Drive. The last version with Google drive support is 1.3.0 and can be installed with this commandnpm install -g homebridge-camera-ffmpeg@v1.3.0

I had seen similar issues with older versions of node from a few years ago and am wondering if they broke something again.I did re-validate it last week and everything was working okay. So I’m stumped as to the problem with NPM.I’m stuck right now in regards to what to try, as this is an issue with NPM and not the package.

What version of node and npm is it running, it needs to be something modern. Also some of the older versions of NPM had issues that are resolved with modern versions

Sorry nope

I would suggest starting here, with the camera plugin GitHub repo issueshttps://github.com/KhaosT/homebridge-camera-ffmpeg/issues

Unfortunately not

HomeKit supports multiple homebridge's, so this would be fine. ( I have never used a PiZero, so can't comment on that )Another approach is utilizing an ESP8266, which is significantly cheaper. I use this for my remote monitoring needshttps://github.com/NorthernMan54/homebridge-mcuiot

I have a had another user with a similar challenge recently, and am still working thru it with them here.https://github.com/NorthernMan54/homebridge-dht/issues/21

A RPI 0 should work, but it you goal is small, then I believe there is an HomeKit esp8266 based temperature sensor on GitHub. You should be able to find it with google.

Please open an issue against the plugin on Github, and if you can include a log from the homebridge much appreciated.I checked my setup, and it is working so it must be something minor going on.

I'm sorry but I wrote this in LUA and not c, which is used by Arduino and it is not possible to convert.

If you google the error message "Error: spawn EACCES", it indicates a permission/access on the DHT22 executable. Try this from the directory with the dht22 commandsudo chmod a+rwx dht22

This should be feasible, but for the discussion can you open an issue on the GitHub site?https://github.com/NorthernMan54/homebridge-mcuiot/issues

Unfortunately not

This looks like a problem with installing the MDNS module, and I can think of a couple of things that may work. Try thissudo su -sudo npm install -g --unsafe-perm homebridge-mcuiot

That is a big with some of the more recent versions of NPM, and should be able to be worked around with ( I updated the instructions with the same )sudo su - npm install -g NorthernMan54/homebridge-bme280 --unsafe-perm

Try this, both SSID's need to be replacedlocal module = {}module.SSID = {}module.SSID["Knut"] = { ssid="Knut", pwd = "1787269548654xxx" }module.SSID["Flocke"] = { ssid="Flocke", pwd = "1787269548654xxx" }return module

Fixed, please try again

I just updated bme.lua to support the latest firmware. Please note that I needed to add a couple of new nodemcu modules in step 5 as well.You should be good to go.

Congrats on getting it working ;-)

I’m thinking homebridge isn’t running as user pi You can see which user account is running homebridge with the ps command ieps -ef | grep homebridgeThen run the permission step again

When installing, do you follow this step?2. Add permissions to the account you will be running homebridge from to connect to the i2c bus on the RaspberryPI. Do this as the user you will be running homebridge from.sudo adduser $USER i2cAlso the log you shared would have had more debugging of the sensor during startup, can you share more the log file. Look at step 5.3 for an example.

This step, the output from homebridge shows the connection to the sensor, and the data returned. It likely has an error in your case.3. Start homebridge, the output should look something like this.[12/11/2016, 6:25:29 AM] Loaded plugin: homebridge-bme280<br>[12/11/2016, 6:25:29 AM] Registering accessory 'homebridge-bme280.BME280'[12/11/2016, 6:25:29 AM] ---[12/11/2016, 6:25:30 AM] Loaded config.json with 1 accessories and 0 platforms.[12/11/2016, 6:25:30 AM] ---[12/11/2016, 6:25:30 AM] Loading 0 platforms...[12/11/2016, 6:25:30 AM] Loading 1 accessories...[12/11/2016, 6:25:30 AM] [Sensor] Initializing BME280 accessory...[12/11/2016, 6:25:30 AM] [Sensor] BME280 sensor options: {"i2cBusNo":1,"i2cAddress":118}Found BME280 chip id 0x60 on bus i2c-1 address 0x76[12/1…

This step, the output from homebridge shows the connection to the sensor, and the data returned. It likely has an error in your case.3. Start homebridge, the output should look something like this.[12/11/2016, 6:25:29 AM] Loaded plugin: homebridge-bme280<br>[12/11/2016, 6:25:29 AM] Registering accessory 'homebridge-bme280.BME280'[12/11/2016, 6:25:29 AM] ---[12/11/2016, 6:25:30 AM] Loaded config.json with 1 accessories and 0 platforms.[12/11/2016, 6:25:30 AM] ---[12/11/2016, 6:25:30 AM] Loading 0 platforms...[12/11/2016, 6:25:30 AM] Loading 1 accessories...[12/11/2016, 6:25:30 AM] [Sensor] Initializing BME280 accessory...[12/11/2016, 6:25:30 AM] [Sensor] BME280 sensor options: {"i2cBusNo":1,"i2cAddress":118}Found BME280 chip id 0x60 on bus i2c-1 address 0x76[12/11/2016, 6:25:31 AM] [Sensor] BME280 initialization succeeded[12/11/2016, 6:25:31 AM] [Sensor] data(temp) = { "temperature_C": 18.23, "humidity": 39.1710189421353, "pressure_hPa": 1016.8910377944043}Scan this code with your HomeKit App on your iOS device to pair with Homebridge:^[[30;47m ^[[0m^[[30;47m ┌────────────┐ ^[[0m^[[30;47m │ 031-45-154 │ ^[[0m^[[30;47m └────────────┘ ^[[0m^[[30;47m ^[[0m[12/11/2016, 6:25:33 AM] Homebridge is running on port 51826.[12/11/2016, 6:26:30 AM] [Sensor] Polling BME280[12/11/2016, 6:26:30 AM] [Sensor] data(temp) = { "temperature_C": 18.35, "humidity": 39.27056837670529, "pressure_hPa": 1016.8940344587268}[12/11/2016, 6:27:30 AM] [Sensor] Polling BME280[12/11/2016, 6:27:30 AM] [Sensor] data(temp) = { "temperature_C": 18.29, "humidity": 38.79282900165324, "pressure_hPa": 1016.9261147858624}

Can you share the log from homebridge and in particular the section showing sensor initialization? I’m thInking the issue is settings for the plugin, or account permissions.

I think the challenge is with step 6, and that some installs are a little bit different. Do you know which directory homebridge-dht was installed into? dht22 should be there

Yeah originally I had instructions pointing directly how to download and compile the binary but had to remove that after the website with the source code was no longer available. I made some minor changes to the text now, does it make sense?

The status's are#define DHT_GOOD 0#define DHT_BAD_CHECKSUM 1#define DHT_BAD_DATA 2#define DHT_TIMEOUT 3Check your wiring and connection to the DHT.

Sorry just saw this message, and I fixed the instructions.

I just fixed it, it should be fine now. I had changed the process for making the executable from manual build, to including the executable in the supplied code base.

Sorry just saw this message, and I fixed the instructions.

Looks like they moved hosting providers. I have gone and added the patched and compiled version to the respository. If you download the repository again you will see the file dht22. Just copy it over, and you should be good to go.

support for the dht devices is via pigpio, and I'm just using their dht example code for the interface. According to their documentation it should just work.http://abyz.co.uk/rpi/pigpio/examples.html

That is really a question for Apple, as I'm passing to back to HomeKit the value as returned by the sensor and not dropping the decimal. I looked at the Eve app and I did see the decimal beside the temperature. I think they drop the decimal due to screen real estate.

can you try from scratch building the dht22 command again, I'm thinking it may have been corrupted when it was patched twice. Basically step 7 again.That the dht works with loldht, is a great indicator that the problem is in the build of the dht22 command.

I have updated the instructions in the README here https://github.com/NorthernMan54/homebridge-mcuio...The steps to install are1) Install the latest version of homebridge-mcuiot2) In the README, follow the instructions in 'Optional - Enable access to Google Sheets3) Create a spreadsheet in Google Sheets, and add the spreadsheet id into config.json4) Restart homebridge

Dom,Not sure if your interested, but I recently updated all my temperate sensor plugins to log the data to Google sheets so you can create graphs etc.Sean

Alek,I have updated the package with logging to google sheets, so that you can creates graphs etc. Details on the configuration are included in the README on github

With HomeKit unfortunately not, there is no graphing interface. Over the next few weeks I'm working on creating a google sheets data logger that you could use. Watch this space in about a month.

Homebridge is found herehttps://github.com/nfarina/homebridgeWhen do a google search, mine returns a furnace repair company as number 2 with this as number 1

The service parameter in customer config.json must be dht22. If you changed the executable name to be dht11, there is a different config parameter called dhtExec that you can use.

I think the problem is in the accessory section of your config.json. Can you share your config.json ?

This is feasible, but I have not done this with this sensor yet. I have used loggly to do this with other sensors. You may want to look at that.

This is normal. I set this up as a single temperature sensor accessory that also supports pressure and humidity as well. In home, if you look at the details you should see humidity as well, pressure is not supported by Home.

If you look in the homebridge log, it will log the current temperature etc every minute.

You need to add to config.lua this linemodule.YL69=0

Dom,In config.lua you can remove this line, as it isn't neededmodule.SSID["The_Beach"] = "brownieg"And the most important part, change this line frommodule.Model = "BME-GD"to module.Model = "BME"And that should be it

Rasket787I had created a custom version of the plugin that added support for Atmospheric Pressure, and had sent a pull request back to the original developer months ago asks them to merge the changes into the original plugin but that never happened. To use the custom version I created, use this command instead of the one listed in step 5.1sudo npm install -g https://github.com/NorthernMan54/homebridge-bme28...This will install the version with support for Atmospheric PressurePS I also went back and changed the instructable to include the same command as well. Tks

Dom,It looks like the nodemcu is working correctly, but the true test is when you poll it for data. Can you try this from the command line on your machine.curl 192.168.1.158It should respond with something like this{ "Hostname": "NODE-18A6B3", "Model": "DHT-YL", "Version": "1.1", "Data": {"Temperature": 20.9, "Humidity": 27, "Moisture": 1024, "Status": 0 }}Also, what sensor do you have attached? DHT or BME ?

That looks perfectly normal, when you restart homebridge and the timeout happens do any errors appear on the nodemcu? I was expecting to see some type of exception on the nodemcu.

Dom,The error you showed from homebridge is a timeout when trying to reach your nodemcu device. It looks like it was seen and discovered, but when it was queried by the plugin the request timed out. Is the nodemcu working okay, was there any errors on its console?

Dan,As the data is just read from the chip, I'm wondering if you may have the wrong chip? They also make a bmp280 chip, which is just temperature and pressure and no humidity. Could they have sold you a bmp280 by mistake? If you pull up the data sheet, they explain what the numbers on the chip mean. And the bmp280 would be a K, while the bme would be a U at the start of the second row.

I was looking at the code and it should support multiple sensors, you would just need to add an additional accessory per device in the config.json. See below for an updated fragment.To wire the second sensor, it would go in parallel with the first, except you would need to change the i2c bus address of the second one to 0x77. To change the i2c address you would need to look at the data sheet for the sensor you purchased.Good luck"accessories": [{ "accessory": "BME280", "name": "Sensor", "name_temperature": "Temperature", "name_humidity": "Humidity", "options": { "i2cBusNo": 1, "i2cAddress": …

I was looking at the code and it should support multiple sensors, you would just need to add an additional accessory per device in the config.json. See below for an updated fragment.To wire the second sensor, it would go in parallel with the first, except you would need to change the i2c bus address of the second one to 0x77. To change the i2c address you would need to look at the data sheet for the sensor you purchased.Good luck"accessories": [{ "accessory": "BME280", "name": "Sensor", "name_temperature": "Temperature", "name_humidity": "Humidity", "options": { "i2cBusNo": 1, "i2cAddress": "0x76" } },{ "accessory": "BME280", "name": "Sensor1", "name_temperature": "Temperature1", "name_humidity": "Humidity1", "options": { "i2cBusNo": 1, "i2cAddress": "0x77" } } ],

Dom,I had created a pull request for the original developer of the BME280 plugin adding Atmospheric pressure to returned data, but it has not been merged back into the original code base yet. Until that happens you can install my version of the plugin, which supports atmospheric pressure, with this commandsudo npm install -g https://github.com/NorthernMan54/homebridge-bme280And restart homebridgeThis will add the Atmospheric pressure sensor. Please note the Atmospheric pressure is not supported by the Apple Home App, but with the third party home kit apps like Elgato Eve.

Dom,Just looking at the two different screen shots, and I see 2 different issues. First for your implementation of homebridge, you need config.json into the directory /root/.homebridgeSecond for the invalid json, I step 5.2 I had originally included just a fragment of the config.json file outling the bme280 config. I have since gone back and changed the example in 5.2 to the complete config.json file.With those 2 changes you should be good to go.

pigpiod should autostart on reboot. Check to see if you have /etc/init.d/pigpiod, and if it is having errors during startup.

Try rebooting

Did step 7.1 complete successfully?sudo apt-get update sudo apt-get install pigpio python-pigpio python3-pigpioIt should setup autostart of pigpiod.

I updated the plugin to create a separate humidity sensor, so if you update the plugin you will now see a humidity as a separate sensor. With this change I added some additional options to the configuration file to allow naming of the each. Please see step 6.2.

Awesome, that is a very unique idea.

In the plugin itself, a second accessory would need to be created. If you give me a could of days, I can add it to the plugin.

Dom,Looking at the homebridge output it is complaining that the homebridge config.json file can not be found in the directory /root/.homebridge.Have you created the config file? And is it in that directory?

I sent an email, but did not hear back. Do you need help with the config or connecting the sensor?

Richard,In step 7.6 this creates the file dht22.sudo cp DHTXXD /usr/local/bin/dht22sudo chmod a+x /usr/local/bin/dht22With the CP command, I'm copying the file DHTXXD and renaming it to dht22.

Hummm, can you share the output from homebridge when starting? I suspect the plugin isn't starting correctly.

Hector,Multiple sensors are supported by the plugin, just not documented in the Instructable. In the readme.md file the config.json setting for multiple sensors is documented. If need more assistance, please let me know.

Dom,Looking at the screen shot, it appears that you are not the correct directory. When I wrote the steps I assumed they would all be executed sequentially, and Step 7.3 assumes that you are already in the DHTXXD directory. This is where you would have been at the end of Step 7.2. Try it again, but execute cd DHTXXDbefore executing the steps in 7.3 again.good luck ;-)

That is odd, have you rebooted since the install?

Perfect, nowgcc -Wall -pthread -o DHTXXD test_DHTXXD.c DHTXXD.c -lpigpiod_if2cp DHTXXD /usr/local/bin/dht22chmod a+x /usr/local/bin/dht22

Hector, at the end of the cp command in step 7.3 there is a period . that you are missing.

Try this, remove the double node_modules and add a .cp /usr/local/lib/node_modules/homebridge-dht/test_DHTXXD.patch .

Just looking back at that section, and your correct their only should be one node_modules directory and not 2. Try it again, but remove the second node_modules directory.

Hector, looking at the output I see that the dht22 command didn't return anything. What happens when you run 'dht22' from the command line? Can you post that output.Also looking back at the instructions, I missed the step to create a cputemp command, so have added it as 8. If you don't want to see your raspberry pi cpu temperature, please use the shorter config.json in step 6. This will fix the cputemp error as well.

Aaron,I went back and changed the patch instructions, and hopefully made them easier to follow this time. And I have included the patch file as part of the homebridge plugin, so you will need to run sudo npm install -g homebridge-dht before following the instructions.

Dom,I took a quick look at the code, and realized all that was missing to support multiples was exposing the gpio pin as a config parameter, and passing it 'dht22'. I added the couple of lines, and it should now be supported.But if you are looking at doing multiple sensors, I have started using multiple ESP8266/Nodemcu modules, and deployed them where I wanted to collect a temperature. Take a look at this on Github https://github.com/NorthernMan54/homebridge-mcuiot