October-15th-2020, 04:04 PM
Hi Benjamin,
the point with the MAC ID is common Raspberry Pi sense and not Hilscher specific. You can use google search to find several links where this is described.
As next I want to give you a hint how you can test any RESTful API yourself using a browser like google chrome for example. It works with Firefox as well.
Any modern browser has the option to enable debugging HTML web pages. So as with google chrome. So visit the netPI main page and choose from the chrome browser's three dots in the upper right corner the option "tools/development tools ... ". A new window will be opened next to the netPI web page.
In this window you have several tabs you can choose to look into, the most important one for you is the "network" tab. In this tab all the web browser's API calls to the netPI web pages are recorded message by message. So now login to netPI as usual ... you will see the requested login message being recorded under "headers" and you see also the response from netPI under "response" and the cookie. You should see basically the very same messages as those you call via the curl command. Then go on further to other netPI web sites you want to get recorded and analyse them ... by this method you will get out where your problem is with ease.
Thx
Armin
the point with the MAC ID is common Raspberry Pi sense and not Hilscher specific. You can use google search to find several links where this is described.
As next I want to give you a hint how you can test any RESTful API yourself using a browser like google chrome for example. It works with Firefox as well.
Any modern browser has the option to enable debugging HTML web pages. So as with google chrome. So visit the netPI main page and choose from the chrome browser's three dots in the upper right corner the option "tools/development tools ... ". A new window will be opened next to the netPI web page.
In this window you have several tabs you can choose to look into, the most important one for you is the "network" tab. In this tab all the web browser's API calls to the netPI web pages are recorded message by message. So now login to netPI as usual ... you will see the requested login message being recorded under "headers" and you see also the response from netPI under "response" and the cookie. You should see basically the very same messages as those you call via the curl command. Then go on further to other netPI web sites you want to get recorded and analyse them ... by this method you will get out where your problem is with ease.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
