Unipi-evok plugin digital output

---

I am very happy with my Smart-Home System. Pimatic is running very good on my System with the unipi-evok plugin working on an Unipi Neuron L203.
Now I tried to create a new Device switching digital output, but there is no option in the value list for digital output.
Has anyone an Idea?

Hi, i assume you mean the Digital Relay device.
That device is based on the SwitchActuator and has the state attribute (or variable) you can use. The actions you can apply in rules or via the API are turnOn, turnOff and changeStateTo.

Is this what you need or is it a different question?

To clarify things: The plugin had been originally developed for the UniPi 1.1 board which did not provide for Digital Outputs. It just provided 8 changeover relays. The Neuron boards are also generally supported, but some features may be missing such as the 4 digital outputs provided by the L203. However, this should be very easy for me to add to the plugin as a digital output behaves similar to a digital delay device. @ansie I’ll have a look into this shortly,

Thats what i’m talking bout. Thank You for your answers and efforts.

@ansie I have a released a new version which contains (experimental) support for Digital Output devices. As I don’t have a Neuron board to test with I kindly ask you for you support with testing the stuff.

1. Install the new plugin version v0.3.3 and restart pimatic after installation
2. Start device discovery -> new you should see four UniPi Digital Output devices in the result
3. Add one of the UniPi Digital Output device to your configuration
4. Check the pimatic log for any error messages
5. Switch the UniPi Digital Output on/off
6. Possibly observe the digital output state or check the state via evok web UI. Does “on” in pimatic correspond to a HIGH signal on the hardware output or in evok?

In case the digital output devices are not discovered as expected please enable debug output on the plugin, restart pimatic, and repeat. Please send a transcript of the debug log messages (an excerpt of pimatic_daemon.log)

@mwittig said in Unipi-evok plugin digital output:

Install the new plugin version v0.3.3 and restart pimatic after installation
Start device discovery -> new you should see four UniPi Digital Output devices in the result
Add one of the UniPi Digital Output device to your configuration
Check the pimatic log for any error messages
Switch the UniPi Digital Output on/off
Possibly observe the digital output state or check the state via evok web UI. Does “on” in pimatic correspond to a HIGH signal on the hardware output or in evok?

In case the digital output devices are not discovered as expected please enable debug output on the plugin, restart pimatic, and repeat. Please send a transcript of the debug log messages (an excerpt of pimatic_daemon.log)

new Plugin installed, pimatic restarted, and Device Discovery started, but no Digital Output. So debug log enabled and here is an excerpt.

19:06:56.563 [pimatic-unipi-evok] debug: [UniPiUpdateManager] Starting Web Socket Heartbeat
19:06:56.569 [pimatic-unipi-evok] debug: [UniPiUpdateManager] Heartbeat
19:06:56.667 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “2_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:06:56.787 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “3_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:06:56.911 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “3_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:06:58.518 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “2_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:06:58.650 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “2_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:06:58.767 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “3_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:06:58.884 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “3_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:00.546 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “2_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:00.656 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “2_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:00.766 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “3_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:00.876 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “3_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:00.994 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“modes”: [“Voltage”, “Current”, “Resistance”], “value”: 0.0, “glob_dev_id”: 1, “dev”: “ao”, “circuit”: “1_01”, “unit”: “V”, “mode”: “Voltage”}]
19:07:01.219 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “1_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:01.367 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “1_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:02.567 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “2_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:02.694 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “2_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:02.811 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “3_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:02.927 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “3_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:03.269 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“modes”: [“Voltage”, “Current”, “Resistance”], “value”: 0.0, “glob_dev_id”: 1, “dev”: “ao”, “circuit”: “1_01”, “unit”: “V”, “mode”: “Voltage”}]
19:07:04.533 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “2_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:04.649 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “2_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:04.767 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “3_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:04.885 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“circuit”: “3_01”, “value”: 0, “glob_dev_id”: 1, “dev”: “wd”, “timeout”: 5000, “was_wd_reset”: 0, “nv_save”: 0}]
19:07:05.598 [pimatic-unipi-evok] debug: [UniPiUpdateManager] received update: [{“modes”: [“Voltage”, “Current”, “Resistance”], “value”: 0.0, “glob_dev_id”: 1, “dev”: “ao”, “circuit”: “1_01”, “unit”: “V”, “mode”: “Voltage”}]

@ansie said in Unipi-evok plugin digital output:

new Plugin installed, pimatic restarted, and Device Discovery started, but no Digital Output. So debug log enabled and here is an excerpt.

Thanks testing and reporting back quickly! Even Though the Evok Source Code contains a “digital output” device this does not seem to be exhibit. According to the API docs (which I should have read in the first place) digital outputs and relays are treated the same way. So, possibly they’re also shown as “UniPiRelay” devices. Did you count the number of UniPiRelay devices discovered by pimatic? Does it match up with the number of relays on the board or do you see four more devices which then should correspond to the digital output lines in case. If this is not the case we need to dig deeper.

Yes your right, the digital output shown as relay devices. So now everything works fine.
Thank You

@ansie Excellent!

I may get back to you later to possibly trial some of the extended features available with Neuron boards which are not yet supported by the plugin

• some of the analog outputs can also be used for measuring resistance.
• some of the transistor-based digital outputs can also be used for PWM modulation (e.g. a dimmer)
• LEDs which can be controlled in a manner similar to the digital outputs
• possibly transistor-based digital outputs can be detected by additional properties exhibited through Evok (needs more debug output to fihure this out)