Closed joe8mofo closed 4 years ago
:wave: Thanks for opening your first issue here! If you're reporting a :bug: bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be useful.
+1 I run Home Assistant within Hyper-V so no direct access to local ports. My Z-wave stick is on Raspberry Pi.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Noone is looking at this request. This shouldn't be stale.
I'm not adding this level of logic to the add-ons. In general, if you need these solutions, it would be better to run ZWave2MQTT itself on a separate device.
Proposing that socat be added to the container. Then allow a variable to be passed to call socat on boot before the zwave daemon starts.
An example socat call would be: socat PTY,link=/dev/zwave,raw,group=root,mode=777 TCP::7676
We would want to pass as a variable.
This would enable people to use zwave as serial devices over IP. If someone had a zwave stick on a raspberry pi or maybe they have a vera; this would enable the device to be passed to the zwave2mqtt addon.