UPGRADE IP 9 verfügbar!
Timberwolf VISU jetzt mit NEUEM Layout Editor
Freie Anordnung, Reihenfolge und Größe der Widgets - viele weitere Verbesserungen
Infos im Wiki: https://elabnet.atlassian.net/l/cp/06SeuHRJ

NEU! Insider & Leistungsmerkmale FÜR ALLE freigeschaltet
Damit kann nun jeder das Upgrade vornehmen und VISU & IFTTT testen. Alle Info hier: viewtopic.php?f=8&t=5074

[FR] Z Wave Integration

Planungen, Rollout, Termine, Aktionen, Leistungsmerkmale, Wünsche, Fragen, Anleitungen
Forumsregeln
  • Denke bitte an aussagekräftige Titel und gebe dort auch die [Firmware] an. Wenn ETS oder CometVisu beteiligt sind, dann auch deren Version
  • Bitte mache vollständige Angaben zu Deinem Server, dessen ID und dem Online-Status in Deiner Signatur. Hilfreich ist oft auch die Beschreibung der angeschlossener Hardware sowie die verwendeten Protokolle
  • Beschreibe Dein Projekt und Dein Problem bitte vollständig. Achte bitte darauf, dass auf Screenshots die Statusleiste sichtbar ist
  • Bitte sei stets freundlich und wohlwollend, bleibe beim Thema und unterschreibe mit deinem Vornamen. Bitte lese alle Regeln, die Du hier findest: https://wiki.timberwolf.io/Forenregeln
Antworten

Ersteller
gavindjharper
Reactions:
Beiträge: 4
Registriert: So Nov 11, 2018 2:34 am
Hat sich bedankt: 4 Mal
Danksagung erhalten: 5 Mal

Z Wave Integration

#1

Beitrag von gavindjharper »

I don't know whether Z Wave Integration is something that would be considered as a future addition to the Timberwolf Server.
Even if this was something on the far horizon, it would be interesting to know if there was an appetite for this, and to get an idea of what the future hardware implementation might look like.

My preference is always to run things over wires wherever possible. I am not massively sold on Wireless devices, however, I know that some are, and whilst some things could be done over e.g. KNX RF, there are other things for which there are not devices.

My own personal interest, would be for using this for access control privileges for Yale Keyless Connect Locks.
https://www.yale.co.uk/en/yale/couk/pro ... door-lock/
I'm currently changing my plans from previous thoughts for using a Loxone system, and so I have had to come up with a plan B for access control. I have a lot of doors, and these seem like a cheap, robust solution.

Thinking about integration of Z Wave...

EU Z wave frequency 868 mhz

There are already lots of USB dongles. I wonder whether ElabNET would have an appetite for developing their own solution, or maybe could "white box" someone elses sticks for use with the server.

In terms of the "philosophy" for Z Wave integration, obviously many services like Smart Things have intelligence "out in the cloud", which doesn't fit with the Timberwolf Philosophy. I would look to something like "Hubitat" for inspiration.

https://hubitat.com/
https://www.techhive.com/article/333488 ... racti.html

They have all of their logic locally (which would be the case if Z Wave devices could be connected through the TW logic engine).
Also one of the great things about their dongle, is that you can have multiple interfaces, which all integrate into the Z wave network.
Living in a house with thick slate walls where wireless doesn't travel well, I would be shredding batteries trying to get devices to "hop" back to base through other Z wave devices, so the idea of being able to have multiple transceivers wired back and powered over PoE would really appeal...
See comment below in another forum.

https://community.smartthings.com/t/wir ... /140839/10

In terms of the physical hardware, whilst I'm aware that some extensions will connect to Timberwolf over USB, I could see advantages for ZWave of having an IP based solution, so that if you want to distribute transceivers over a wide area, it is simple using POE and standard CAT cable.
Hubitat has built-in support for synchronizing multiple Hubitat Elevation hubs together over Ethernet. Typically, you would designate one hub as the primary. This hub would run all whole home automations, provide dashboard access, perform cloud integrations, etc… The second hub would be used in the remote location, and would have its own Z-wave and Zigbee networks. These devices would then be mirrored to the primary hub as virtual devices. If desired, local automations on the secondary hub are possible, assuming all of the necessary devices are connected to this hub.
For the software development, it might be worth taking a look at OpenZWave
http://openzwave.com/
Antworten

Zurück zu „Timberwolf Hardware“