Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does netRemote.sys.alarm.status work on all devices? #19

Open
tagru opened this issue Jan 23, 2020 · 6 comments
Open

Does netRemote.sys.alarm.status work on all devices? #19

tagru opened this issue Jan 23, 2020 · 6 comments

Comments

@tagru
Copy link

tagru commented Jan 23, 2020

I am just wondering if anyone has ever got the alarm settings to work via netRemote?

If I use the request
http://xx.xx.xx.xx/fsapi/GET/netRemote.sys.alarm.status?pin=1234 (doc)
the answer is:

<fsapiResponse>
 <status>FS_NODE_DOES_NOT_EXIST</status>
</fsapiResponse>

Is is device or firmware dependent if it works? Could @flammy maybe share where he got the information from in the first place?

I am currently testing with a Hama IR110 (FW:ir-mmi-FS2026-0500-0084_V2.11.16.EX69632-2A10)

Thanks and regards,
tagru

@JRInge
Copy link

JRInge commented Jul 5, 2020

I am testing using a Roberts Stream 93i and a Pure Evoke C-F6, both of which have an alarm function. The netremote.sys.alarm.status node doesn't seem to be implemented on either radio, and neither do the other alarm nodes listed in FSAPI.md. I get the same FS_NODE_DOES_NOT_EXIST response.

@flammy
Copy link
Owner

flammy commented Jul 7, 2020

I added the node with some other nodes that are not supported on my own device (like multiroom support).

This indicates that the feature is from a newer chipset or firmware.

@dizzy314
Copy link

On my Karcher DAB 7000i the netRemote.sys.alarm.config node is writable but returns alway FS_FAIL:

$ curl -s 'http://192.168.3.44/fsapi/SET/netRemote.sys.alarm.config?pin=1234&value=xxx'
<fsapiResponse>
<status>FS_FAIL</status>
</fsapiResponse>

Does anybody know how the value should be formatted for this node? Internally the alarms are stored as a 18+18 byte array but this format doesn't work as value for this node.

@MatrixEditor
Copy link

MatrixEditor commented Jul 22, 2023

@dizzy314, the prototype for that node is defined by:

prototype = [
    Argument(name="key", length=1, type=ArgType.ARG_TYPE_U32),
    Argument(name="on", length=1, type=ArgType.ARG_TYPE_E8),
    Argument(name="time", length=7, type=ArgType.ARG_TYPE_C8),
    Argument(name="duration", length=1, type=ArgType.ARG_TYPE_U8),
    Argument(name="source", length=1, type=ArgType.ARG_TYPE_E8),
    Argument(name="preset", length=1, type=ArgType.ARG_TYPE_U8),
    Argument(name="repeat", length=1, type=ArgType.ARG_TYPE_E8),
    Argument(name="date", length=9, type=ArgType.ARG_TYPE_C8),
    Argument(name="volume", length=1, type=ArgType.ARG_TYPE_U8),
]

As this node is a ListNode, you can just "select" an item by providing its key value. If you query all list nodes, you will be able to see all available keys that can be used as the value in the SET request.

@einarav
Copy link

einarav commented Jul 14, 2024

@MatrixEditor I do not understand how I shall build the HTTP request with this, could you please provide an example? I get the same error as @dizzy314 when trying to set an alarm. I use a Roberts istream revival 2 which has the alarm function.

@MatrixEditor
Copy link

@einarav as I stated before, a LIST node can be used to select a stored preset. Therefore, using key=... should set the desired alarm configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants