OmniLinkBridge to integrate Home Assistant, SmartThings, Node-RED

[grantlewis]

No, @pete_c, I haven't. It's still appearing.

 

[pete_c]

Gonna try an experiment today and put the thermostat manually in the configuration yaml.
 
So using MQTT explorer and Homeseer see:
 
[sharedmedia=gallery:images:1184]
 
The configuration yaml template for MQTT HVAC looks like this in an example.
 



 

# Full example configuration.yaml entry
climate:
- platform: mqtt
name: Study
modes:
- "off"
- "cool"
- "fan_only"
swing_modes:
- "on"
- "off"
fan_modes:
- "high"
- "medium"
- "low"
power_command_topic: "study/ac/power/set"
mode_command_topic: "study/ac/mode/set"
temperature_command_topic: "study/ac/temperature/set"
fan_mode_command_topic: "study/ac/fan/set"
swing_mode_command_topic: "study/ac/swing/set"

So will attempt today to do the same except for using the OmniStat Values and put this template in to configuration dot yaml.
 
Note all of this is guessing right now as I have been tweaking the configuration yaml file with all sorts of things relating to MQTT but nothing yet relating to the Omnilinkbridge.
 
Reading values see:
 
1 - omnilink/thermostat1/hold_state - off / on
2 - omnilink/thermostat1/fan_mode_state - off / on
3 - omnilink/thermostat1/mode_state - heat / off / cool
4 - omnilink/thermostat1/temperature_cool_state - here seeing 78 and invalid
5 - omnilink/thermostat1/temperature_heat_state - here seeing 70 and invalid
6 - omnilink/thermostat1/current_temperature - see current temp
7 - omnilink/thermostat1/current_operation - idle / heat / cool

 

[pete_c]

Gave up trying to edit the above post...
 
On the GitHub Ryan posted:
 

Thermostats

SUB omnilink/thermostatX/current_operation  
string idle, cool, heat

SUB omnilink/thermostatX/current_temperature  
int Current temperature in degrees fahrenheit  

SUB omnilink/thermostatX/current_humidity  
int Current relative humidity

SUB omnilink/thermostatX/temperature_heat_state  
SUB omnilink/thermostatX/temperature_cool_state  
PUB omnilink/thermostatX/temperature_heat_command  
PUB omnilink/thermostatX/temperature_cool_command  
int Setpoint in degrees fahrenheit

SUB omnilink/thermostatX/humidify_state  
SUB omnilink/thermostatX/dehumidify_state  
PUB omnilink/thermostatX/humidify_command  
PUB omnilink/thermostatX/dehumidify_command  
int Setpoint in relative humidity

SUB omnilink/thermostatX/mode_state  
PUB omnilink/thermostatX/mode_command  
string auto, off, cool, heat

SUB omnilink/thermostatX/fan_mode_state  
PUB omnilink/thermostatX/fan_mode_command  
string auto, on, cycle

SUB omnilink/thermostatX/hold_state  
PUB omnilink/thermostatX/hold_command  
string off, hold

 

[123]

 MQTT Explorer shows the two entities

 
As mentioned in my previous post, you can use MQTT Explorer to delete retained messages. 
 
Click on a topic then click the red 'RETAINED' button to delete the topic's retained message.
 
I believe the latest version of MQTT Explorer lets you delete all retained messages in a hierarchy of topics. Select the thermostat's root topic, click delete, and it should delete the whole thing in one operation.

 

[grantlewis]

OK, starting to make more sense now. Thank you for the clarification.
 
I'm seeing topics in two places: in Omnilink / Thermostat
 

 
and in homeassistant / climate / omnilink / thermostat1
 

 
Only the second topic has that Retained button on the right. So I'm guessing that's the right one?

 

[pete_c]

@Grant...
 
You cannot break the OmniLinkBridge and HA doing this as the Mosquitto broker is just handling or the in between of transaction messages.

 

[grantlewis]

Thank you, no more error messages! I appreciate your patience -- I'm not very thoroughly versed in MQTT and it all seems rather opaque.
 
So to confirm: as long as discovery is disabled, those error messages shouldn't reappear, right?

 

[pete_c]

I have left my MQTT discovery on in HA.  Try it and see if two thermostats show up.  They should not show up.

 

[grantlewis]

Discovery is on, still no error messages. Fantastic! Thanks again.

 

[pete_c]

Good news Grant!!
 
Do you see the HA error message related to the thermostat as I have shown above?
 
[sharedmedia=gallery:images:1183]

 

[arakasi55]

Hi Pete, did you manage to clear/resolve the above message? I have been receiving that the whole time, but my issue with temps being reported in F rather than C was my bigger priority (still not resolved by the way).
 
I've gone through all of the OmniLinkBridge code and the only area I can find that looks to be doing any conversion is in this file
 
https://github.com/excaliburpartners/OmniLinkBridge/blob/e0d61f091a004cebb619d0f4da24d0e043fdfbd1/OmniLinkBridge/Extensions.cs
 
Now, I'm no programmer, but it is commented to say it's a conversion from the OPII integer values to Celsuis??

 

[pete_c]

Nah.  Haven't had a chance to look for issues.  Been doing outside stuff mostly. 
 
Yes do not understand why there is a conversion to Celsuis when the OP 2 panel outputs in Celuis if you configure it to do so eh?

 

[arakasi55]

It's worth noting that the state topic issue above is a breaking change in 0.95.4 
After updating, the thermostat is now no longer present

 

[pete_c]

As mentioned earlier wasn't tinkering with HA and yesterday decided to update HA...
 
Updated here too to .95.X and see the same now...main lovelace gui page shows....
 
Entity not available: climate.thermostat_1
 
Also noticed that my Firefox ad blocker and ghostery were blocking my scripts / events.  For a bit thought it was HA.
 
My Alexa aps continue to work fine....(TTS and media control)...

 

[arakasi55]

I ended up manually configuring the thermostat as an MQTT device. 
Without the custom card with dual set points, I've resorted to using the simple thermostat card and still have temps showing in F. I'm about to replace the Omni Thermostat with a Zen ZigBee based one as I just don't seem to be getting anywhere with the temp unit issue and OmnilinkBridge