Recent content by tigers

Ti my understanding HASSOS (or whatever they call it now) is a full operating system featuring only HA and its plugins. That is: on the raspberry you can only install HA and are limited to his plugins and add-ons, nothing else can run on it. The core version is instead simply an "app" on the...

But does this work without HASSOS? I prefer using a core installation of HA, to have more freedom of running other things on the raspberry. Also I like to have things separated so I'm case of failure of one of them the rest will keep going.

Hi, as a total noob I did it twice myself with your setup I'll try to explain it in simple words. They will probably be incorrect or simply wrong, but I hope they'll help you. It's not the easiest task since omnilinkbrodge needs some c libraries that are windows only and must be emulated in...

The cost are quite high and I probably would've to pay customs too. I'll give a call to my original installer to see if he has some spares

I think it’d be shorter, easier and more future proof to change the name in the customize.yaml. You can also do a global customization and change icons,names, etc. it accepts wildcards, so maybe you can do it with a few lines of code. Edit: you can also add a 'friendly name' properties to any...

Will this work on an European board? I’m in Italy and my OPII was rebranded by an Italian reseller, I bought an upgrade chip from the years ago (when the rooms option came out) but haven’t upgraded ever since. I’m on version 3.9 maybe, so not long behind, but since the OPII is now sadly end of...

Sorry, cant help you even if they seem quite common chips. I was looking for what chip the temperature sensors use, I assume it’s the LM34 then?

This has been introduced in 2023.8 update for all mqtt entities. It's not a problem per se and omnilink already used a prefix so it didn't need it. This didn't broke anything for me, I don't know if it should be addressed, there's plenty of info in home assistant doc, maybe someone could take a...

Hi, my sample house is wired to a omni pro ii console, that communicates with home assistant via mqtt. The console was installed 20+ years ago and it's beginning to have problems, so I'm thinking of a way to switch to something more up to date. I figured a way to substitute anything except the...

I'm experiencing the same issues, I was thinking of some bad caps like someone wrote in the beginning, but it may as well be an ethernet problem, since it may have begun when I changed my old 10 mb switch for a new one. Is there a way I can look at the logs and see if this may be the problem...

I believe that's because the omnilink is the "device", with lots of entities associated. I don't think that this can be changed with the current Home Assistant setup, maybe this could be done if omnilinkbridge starts to present them to mqtt as different devices.

Hi, I had some problem with my OPII console yesterday (stuck in some system reset loop - a RAM cleanup from the installer setup seems to have fixed it, reloaded all my config with PC ACCESS to be sure, so I'm pretty sure the names in the OPII console are still the same). Problem is that this...

The MQTT server IP address is missing, so it doesn't know WHERE to send the data (you must enter the IP of the server running Mosquitto). I believe the values in square brackets [] are in your file but you have left them out for security reasons. If not, that's another problem.   I'd check that...

Also, one of the big noews with the latest Mosquitto version is that it does not allow anonymous access to the MQTT server by default. This should not be a problem if you have a HASSIO install, but is a concern for whoever is using the so called "core" install (i.e. a plain Raspberry Pi with...

I tried with HACS but didn't succeed. You can find my post explaining how I installed everything. I'm running your exact config: Raspbian 32 bit on a Raspberry 4B with 128 Gb SSD I had lying around.