If you have any links as to what the config topic should contain that would be very helpful.
Thanks
Here’s the main topic but I’m sure you’ve seen that.
Each device type has different topics. I would suggest to start on an on/off switch or a non colour light as those are relatively easy. A binary sensor is even easier of course.
As an example here is a non colour dimable light from HE exposed to HA - this is the config topic for HA Discovery within homeassistant/… which is the configured top level discovery topic within HA
{
“name”: “vDimmer”,
“availability_topic”: “homie/he43/$state”,
“payload_available”: “ready”,
“payload_not_available”: “init”,
“unique_id”: “Hubitat-MQTT:_vdimmer”,
“state_topic”: “homie/he43/vdimmer/onoff”,
“command_topic”: “homie/he43/vdimmer/onoff/set”,
“payload_on”: “true”,
“payload_off”: “false”,
“value_template”: “{{ value }}”,
“on_command_type”: “first”,
“brightness_state_topic”: “homie/he43/vdimmer/dim”,
“brightness_command_topic”: “homie/he43/vdimmer/dim/set”,
“brightness_value_template”: “{{ value }}”,
“brightness_scale”: 100,
“device”: {
“identifiers”: “HE_77347”,
“name”: “vDimmer”,
“sw_version”: “pre4 beta 3e”,
“model”: “he43”,
“manufacturer”: “Hubitat”
}
}
and here is the corresponding actual device that is being published to MQTT from HE, within a homie/he43/vdimmer/… topic structure but that is not important - the mcsMQTT structure will be what you use. In homie/… you add /set to the end of a topic to control it. mcsMQTT will have it’s own variant.
I’ve been using HS3 for many years, and now that I’m considering a whole new system I’ve been debating HS4 or HASS. I’m leaning strongly towards HASS, based on everything I’ve read. Does anyone have anything negative to say about it?
@fluffypony I think you’ll always find quite a few negative views about HA - but the important context I feel is that they are fewer generally than any other major platform. Discontented users post many many times more frequently than happy ones.
HA is evolving very nicely at the moment to address a lot of those concerns making it appropriate and approachable to far more users.
People are very opinionated about various aspects of their HA system and what suits one will not always suit another. If it works for you and you like the general implementation of the app and it’s capabilities I think your 95% there and can work around the other 5% either through tolerance or learning so you can adapt or contribute.
1 Like
While I’m here to stay, and mostly having fun figuring out all of the things I can do that weren’t imaginable under HS3, there are some negatives worth mentioning.
Mainly, and this is certainly not a top priority for everyone, but the Z-Wave support has a way to go. The instability has led me to unearth an old Vera Edge for Z-wave handling.
There is what I would describe as a steep learning curve. It isn’t insurmountable, but the often out of date or altogether missing documentation doesn’t make the learning process as enjoyable as it could be. For me it seems like things just sort of clicked on in my mind one day.
All things considered however, I really can’t believe what I use to put up with running HS3 and how I didn’t catch on to HA a lot quicker than I did.
1 Like
@fluffypony - Don’t let someone else’s opinion affect your decision. Do your research and, may be do what I’m doing, running HS3 and HA side-by-side during the transition. BTW, HASS is kind of going away in favor of HA since “hass” in german means hate or hatred.
@xAPPO is right. Just like product reviews, people are much more likely to write a negative review than they are a positive one.
My experience has been similar to @SentryBot2281. When compared to HST, the pace of HA development, and therefore changes, can be dizzying. Is that even a word? Anyway, the group of HS users making the transition is growing by the day so I’m sure you’ll have some good support.
1 Like
Hi Kevin,
I got a basic script working for binary sensors but I think I’m going to step back and actually put an implementation plan together before I go too far. My original thought was to just create a list of dev refs and walk through the list. That may be tricky since not all of those devices may map cleanly to one of HA’s MQTT components. I need to experiment a bit more to see what would work best.
kenn, great, i love to test when your ready 
Hi all,
I have been following this thread with a lot of interest as I am also thinking of dropping HS3 to go to HA. Right now my plan is to use HS as my 60 node Z-Wave controller as I have integrated the pyhs3 custom component from Ken and it seems to be working. I can see and control my Z-Wave devices that are connected to HS with HA Lovelace UI. I cannot seem to get HA automations working as I get an error stating the device does not have a unique entity ID. Is there any way to add the HS Z-wave devices into an HA automation?
Hi @ando1,
Are you using the homeseer component from marthoc or the one from my fork here: EDIT: https://github.com/kmitch95120/homeseer/tree/additional-sensors? Mark didn’t merge my last pull request so you may not have the code that’s creating the unique entity ids for devices. I’m using z-wave devices from HS3 in HA automations so I know it works.
EDIT: Fixed link to branch within my fork that has the latest code.
I am using the fork from your code. I am trying to create the automations in the UI. Is that the way you are doing it or are you using automations.yml?
Using the UI. Most of my automations are sunrise/sunset based.
Can you give me an example of an automation you are trying to create so I can try it out as well?
Hi Ken…I must have been doing something else wrong as now it seems to work. I am also moving to node red as this seems to be a better way for me to understand the automations.
during my journee, i still have some concerns regarding the use of HA. especially since i have some big event structures in HS3 and i have todo a lot of yaml programming to get that working in HA.
Im still in a phase of running both systems next to each other, i managed to get 80% of my devices active in both systems. and now trying to find (the best)solutions for my specific needs (GUI, TTS via sonos, Google assistant, blueiris integration, Alerting, counting values, counting usage, timers, chromecasting cameras, sending video by email, managing automations/script, possibly node-red, etc)
Next to that i still have an issue with my shutters being inverted (i using marthocz integration with the new fork) but i cant find a way to invert them, also tried rewiring them, but then it wont work as expected either.
i think i could rebuild 90% in HA, but its going to be a real PITA to do so, and another concern is howto catalog the events and scripts, to make them logical easy to find, and maintainable.
again im coming from a 2000+ devices and 800 events HS3 system, so thats also something to take into account 
@kenm Do you know if the HomeSeer HSM200 Z-Wave Multi-Sensor is supported by pyhs3? I just added one in my HS3 network and cant seem to find it in HA. Here is a screen shot of the configuration screen in HS
@Bart_Bakels - I’m also running HA and HS3 side-by-side and I"m finding things that I like and dislike about both. The last I looked I had over 900 devices and 1200+ events. I use a plugin called EasyTrigger which adds some great trigger options that aren’t standard with HS3. The biggest challenge for me is the z-wave network that’s now grown to 80 nodes.
@ando1 - Glad you got it working. I"m going to start experimenting with node red myself so we can figure things out together. The child devices of the HSM200 should be supported but we may have to modify the Device Type (String) to match the strings I posted earlier in this thread. The configuration screen shot you posted is for the root device, which doesn’t actually have any functionality. The devices you want to look at are the “Associated Devices” shwon at the bottom of the root device configuration screen.
Hi Bart,
I’m almost certain I’m going to reverse the way the script would work. Rather than writing this is VB and running on the HS side, I’m going to write it in Python and grab the HS device information using the JSON interface. I’ve still got a lot of tinkering to do before I’ll have something to test.
1 Like
Just keep me posted, great to hear there are more people in the same boat here
Btw i use easytrigger as well.
@kenm Here are all the child devices their respective Device Type:
Color Control = Z-Wave Switch Color
Home Security = Z-Wave Notification
Luminance = Z-Wave Sensor Multilevel
Temperature = Z-Wave Sensor Multilevel
Also do you know if there is a way to make my HS-WS200+ switches show up as lights under HA. The WD200+ dimmers show under the light domain but the WS200+'s show under the switch domain.
Also, I found these 2 videos that helped me tremendously for Node Red:
I’m not sure about Color Control so I’ll have to investigate that one.
Try to change the others as follows:
Home Security = Z-Wave Sensor Binary
Luminance = Z-Wave Luminance
Temperature = Z-Wave Temperature
I’m not certain about Home Security since it might be one of those status devices that can accept multiple values, not just 0 or 1.
What is the Device Type (String) for the WS200+ and the WD200+ devices?
Thanks for the links to the Node Red videos.