Recent content by arakasi55

I managed to sort it out after taking a break and removing my blinkers, lol. Firstly, when I did the configuration, I missed the save button in the config section the first time around and clicked save at the bottom under network, which consequently lost the settings i'd added. When I...

I'm in a similar situation. I'm migrating from HA and OLB running in Docker containers on a Debian installation to a new HAOS running as a Proxmox VM. I've restored my backup, have added the OLB add-on and done the configuration, but i'm not getting any entities coming through. I deleted all...

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...

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...

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

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...

  This would be my suspicion. I have two OT7's in my office, both are able to display video streams no problem from 7 cameras, however they only work with MJPEG streams.

Hi Pete, I removed this line but it has had no effect. I am all but convinced it has to do with the thermostat code in OmniLinkBridge but cannot find a way to contact Ryan short of logging an issue on his GitHub

Thanks, ill Try removing it and see how it goes. Regarding your linked article, it seems to be the opposite of my particular issue: This overload of meanings means that values are converted to the user's desired display unit, but the string which is appended for display is the unit used by the...

Yes, mine is set to metric with temps set to C homeassistant: # Name of the location where Home Assistant is running name: Home # Location required to calculate the time the sun rises and sets latitude: -37..... longitude: 144..... temperature_unit: C # Impacts weather/sunrise...

Almost. HA temps are all in Fahrenheit. Omni is sending C, MQTT sees C, by time it reaches HA its in F. The code I linked to on Ryans GitHub under thermostat has to be the culprit, but I cannot find where that code resides 1 - Omni Panel ==> Homeseer Omni Plugin ==> temperature values are fine...

Sorry, to clarify, that image from Homeseer is using the HAI plug in, not MQTT

Not sure what they were at that exact point in time, but currently are 19 and 29.5c

Thanks Pete. It definitely seems like it's a setting in OmniLinkBridge as the MQTT messages are being sent with the temperature values in F    This is what is being sent from OmniLinkBridge   { "current_temperature_topic": "omnilink/thermostat1/current_temperature"...

Thanks Pete. I wonder, on Ryan's GitHub site, I see in the climate.py code there is reference to Farenheit. Do you know where that file resides? In the meantime, i'll try recreating the card as you suggest