- Posts: 443
- Thank you received: 36
Zwave hardware suggestions?
- Nillaz
- Topic Author
- Away
- User
-
Less
More
2 years 4 months ago #1573
by Nillaz
Replied by Nillaz on topic Zwave hardware suggestions?
I'm not 100% sure but I don't think so. I don't even see that driver in the list of available options.
Please Log in to join the conversation.
- Nillaz
- Topic Author
- Away
- User
-
Less
More
- Posts: 443
- Thank you received: 36
2 years 4 months ago #1574
by Nillaz
Replied by Nillaz on topic Zwave hardware suggestions?
Thanks David. I will look through this.allonis.com/support/documentation?view=category&id=159
Please Log in to join the conversation.
- Nillaz
- Topic Author
- Away
- User
-
Less
More
- Posts: 443
- Thank you received: 36
2 years 4 months ago #1577
by Nillaz
Replied by Nillaz on topic Zwave hardware suggestions?
The link provided could use an edit for clarity, but by and large they helped me get Zwave set up with a minimum of fuss. My plugs are working as expected and respond to commands instantly and I'm looking forward to expanding the network. Thank you again!
Please Log in to join the conversation.
- David Li
- Offline
- Admin
-
Less
More
- Posts: 1019
- Thank you received: 99
2 years 4 months ago #1580
by David Li
Replied by David Li on topic Zwave hardware suggestions?
Good to hear you are up and running!
You are lucky that we just did a pass through the documentation to add the 64 bit paths for the current Master Image.
And I just did some additional small tweeks to the documentation for clarity post your comments.
Was there something in particular that wasn't clear in the doc?
Thanx!!
You are lucky that we just did a pass through the documentation to add the 64 bit paths for the current Master Image.
And I just did some additional small tweeks to the documentation for clarity post your comments.
Was there something in particular that wasn't clear in the doc?
Thanx!!
Please Log in to join the conversation.
- Nillaz
- Topic Author
- Away
- User
-
Less
More
- Posts: 443
- Thank you received: 36
2 years 4 months ago #1591
by Nillaz
In the "Configure ZWave JSUI Software" section:
It states to launch docker container "interactively" and make sure there are no errors, but what does it mean to launch interactively, and what constitutes an error? I just ran the command and watched it do it's thing. When it was finished it didn't return any "ERROR", but several of the lines said "WARN" in relation to a few files (I don't remember which ones were which now, but I remember at least some of them pertaining to .json files). Is a WARN the same as an ERROR? I continued to proceed and everything seems to have gone fine.
Further down it says that the Discoverer preset needs to be set to homeassistant. It doesn't say that this option isn't surfaced until you enable the MQTT Discovery toggle and mine was disabled by default. Some quick googling told me how to find this and homeassistant is the default so no big deal but this could be clearer.
Otherwise things were pretty straightforward.
Replied by Nillaz on topic Zwave hardware suggestions?
Mostly minor things that I was a little concerned with in the moment but that I was able to figure out or otherwise get pastGood to hear you are up and running!
You are lucky that we just did a pass through the documentation to add the 64 bit paths for the current Master Image.
And I just did some additional small tweeks to the documentation for clarity post your comments.
Was there something in particular that wasn't clear in the doc?
Thanx!!
In the "Configure ZWave JSUI Software" section:
It states to launch docker container "interactively" and make sure there are no errors, but what does it mean to launch interactively, and what constitutes an error? I just ran the command and watched it do it's thing. When it was finished it didn't return any "ERROR", but several of the lines said "WARN" in relation to a few files (I don't remember which ones were which now, but I remember at least some of them pertaining to .json files). Is a WARN the same as an ERROR? I continued to proceed and everything seems to have gone fine.
Further down it says that the Discoverer preset needs to be set to homeassistant. It doesn't say that this option isn't surfaced until you enable the MQTT Discovery toggle and mine was disabled by default. Some quick googling told me how to find this and homeassistant is the default so no big deal but this could be clearer.
Otherwise things were pretty straightforward.
Please Log in to join the conversation.
Time to create page: 0.354 seconds