Driver Releases

kirky27's Avatar
User User
  • Posts: 46
  • Thanks: 0

Re: Driver Releases

2 years 5 months ago - 2 years 5 months ago
#2074
I cannot access the system.
Still frozen like the screenshot below:
Last edit: 2 years 5 months ago by kirky27.

Please Log in or Create an account to join the conversation.

kirky27's Avatar
User User
  • Posts: 46
  • Thanks: 0

Re: Driver Releases

2 years 5 months ago
#2075
This is what I see when I try to access my server.

Please Log in or Create an account to join the conversation.

David Li's Avatar
Admin Admin
  • Posts: 1027
  • Thanks: 99

Re: Driver Releases

2 years 5 months ago - 2 years 5 months ago
#2076
This is what I see when I try to access my server.
Tip 5 Clear Cache
allonis.com/support/documentation?view=category&id=412

Or, ensure you are using the right IP address that might have changed on a reboot if you didn't reserve the IP address on your router DHCP server.
current IP is 20.10
 
Last edit: 2 years 5 months ago by David Li.

Please Log in or Create an account to join the conversation.

PhoenixF15E's Avatar
User User
  • Posts: 91
  • Thanks: 3

Re: Driver Releases

2 years 5 months ago
#2079
As far as I know I need to reverse engineer the http interface on the HTP-1 as I cannot find any reference to a protocol document. What is your HTP-1's ip address? 
I don't own an HTP-1, but it is on my short-list of future processors, so I am interested.

The HTP-1 has a robust and straightforward control scheme outlined in the users manual attached below starting at page 94.  There are NEC IR codes that are passed via wget or curl.

Operating status is passed via a config.json that is returned after any HTTP request.  If someone has an HTP-1 and posts a copy of the file here, that would be appreciated.  

As an example of what level of integration can be achieved, go here  and look at Pink Soda's custom controller, which is now integrated into the HTP-1's firmware.  VU meters, parametric control, exBEQ, etc., are a few examples of what can be done.  The controller is written in Vue and the source code is here on Github,

Kyle

 

Please Log in or Create an account to join the conversation.

Fattykidd's Avatar
User User
  • Posts: 150
  • Thanks: 3

Re: Driver Releases

2 years 5 months ago
#2080
As far as I know I need to reverse engineer the http interface on the HTP-1 as I cannot find any reference to a protocol document. What is your HTP-1's ip address? 
I don't own an HTP-1, but it is on my short-list of future processors, so I am interested.

The HTP-1 has a robust and straightforward control scheme outlined in the users manual attached below starting at page 94.  There are NEC IR codes that are passed via wget or curl.

Operating status is passed via a config.json that is returned after any HTTP request.  If someone has an HTP-1 and posts a copy of the file here, that would be appreciated.  

As an example of what level of integration can be achieved, go here  and look at Pink Soda's custom controller, which is now integrated into the HTP-1's firmware.  VU meters, parametric control, exBEQ, etc., are a few examples of what can be done.  The controller is written in Vue and the source code is here on Github,

Kyle



I've already sent my config.json to David quite a while ago. 
In the meantime it's been working very well to just have the webui brought up on the remote screen. 
I've also decided to use ezbeq instead of the built in beq functionality so I can blacklist a certain beq author. All of which is accessable from the smartremote screen. 
 

Please Log in or Create an account to join the conversation.

kirky27's Avatar
User User
  • Posts: 46
  • Thanks: 0

Re: Driver Releases

2 years 5 months ago
#2081
I’ve already cleared the cache on my desktop. 
I’m seeing the same thing on multiple devices.
Should I rebuild from the Master image?
I actually have a working USB backup which I could use but if it’s relatively simple to build from scratch I might do so.
Did you get to investigate the Storm driver?
Thanks.

Please Log in or Create an account to join the conversation.

Time to create page: 0.336 seconds