OmniLinkBridge to integrate Home Assistant, SmartThings, Node-RED

[pete_c]

Found how to solve an issue I was having with MQTT / HA this morning.  It may have helped with your Omnistat issue and values.
 
Now it's too late as it is not working these days.
 
Here have been configuring (reconfiguring) my 1-Wire network to using MQTT.
 
I currently have set up two main 1-Wire hubs for temperature only DS18B20 sensors.  I can go up to 5 sensors per device.
 
I was not getting temperature readings from one hub here and using MQTT explorer noticed that the MQTT was not working for one hub.
 
Using MQTT explorer deleted the hub and let it recreate the broadcasts and now it is reading the hub correctly.

 

[grantlewis]

Thought I'd ask here first before making the request on GitHub: Is there an option for excluding an entity class? For instance, I want to maintain access to Omni flags and thermostats in HA but would like to exclude lights.
 
If this isn't currently possible, I'll log it as a feature request.

 

[pete_c]

@arakasi55
 
Just getting to the thermostat stuff.
 
Did you create a custom climate section for your configuraiton.yaml file?
 
Current version of HA doesn't display any thermostat stuff these days.

 

[pete_c]

Tried the following but getting errors on restart.
 
climate:
  - platform: mqtt
    name: thermostat1
#    current_operation:
#      - "off"
#      - "idle"
#      - "heat"
#      - "cool"
    fan_modes_state:
      - "on"
      - "auto"
    hold_state:
      - "on"
      - "off"
    mode_state:
      - "cool"
      - "heat"
      - "auto"
      - "off"
#    current_operation_topic: "omnilink/thermostat1/current_operation"
    current_temperature_topic: "omnilink/thermostat1/current_temperature"
    temperature_heat_state_topic: "omnilink/thermostat1/temperature_heat_state"
    temperature_cool_state_topic: "omnilink/thermostat1/temperature_cool_state"
    mode_state_topic: "omnilink/thermostat1/mode_state"
    fan_mode_state_topic: "omnilink/thermostat1/fan_mode_state"
    hold_state_topic: "omnilink/thermostat1/hold_state"
 
2019-10-18 18:22:09 ERROR (MainThread) [homeassistant.config] Invalid config for [climate.mqtt]: [fan_modes_state] is an invalid option for [climate.mqtt]. Check: climate.mqtt->fan_modes_state. (See /config/configuration.yaml, line 201). Please check the docs at https://home-assistant.io/components/climate.mqtt/
2019-10-18 18:22:17 ERROR (MainThread) [homeassistant.components.mqtt.climate] Exception in async_discover when dispatching 'mqtt_discovery_new_climate_mqtt': ({'current_temperature_topic': 'omnilink/thermostat1/current_temperature', 'temperature_low_state_topic': 'omnilink/thermostat1/temperature_heat_state', 'temperature_low_command_topic': 'omnilink/thermostat1/temperature_heat_command', 'temperature_high_state_topic': 'omnilink/thermostat1/temperature_cool_state', 'temperature_high_command_topic': 'omnilink/thermostat1/temperature_cool_command', 'min_temp': '45', 'max_temp': '95', 'mode_state_topic': 'omnilink/thermostat1/mode_state', 'mode_command_topic': 'omnilink/thermostat1/mode_command', 'modes': ['auto', 'off', 'cool', 'heat'], 'fan_mode_state_topic': 'omnilink/thermostat1/fan_mode_state', 'fan_mode_command_topic': 'omnilink/thermostat1/fan_mode_command', 'fan_modes': ['auto', 'on', 'cycle'], 'hold_state_topic': 'omnilink/thermostat1/hold_state', 'hold_command_topic': 'omnilink/thermostat1/hold_command', 'name': 'Thermostat 1', 'state_topic': None, 'availability_topic': 'omnilink/status', 'platform': 'mqtt'},)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/mqtt/climate.py", line 244, in async_discover

 

[arakasi55]

Hi Pete, here is the config I used when I was running the custom config for the Omnistat. Other than the measurement issue, it worked fine for me at least until 0.96, though I've since stopped using the OmniStat as Fahrenheit to C conversions was too much for the WAF.
 
climate:
  - platform: mqtt
    name: Thermostat
    modes:
      - "auto"
      - "off"
      - "heat"
    fan_modes:
      - "auto"
      - "on"
      - "cycle"
    mode_state_topic: "omnilink/thermostat1/mode_state"
    mode_command_topic: "omnilink/thermostat1/mode_command"
    fan_mode_state_topic: "omnilink/thermostat1/fan_mode_state"
    fan_mode_command_topic: "omnilink/thermostat1/fan_mode_command"
    hold_state_topic: "omnilink/thermostat1/hold_state"
    hold_command_topic: "omnilink/thermostat1/hold_command"
    current_temperature_topic: "omnilink/thermostat1/current_temperature"
    temperature_low_state_topic: "omnilink/thermostat1/temperature_heat_state"
    temperature_low_command_topic: "omnilink/thermostat1/temperature_heat_command"
    temperature_high_state_topic: "omnilink/thermostat1/temperature_cool_state"
    temperature_high_command_topic: "omnilink/thermostat1/temperature_cool_command"
    availability_topic: "omnilink/status"

 

[charliebarns]

After months of issues with the notifier board I am canning it and moving on. I've successfully installed OmniLinkBridge and at this point have notifications working sending emails. First question, can you customize what notifications are sent and to whom? With the notifier board you could specify what types of notifications to send and to whom. I suspect given the versatility of OmniLinkBridge I will learn its many features over the coming months and am just now starting to read about it's integration with HA.
 
thx
 
cb

 

[grantlewis]

After months of issues with the notifier board I am canning it and moving on. I've successfully installed OmniLinkBridge and at this point have notifications working sending emails.

 
I'm in EXACTLY the same boat as you are, charliebarns. Pete_c kindly helped me get to where I am now. Right now I'm working on getting Node-RED to respond to changes in an IMAP email sensor that watches a dedicated gmail address set up for the house. Then I plan to have Node-RED send iOS notifications through the HA app based on that sensor. (I may eventually use the Node-RED email node but wanted to try the platform: imap_email_content first.) I've got a driveway sensor that is very chatty under OmniLinkBridge, and my plan is to just filter out those messages at some point in the process -- either setting up a filter in gmail or else doing it in Node-RED.

 

[pete_c]

Basically what was done here was to enable STunnel to be utilized as an email proxy (TLS/SSL) which will work with both the Elk and HAI panel email.
 
STunnel runs 24/7 on any PC any OS. 
 
So basically you just shut off the TLS/SSL functions on the Elk or HAI boards and send the email to the STunnel proxy.
 
I use GMail for my stuff here but you can utilize any email service with STunnel.

 

[rsw686]

After months of issues with the notifier board I am canning it and moving on. I've successfully installed OmniLinkBridge and at this point have notifications working sending emails. First question, can you customize what notifications are sent and to whom? 

 
Glad to hear you got it working! Unfortunately the notifications can't be customized. I first wrote the software so I could get email alerts. I then realized that building out customizable alerts was reinventing what already existed. I wanted better Z-Wave support for locks so I turned to SmartThings. Long story short SmartThings seems to be unreliable at the worst times. So finally I had enough with cloud based services and wrote the MQTT portion. With Home Assistant, Node-RED, or another product that supports MQTT you can fully customize your notifications and actions. My time has been limited lately and since OmniLinkBridge has been working flawlessly I haven't made any changes to it.
 
The only thing that drives me crazy is when the Zigbee OmniStat 2 thermostats briefly loose connection and OmniLinkBridge reports 0F to Home Assistant. This messes up the temp graphs as the scale goes all the way to 0. I plan to fix this when I get some free time.

 

[pete_c]

Thank you Ryan.
 
The OmniLinkBridge is greatest thing that has happened for the OmniPro 2 panel since the creation of sliced bread.
 
Thank you for providing us a great application.
 
I have recently shut down the Smartthings hub and gone to using Home Assistant MQTT for use with the OmniLinkBridge only.
 
I am sure you are aware that the climate / Omnistat functions do not work with current version of Home Assistant eh?
 
Initally the climate / thermostat functions were warnings then over time got disabled.

 

[rsw686]

Im still running Home Assistant 0.87.0. I heard about the issue, but havent had a chance to update mine and go through the debugging process. While Home Assistant is the best thing Ive found, I cant stand how they dont care about backwards compatibility and are constantly changing and breaking things.

 

[pete_c]

Thank you Ryan.
 
It was working fine with 0.87.0
 
Then after wards updates started with an error message that it would work with errors and it did.
 
Then updated to current version 0.98.4 and the thermostat functions are gone now.  Rest of the OmniPro stuff is working well.
 
Here I have only added some WiFi devices that are Tasmota / Espurna updated for MQTT and Alexa Text to speech which is working well these days.
 
Should I downgrade to Home Assistant V 0.87.0 for time bean?

 

[charliebarns]

Appreciate the feedback guys. So I've managed to get OmniLinkBridge to send messages. I've installed HA and Mosquitto on my Pi3 and I've got them setup with a back interface that shows zone status on one of my OmniPro setups. I'm having trouble trying to set up alarm panel under HA and link it to the OPII. Under entities I don't see alarm panel or status. Does this exist or does OmniLinkBridge not allow control of the alarm state?
 
thx!
 
CB

 

[pete_c]

Enable the Lovelace GUI and you should see the alarm interface. 
 
Or look at the unused entities to see alarm stuff.

 

[rsw686]

I just upgraded to Home Assistant 0.100.3 and see the thermostat issues. I'll see what I can do to get this working.