The analogclock part here is the name of the top-level node. The code you linked is quite old and from a time where info-beamer on the Pi didn’t even exist. When you ran info-beamer and gave the analogclock directory as argument, the top level node is named analogclock. Or more generalized: Starting info-beamer with info-beamer /path/to/some-directory will result in the top leven node being named some-directory.
The UDP addressing expects the full node path, including the top-level node. So the above call expects that node to be named analogclock.
Now on hosted, all the Lua top level code always ends up in /space/root, so the top-level node is always named root. If you change the value to root/clock/set:... it should work.
It seems that I can’t login using ssh.
Putty gives me a time-out and Linux: ssh: connect to host 172.16.1.150 port 22: Resource temporarily unavailable
Authorization file is added and is working on other systems
Just to be sure: This is the node.lua of the top-level directory, correct? So it’s not part of a package that is added as a child within a setup (similarly to how the power saver package is usually used).
You can also increase the log level by running pkill -usr2 info-beamer on the device once. This will increase the debug level from 3 to 4 and the log will be filled with a lot more information. The UDP message should be in there, but I can’t tell you what to grep for right now. I think using logread -f|grep -i udp should show something though.
Hm. I can take a look later to see what’s going on. The code looks correct, so it’s probably something minor. Which setup/device is that? Can you leave it running for a few hours?
Did the pkill command above yield any log lines? You should see something when you logread -f|grep state and trigger the state callback. A similar line will be generated when you send the clock/set message. Do they show up?
Are there maybe multiple util.data_wrapper “blocks” within your node.lua file? Do you have child nodes? How do you try to trigger this? Using Python? What exactly do you send there?
When using the terminal output you are using I just get a million lines:
May 1 08:27:09 Micro user.notice info-beamer: [main.c] frame time 0.0167
May 1 08:27:09 Micro user.notice info-beamer: [font.c] buffered rendering 72 vertices from 1
May 1 08:27:09 Micro user.notice info-beamer: [font.c] buffered rendering 108 vertices from 2
May 1 08:27:09 Micro user.notice info-beamer: [font.c] buffered rendering 54 vertices from 3
May 1 08:27:09 Micro user.notice info-beamer: [font.c] buffered rendering 168 vertices from 4
May 1 08:27:09 Micro user.notice info-beamer: [font.c] buffered rendering 138 vertices from 5
May 1 08:27:09 Micro user.notice info-beamer: [font.c] buffered rendering 90 vertices from 6
The util.data_mapper is executes when I press the button, but e.g. the [“device_info”] section is never called (I never get location and description filled) - and as far as I can see neigher is the [“clock/set”] section
I imported the package into my account, assigned it to a device, exposed info-beamer to the network (otherwise it’s completely unreachable from outside the device) and then sent the packet using:
That worked and resulted in the following log output on the device:
May 1 [..snip..] user.notice info-beamer: [root] DEBUG: Clock/set
So there must be some small difference in how you approach this somewhere. How and from where do you send the device_info packet for example? What’s the exact code for that? Is that from another machine in the network?