Welcome!On this forum you can discuss iRidium with other users. iRidium consist of 2 main components - i3 pro app and iRidium Server. Please post here your questions, ideas or errors you find.
Please send your questions to support team as a private messages.
Please see www.onvif.org (http://www.onvif.org)
There is a great opensource Home Automation System, called openHAB available. The problem of those systems is actually lack of nice looking GUIs for users.
iRidium could solve that problem if there would be a feature available, which could connect to OpenHAB server over ethernet.
Did anyone try this? What options are available?
Use the attached project,
Set the IP Address to the GC driver to local ip of the global cache device you have.
run the project
Device is shown online
Unplug the network connector from the global cache device
the device still shows in the emulator the device is connected.
Next, turn off\unplug the network cable on your system running the emulator so that there is no network access.
The emulator still shows that the global cache driver is connected.
Update::: I have tested this with KNX IP Router, this will timeout the connection when the timeout value is reached with both cases. It should put the driver into a offline state the moment the internet connection is down.
Then I tested this with the AV TCP driver, again the same as the GC Driver.
To conclude; firstly there should be a configurable timeout setting for all drivers like the KNX IP Router driver.
Secondly, the moment that the internet connection is lost, ie no wifi, wifi card turned off and with wired network connections, network card gets disabled or network cable unplugged then ALL drivers configured in the project should be pushed into an offline state.
Can we have support for the iTach Flex Relay and sensor cable in the Clobal Cache Driver. Plugged into the iTach Flex allows you to control 4 Relays and monitor the states of 4 inputs
ALL the new HDL Wireless devices have also a 4channel drycontact input. When an input is changed, the modules automatically send out a "Dry contact broadcast message". But iRidium does not recognize these messages. So you have to repeatly request the status of each channel on every wireless device over and over again. Please include the broadcast message datagram into iRidium PRO as soon es possible, so iRidium can react directly to an input change. And also decreasing the bus traffic!
I attached a screen shot. I have a status request for channel1 and channel2 running every 10 seconds. When the status changes, you see that the module automatically send out a broadcast of each channel that is changed (Line 39 and 51). In this case channel2 changed from closed to open and back again to closed.
So, iRidium has to process the OP-Code 15D0 correctly!
Martin Lang - MEB Austria
Customer support service by UserEcho