FAQ

Frequently asked questions

We are currently in the process of setting up a list of FAQs. For the time being please feel free to direct all questions and feedback to our forum.

Please follow this link to reach our forum community
Add License manual to Raspberry Pi and nomos Box

To add a license manually, login to your box via SSH over an FTP-Client (e.g. CyberDuck or FileZilla) using the Username: root and the Password: nomos. Then navigate to /root/nomos/config/ and place the key-file “NXS97891Fxx_MyHServ_name.key” in this directory. Once copied in there rename the key-file to “nomos.key” and the box will active itself.

Manual Update nomos Box

Please clear a USB-Stick (should not be bigger then 4GB), unzip the update-file "Nomos4Linux_version.zip" and copy the “install.sh” and “nomos.tar.gz” on the stick. Then insert it to the nomos Box and wait till the right LED goes off again, we execute the Restart of the Daemon automatically. You should then see in the Wizard under Basic Configuration/Software Update  the corresponding version number next to Controller.

Manual Update Raspberry Pi

Please clear a USB-Stick (should not be bigger then 4GB), unzip the update-file "Nomos4RPI_version.zip" and copy the “install.sh” and “nomos.tar.gz” on the stick. Then insert it to the Raspberry Pi and wait approx. 60 seconds before removing it, we execute the Restart of the Daemon automatically. You should then see in the Wizard under Basic Configuration/Software Update  the corresponding version number next to Controller.

Can I use my Receiver as a CEC gateway?

No, this is not supported by most AVR's in the industry

Can you discover CEC?

yes, please find here a log that shows the discovery of CEC controllable devices: Zu Beginn ist der RPI nicht angeschlossen: 08:43:31.147 - cec: bus configuration: 08:43:31.148 - cec: device 'nomos', LA: 1, PA: 1.0.0.0 08:43:31.150 - cec: device list: Dann wird er an einen beliebigen Eingang des AVR angeschlossen und erkennt zunächst den bereits eingeschalteten TV: 08:43:57.193 - cec: device list changed: TV 08:43:57.195 - cec: bus configuration: 08:43:57.197 - cec: device 'TV', LA: 0, PA: 0.0.0.0 08:43:57.198 - cec: device 'nomos', LA: 1, PA: 1.0.0.0 08:43:57.552 - bc: <CEC><TV=ON></CEC> Kurze Zeit später erkennt er auch die beiden anderen (ausgeschalteten) Geräte: 08:44:06.750 - cec: device list changed: TV,BD PLAYER,RECEIVER 08:44:06.750 - cec: bus configuration: 08:44:06.750 - cec: device 'TV', LA: 0, PA: 0.0.0.0 08:44:06.750 - cec: device 'nomos', LA: 1, PA: 1.0.0.0 08:44:06.951 - cec: device 'BD Player', LA: 4, PA: 2.0.0.0 08:44:07.155 - cec: device 'RECEIVER', LA: 5, PA: 1.0.0.0 Dann schalten wir den BluRay Player ein und bekommen kurz danach das Feedback: 08:46:16.615 - network: udp message from 192.168.1.201:1037, size 31 bytes 08:46:16.617 - parser: parsing sequence: <CEC><POWER_ON=BD PLAYER></CEC> 08:46:16.619 - parser: command: CEC - POWER_ON=BD PLAYER 08:46:18.227 - cec: turning 'BD PLAYER' on 08:46:18.229 - parser: reply sequence: <CEC>POWER_ON=|OK</CEC> 08:46:18.231 - network: message parsed 08:46:27.095 - bc: <CEC><BD PLAYER=ON></CEC> Dito für den AVR: 08:46:43.737 - network: udp message from 192.168.1.201:1037, size 30 bytes 08:46:43.740 - parser: parsing sequence: <CEC><POWER_ON=RECEIVER></CEC> 08:46:43.741 - parser: command: CEC - POWER_ON=RECEIVER 08:46:44.748 - cec: turning 'RECEIVER' on 08:46:44.750 - parser: reply sequence: <CEC>POWER_ON=|OK</CEC> 08:46:44.752 - network: message parsed 08:46:56.319 - bc: <CEC><RECEIVER=ON></CEC> Dann schalten wir den TV aus: 08:46:56.397 - network: udp message from 192.168.1.201:1037, size 25 bytes 08:46:56.399 - parser: parsing sequence: <CEC><POWER_OFF=TV></CEC> 08:46:56.401 - parser: command: CEC - POWER_OFF=TV 08:46:56.464 - cec: switching 'TV' off 08:46:56.465 - parser: reply sequence: <CEC>POWER_OFF=|OK</CEC> 08:46:56.467 - network: message parsed 08:47:01.529 - bc: <CEC><TV=OFF></CEC> Da der BluRay Player von sich aus mit dem TV kommuniziert, schaltet er sich automatisch mit aus: 08:47:03.359 - bc: <CEC><BD PLAYER=OFF></CEC> Und zum Schluss ziehen wir das HDMI Kabel wieder aus dem RPI: 08:47:20.208 - cec: device list changed: 08:47:20.210 - cec: bus configuration: 08:47:20.212 - cec: device 'nomos', LA: 1, PA: 1.0.0.0

How do we connect to CEC Bus?

Over HDMI on the RaspberryPI and / or the Pulse Eight USB-Adapter.

What about security issues?

Unfortunately security issues cannot be ruled out completely when it comes to technology, especially not when operating a system that users can access at any time and from any place in the world. Nevertheless, we give you the option of simply disabling the cloud access.

Now the connection between the nomos daemon and the cloud server is encrypted with a unique key pair. An attack is only possible when the cloud server is compromised (a problem basically all services offered on the internet face) or the emergence of a security gap in the encryption system. In the latter case, we would offer an automatic update and close the security gap .

The connection between the nomos app and the nomos daemon is encrypted via the cloud end-to-end. This means that the nomos app exchanges a key with the nomos daemon when both are in the same network. Once the app connects with the daemon via the cloud this key is used. The data exchanged between the app and the daemon can therefore neither be read on the Internet nor on the cloud server . A breach is possible only if the app data is stolen (on the mobile device) and this theft goes unnoticed .