I’m running mosquitto broker as an add-on.
I deleted everything and set it up the second time and it works fine now. I “think” I might have typo’d the mqttuser password when I first entered it.
Yes, Please. This would be most helpful.
RE: HomeSeer export via MQTT Discovery
You may already be aware of this, but for those who don’t, I have the following suggestion:
If possible, include device information in the discovery topic’s payload.
Here’s a simple demonstration. The following script will make Home Assistant create a ‘signal strength’ sensor that is part of an ‘Aqara contact sensor’ device. Note the inclusion of the device-related parameters in the payload. The payload can, of course, be presented all on one line but I’ve prettified it for legibility.
sequence:
- service: mqtt.publish
data:
topic: homeassistant/sensor/frontdoor_contact_linkquality/config
retain: true
payload: >
{
"name": "Frontdoor Contact Linkquality",
"device_class": "signal_strength",
"state_topic": "zigbee2mqtt/0x00158d000232a9ad",
"unique_id": "0x00158d000232a9ad_linkquality_zigbee2mqtt",
"device": {
"identifiers": ["zigbee2mqtt_0x00158d000232a9ad"],
"name": "0x00158d000232a9ad",
"model": "Aqara door & window contact sensor (MCCGQ11LM)",
"manufacturer": "Xiaomi",
"sw_version": "Zigbee2mqtt 1.12.2"
}
}
When the user goes to Configuration > Devices, the device named “0x00158d000232a9ad” will appear in the list. It serves as a convenience for the user, revealing the device’s details and the entity, or entities, that represent it within Home Assistant.
If I create another discovery topic whose payload contains information for another entity but the same device information, this new entity becomes part of the same device. The following screenshot shows the device now also has a binary_sensor representing the door’s state.
1 Like
Well… My first update of HA was an EPIC failure.
Excuse my misuse of any terms as I’m just figuring that out as well.
Running HASSOS 3.12 and HASSIO 0.107.7 in a Virtualbox VM on a Macbook Pro. (not sure if that matters).
- Took a snapshot of HA using Supervisor->Snapshots and copied it off to the host system.
- Took a VM snapshot as well.
- Applied HASSOS 3.13 update without any problem. At least none that I could observe.
- Took another snapshot of HA using Supervisor->Snapshots and again, copied it off.
- Took another VM snapshot.
- Applied HA 0.108.5 updated and didn’t observe any errors.
- Web UI never came back. I could ping the ip address but no UI.
I took a snapshot of the VM in the failed state and restored to the snapshot taken in step #5 and everything came up OK with 3.13 and 0.107.7.
Any guidance on how to go about determining what went wrong would be much appreciated.
I am having some similar weird problems with 0.108.x as well on my QEMU VM installation and have not spent the time to look into it. I have stuck with 0.107.7 for now…
Indeed. This guy goes to the doctor and says “Doctor, it hurts when I do this.” and the doctor replies “Then stop doing that.”.
I’m intrigued by this thread. When I first ventured down Home Automation, some guy tried to talk me into HS. I ran for the hills when I saw the prices on everything, glad I did! Anyways, welcome to HA.
Thanks @petro for the welcome. The same thing that drew me to HS in 1999 is what brought me here. The ability to have almost full control over my environment and to develop and contribute whenever possible. I wrote VB and VB.net code for years and switched to Python in the late 2000’s. I love the fact that I was able to go right to the source code yesterday when I was researching an error message related to the serial package. Enhancing the pyhs3 library and homeseer custom component was one of my first tasks.
Ha… sorry for the little value added. I guess it was just to say “me too” but it did not offer a solution. May try it again this weekend… and find out what is going on. My wild guess would be some library folder issues with the Python installation which is a pretty typical thing.
Not at all. Thanks for replying. I’m glad (well, sort of) that I’m not the only one running into a similar problem. For me, the VM snapshot is the fastest recovery method until I learn more about how to restore an HA snapshot without the UI.
Thanks again.
So… Can anyone help me learn how to repurpose my Hometroller SEL? I’m sorry! I cant find anything anywhere.
Thanks for any help.
Hi Carlos ( @Cmriquinha9798),
I’d recommend you set the SEL aside for a little while and get yourself a Raspberry Pi starter kit instead. You would need to install a base Linux OS on the SEL as well as either HA core or HA supervised, but in either case you would have to be the Linux admin for your OS. With the RPi, you can get a ready to run HASSIO image that should have you up and running in a short time without having to get your hands dirty with the OS stuff.
Later, you can re-purpose the SEL, or possibly even sell it and stick with the RPi.
Hi Guys,
Question for you, after searching for 20 minutes in the forums…
HomeSeer had a Plugin called BLRadar (and DooMotion in the early days) These plugins helped me to define occupancy/active zone functions based on motion sensors.
In other words I want to have an active zone entity based on the fact a motion sensor detected motion within a definable time range.
Thanks for helping,
Rien
Sounds like something achievable with a Template Binary Sensor. It would replicate the state of an existing motion sensor but only during a specified time period (outside of that range it would always report off).
Alternately, you could use Template Sensor to report three possible states: on, off, and something like none to represent its state during off-hours. It depends on the use-case.
Hey Ken,
Thanks a ton! That’s EXACTLY what I was looking for. Some clear direction. Very much appreciated!!
Glad it helped. I’ve started looking into hassos and hass.io a bit more to understand why it’s only available for RPi or as a VM. It seems like a bare metal x86-64 image could be possible, but that’s based on my very limited knowledge of how hass.io works.
Here’s where I started: HomeAssistant for newcomers: What it is, what is hassio, hassos, hassbian, 101 and cookies
I have a couple of Zotac Intel atom based boxes that would make perfect HA platforms, much like the SEL.
There’s many ways to install directly.
Use the Alternative installs and the virtual environment (this is a python venv) not a virtual machine and you can install on almost anything with python (correct version of course).
But you only get “core” with this method, right? I want the full-on docker method with hassos, supervisor, add-ons, etc. but I want it running on a bare-metal x64 platform.
The recent name change of “core” didn’t change product.
Why do you want the other pieces that are only needed when running inside docker?
hassos is just the os layer that provides docker which “core” then runs inside. Supervisor just manages the docker instance. Add-ons you just install manually or with hacs. This would be the purest of bare-metal installs.
OK. Thanks for the education. I’m still learning and trying to figure all of this out as the names and terms seem to be changing under my feet. I did not realize you could install add-ons manually. That’s definitely a big piece of info.