search

NorthernMan54 / node-red-contrib-homebridge-automation

Homebridge and Node-RED Integration
Apache License 2.0
105 stars 18 forks source link

Beta Test for Version 0.1.0 #54

Closed NorthernMan54 closed 1 year ago

NorthernMan54 commented 4 years ago

Backlog of Enhancements for Version 0.1.0

Functional Improvement for long standing issues

New Features

Housekeeping

Installation

To install the beta version, please use this command

cd .node-red
npm install homebridge-automation@beta

To rollback to the production version please use

cd .node-red
npm install homebridge-automation@latest
NorthernMan54 commented 4 years ago

@dxdc What else is on the list?

dxdc commented 4 years ago

this looks great @NorthernMan54! A few other ideas?

  1. Switching to axios instead of requests since it's deprecated? Wondering if it will be more stable as well.
  2. Also, for node.timeout (used to set status) maybe add a clearTimeout b/c just reassigning it doesn't necessarily clear the existing one.
gewaechshaus commented 4 years ago

Hey @NorthernMan54,

correct me if I am wrong, but I think you have posted wrong install instructions... (In case of running node-red on a pi/buster)

Change npm install homebridge-automation@beta

To npm install node-red-contrib-homebridge-automation@beta

Cheers Jan

NorthernMan54 commented 4 years ago

@gewaechshaus You are are correct, typo in that. Also as a FYI, I got distracted with other things and have not used the BETA for anything yet. The master branch is the most recent code base.

CaseyRo commented 3 years ago

@NorthernMan54 expecting any new betas?

NorthernMan54 commented 3 years ago

Actually I have not been focused on this recently, been playing with esp32/esp8266 devices receiving and sending 433mhz signals lately

dxdc commented 3 years ago

@NorthernMan54 As far as sending signals, this product is excellent:

https://bondhome.io/

They have a local API, totally extensible, as well as an iPhone app. Receiving signals is another story though... although I have some good experience with rtl_433 (SDR library) which is a fun way to do it.

NorthernMan54 commented 3 years ago

I had been using sdr’s connected to a RPI ( homebridge-rtl ) but have are looking to improve my deployment and use an esp8266

this is one device im building, esp8266 with RXB6 running RFLink

71858C06-F65D-492F-BDBB-38DCDD417B0F

dxdc commented 3 years ago

Nice! I have some ESP8266 also (is that a nodeMCU?), but it looked fairly tricky to program the Rf module... and I didn't have much luck with it. I had not seen RFLink! That looks really interesting, seems like a better type of SDR then and more energy efficient?

Would be very curious what that looks like. I have some ESP8266 code I can share too that I used to create a simple webserver and have some experience with SPIFFS too for storage. Ultimately, hooking this to MQTT for bidirectional communication would be amazing.

NorthernMan54 commented 3 years ago

Thanks for offering to share your code.

I have been focused on leveraging other people's frameworks and just submitting pull requests to add any features I need. Am currently looking at openmqttgateway. I found rolling my own package from scratch not really worth the effort.

dxdc commented 3 years ago

@NorthernMan54 openmqttgateway reminds me of Tasmota, though I think Tasmota may be more full featured (possibly more so than you'd need)? I've had a lot of success with that.

https://tasmota.github.io/

The rules engine in Tasmota is exceptional though. You can have it take specific actions after power cycle, etc.

NorthernMan54 commented 3 years ago

Two thumbs up on Tasmota ( I flashed my fleet of random purchases and device creations over the years to Tasmota during the summer ). And created a plugin Homebridge-tasmota to simplify management. After seeing how feature rich it was, I have stopped playing around with random code.

Unfortunately though for my use case, Hampton Bay Ceiling Fans, GE Ceiling Fans and random 433Mhz sensors Tasmota doesn't work. My V2 Device ( ESP8266 and CC1101 ) is starting to look promising with OpenMQTTGateway.

What I'm looking to create is a transmitter module for 303Mhz, 315Mhz and receiver for 433Mhz. And also IR. Once I complete the design am looking at a mini production run of 3 units ( 2 for me and one for a buddy ). If it looks like I'm jumping around a bit, in early December I had started using the RXB6 module, and at the same time ordered a CC1101 with a 6 week delivery. It showed up earlier this week, and after hooking it up, I went wow, this is night and day better than the RXB6 approach and hence parked it. For the RXB6 approach I was also going to use separate transmitter modules.

This is an ESP32 connected to a CC1101 Module running openmqttgateway

IMG_5831

dxdc commented 3 years ago

This looks really interesting! I'm curious how your production goes with it.

You've seen the ceiling fan replacements though w/ Sonoff (can be flashed w/ Tasmota)? https://sonoff.tech/product/wifi-diy-smart-switches/ifan03

Those would work to replace the controllers in your fans, but seems like your use cases may be different. Rf is king in terms of speed and battery life though, nothing can beat it as far as I know.

I've been messing around a little bit with Tensorflow Lite using Coral (https://coral.ai/docs/edgetpu/models-intro/)

It allows you to run simple, exportable machine learning models which are super easy to generate from https://teachablemachine.withgoogle.com/

Would be cool to pair with an HB plugin of some kind for a motion sensor or occupancy sensor or even just plain MQTT. Really cool to see how far you are pushing the envelope of HB integration!

coast3r commented 3 years ago

Recently installed node-red. Nodes were working before update to 1.3.0 and 1.3.1. Running v0.0.79, installed via the Manage palette menu. PIN is entered and after deployed, the following is displayed in the log: 25 Feb 15:35:44 - [error] [hb-status:86adf5a5.2e176] 437:Can't find device Does appear to be related to the very recent Homebridge update to 1.3.x. Will continue to look into this.

NorthernMan54 commented 3 years ago

Double check your device names in each node, am thinking the device name changed for one of your nodes.

and by double check I mean double click each node individual and ensure the name isn’t blank on the device screen

coast3r commented 3 years ago

Tried with a clean re-install of the nodes and an empty flow. [Inject] > [HB Status] > [Message]. The PIN has been set in the configuration node. Have also restarted Homebridge and Node-Red. Both are running in Docker. Could have been clearer in my earlier message. It was working with Homebridge 1.2.x. Have been unable to reach Homebridge after 1.3.x upgrade. Currently, my home bridge server is not found and the Device list remains blank.

coast3r commented 3 years ago

Took another look at my Docker settings and changed network_mode to host. This has fixed the issue for me. Perhaps this setting got changed recently while making some other edits to my install. Things are working for me now. Thanks for the advice to double-check everything.

NorthernMan54 commented 3 years ago

Glad to hear you resolved your issues @coast3r