I don’t think that’s right. Isn’t Home Assistant OS the NEW name for HASSOS?
#1 Requirements : Home Assistant Core (Comes with HomeAssistant OS)
#2 Requirements : Home Assistant Core (Comes with HomeAssistant OS)
#3 Requirements : Home Assistant Core (Comes with HomeAssistant OS)
#4 Requirements : Home Assistant Core (Comes with HomeAssistant OS)
#5 Requirements : Home Assistant Core (Comes with HomeAssistant OS)
I believe am running what you’re calling HASSOS…
yes. you are correct.
I just thought of another possible useful feature that could be added by separating the server from HA.
We could actually use HA to control two zwave js servers. that way if you needed to you could have two physically separated zwave networks and be able to control them from one HA instance as long as they were accessible over the same network. it would just require HA to allow multiple zwave js integrations.
Does anyone know if that’s even feasible and if so if it’s in the roadmap or how the best way to suggest it if not?
I could do a FR but we all know how much attention those tend to get…
Thank you!
Secondly, if I understand correctly, there are two incarnations, and isn’t the underlying code for Z-Wave JS currently different from what’s in ZwaveJS2MQTT and that there is a desire for them to be merged &/or to merge the ZwaveJS2MQTT Control Panel into the core add on?
I guess what should really be added in a nice graphical way is that the MQTT broker also handles other Mqtt events, than only those events coming from and going to the ZwaveJS Add-on. It is after all the main distinction between this 2 architectures, and does make the world of difference.
Like this stuff?
Maybe depending on your use case.
But in this discussion it only would tend to confuse things even further.
I’m not sure I really know the nuts and bolts of things deep in the code but they should be very similar if not the same.
The only difference between the various incarnations is the way that they communicate with HA.
And that the zwavejs2mqtt incarnation has a UI control panel while the others don’t.
I don’t think they will add it into the add-on. it will make more sense to add it into the zwave js integration itself.
Yes, sorry, I’m still using HASSOS as shorthand. I’ll stop to avoid confusion. I’m talking about the basic Home Assistant OS installation on a Pi.
Where did you get this list of requirements? I’m pretty sure you can’t run NodeJS and therefore #1 on a Home Assistant OS Supervised installation, can you? We don’t have that access to the system. Similarly with #2, since that is what the new Zwave JS Add-on is for, the wrapper for the zwavejs server (which is included in #3). We can, however run #3 as an Add-on, and of course, #4 and #5 are specific for our basic installation. But to run #5, we need either #4 or #3. Hopefully someone can confirm/correct.
I can install #1…
…but I’m sure I don’t want to!
No, the new Z-Wave JS is not a wrapper for OpenZWave (Beta) 1.6.
I was running that until a couple of days ago.
The absolute core for both might be the generic OpenZWave project but OpenZWave (Beta) was basically a pull from Justin’s QT-OpenZwave.
Ah, OK, that expains it. You’re 1,2,3,4,5 are different than my 1,2,3,4,5. I was referring to the 5 different elements of ZWave JS described by @JumpMaster to which I was replying. I think you took those to mean the five things listed in Petro’s post. We are talking two different things. 
Ah! Apples vs Oranges! Native Indian vs Asian Indian. Male brain vs Female brain…
We need to use the same dictionary!
So, I am using @JumpMaster’s #4. Home-Assistant Z-WaveJS Addon & #5. Home-Assistant Z-WaveJS Integration
What do you mean? Like this?
Yep, exactly like that! Cool! 
I don’t have a need for it but I’ve seen others talking about using zwave like that many times in the past.
I guess I shouldn’t have made an assumption that you could only have one instance like most of the other stuff only allows.
So, I three anomalies with my blinds…
15:52:43.132 CNTRLR starting inclusion process...
15:52:43.157 CNTRLR handling add node request (status = Ready)
15:52:43.158 CNTRLR the controller is now ready to add nodes
15:52:57.158 CNTRLR handling add node request (status = NodeFound)
15:52:57.163 CNTRLR handling add node request (status = AddingSlave)
15:52:57.168 CNTRLR handling add node request (status = ProtocolDone)
15:52:57.168 CNTRLR stopping inclusion process...
15:52:57.230 CNTRLR handling add node request (status = Done)
15:52:57.231 CNTRLR done called for 30
15:52:57.231 CNTRLR finished adding node 30:
basic device class: Routing Slave
generic device class: Multilevel Switch
specific device class: Unused
supported CCs:
· Basic (0x20)
· Multilevel Switch (0x26)
· Z-Wave Plus Info (0x5e)
· Association (0x85)
· Association Group Information (0x59)
· Version (0x86)
· Manufacturer Specific (0x72)
· Device Reset Locally (0x5a)
· Powerlevel (0x73)
· Binary Switch (0x25)
· Battery (0x80)
· Configuration (0x70)
controlled CCs:
15:52:57.231 CNTRLR » [Node 030] Assigning return route to controller...
15:52:57.238 CNTRLR the inclusion process was stopped
15:52:57.741 CNTRLR [Node 030] Configuring Z-Wave+ Lifeline association...
15:52:57.824 CNTRLR [Node 030] Beginning interview - last completed stage: None
15:52:57.825 CNTRLR [Node 030] new node, doing a full interview...
15:52:57.825 CNTRLR » [Node 030] querying protocol info...
15:52:57.839 CNTRLR « [Node 030] received response for protocol info:
basic device class: Routing Slave
generic device class: Multilevel Switch
specific device class: Unused
is a listening device: false
is frequent listening: true
is a routing device: true
is a secure device: unknown
is a beaming device: true
maximum baud rate: 40000 kbps
version: 4
15:52:57.847 CNTRLR [Node 030] Interview stage completed: ProtocolInfo
15:52:57.847 CNTRLR » [Node 030] pinging the node...
15:52:57.915 CNTRLR « [Node 030] ping successful
15:52:57.915 CNTRLR » [Node 030] querying node info...
15:52:58.079 CNTRLR « [Node 030] node info received
supported CCs:
· Z-Wave Plus Info
· Association
· Association Group Information
· Version
· Manufacturer Specific
· Device Reset Locally
· Powerlevel
· Multilevel Switch
· Binary Switch
· Battery
· Configuration
controlled CCs:
15:52:58.087 CNTRLR [Node 030] Interview stage completed: NodeInfo
15:52:58.089 CNTRLR [Node 030] ManufacturerSpecificCC: doing a partial interview...
15:52:58.090 CNTRLR [Node 030] VersionCC: doing a partial interview...
15:52:58.090 CNTRLR [Node 030] trying to load device config
15:52:58.095 CNTRLR [Node 030] device config loaded
15:52:58.095 CNTRLR [Node 030] ZWavePlusCC: doing a partial interview...
15:52:58.096 CNTRLR [Node 030] BatteryCC: doing a partial interview...
15:52:58.097 CNTRLR » [Node 030] querying battery status...
15:52:58.364 CNTRLR « [Node 030] received response for battery information:
level: 100
15:52:58.365 CNTRLR [Node 030] MultilevelSwitchCC: doing a partial interview...
15:52:58.366 CNTRLR » [Node 030] requesting current switch state...
15:52:58.617 CNTRLR [Node 030] BinarySwitchCC: doing a partial interview...
15:52:58.618 CNTRLR » [Node 030] querying Binary Switch state...
15:52:58.866 CNTRLR « [Node 030] received Binary Switch state:
current value: true
15:52:58.866 CNTRLR [Node 030] ConfigurationCC: Loading configuration parameters from device confi
g
15:52:58.868 CNTRLR » [Node 030] querying parameter #1 value...
15:52:59.072 CNTRLR « [Node 030] parameter #1 has value: 1
15:52:59.073 CNTRLR [Node 030] AssociationCC: doing a partial interview...
15:52:59.074 CNTRLR » [Node 030] querying association group #1...
15:52:59.282 CNTRLR « [Node 030] received information for association group #1:
maximum # of nodes: 1
currently assigned nodes: 1
15:52:59.284 CNTRLR [Node 030] AssociationGroupInfoCC: doing a partial interview...
15:52:59.284 CNTRLR [Node 030] Interview stage completed: CommandClasses
15:52:59.285 CNTRLR [Node 030] Interview stage completed: OverwriteConfig
15:52:59.285 CNTRLR » [Node 030] requesting node neighbors...
15:52:59.300 CNTRLR « [Node 030] node neighbors received: 1, 3, 8, 9, 12, 21, 22, 23, 26, 27
15:52:59.300 CNTRLR [Node 030] Interview stage completed: Neighbors
15:52:59.301 CNTRLR [Node 030] Interview completed
15:52:59.301 CNTRLR [Node 030] The node is ready to be used
Client disconnected
Code 1000:
New client
Not that it matters, but OZW Beta allows it too. Very useful for testing.
I’ve tried excluding/including one of the stubborn nodes but end up with the same result. I’ve restarted the ZWJS server, the integration, HA and the entire box…
Any suggestions?