N
The right sidebar has a few pixels above, below and to it's right which "belong to" the editor background. I understand that it was a conscious decision to have this sidebar floating - I think the reason was "to maximise the editor screen space"? However it is infuriating when switching back and forth between the Monaco editor and debug panel to accidentally click just to the right of the debug scrollbar and the editor closes. Whatever the value of the gap above and below the sidebar, surely…
N
Thank you it's been solved, package published again. Sorry of the frustration.
N
These heaters are already sold to private and businesses alike, they are app controlled. A lot of home electronics are cloud controlled, from lights, heaters, heatpumps ++. We control electric panel heater / wall heater / convector heater. If it breaks, thousands will break, not just the 100 we got. They don't got our name on it, while we provide them and add functionality on top, I'm sure it can be communicated to our customer that the problem is with the manufacturer. If needed, we'd have to…
N
Thank you! I'm shocked and pleased that for once the error wasn't my own stupidity!
N
This guy is fully invested ... https://www.youtube.com/watch?v=WYsRZXlSmLA - I must admit I found the channel quite entertaining - but no way would I let ChapGPT (or other AI) knowingly have full control in my laptop or house server. And then it just gets weird.... A Man and His Muse AI Agent Sue Meta
N
Hi There, Why? No error explanation, no memo, no info - just a erroneous error message. Sorry for being frustrated but it's just something that is continually happening with many folks believing that others have ESP or some other mind-reading powers: I don't know why my tar format is suddenly being rejected. This error message from a package I've had published and now wanting to do a upgrade, I get this random error. --> https://www.npmjs.com/package/@gregoriusrippenstein/node-red-scratchpad…
N
I found the problem with discovering writable attributes there was a change in matter.js as to this path, Fixed in 0.2.2 of the controller
N
And one more I just forgot, where are we heading? Have you heard about this, I guess you have, no coding no more.... Lovable App & Website Builder | Build Software in Minutes | Lovable Describe what you want in plain language and Lovable builds it: full-stack apps, websites and internal tools. Start free.
N
mudwalker: At the end of the day, Knowledgeable Forums are very valuable I can only agree fully to that! How boring will forums become if everybody is just starting to share results given to them by AI? I hope we will not see this happen here Sometimes AI can be useful. I'm not very skilled in coding & have no patience sitting in front of the computer day long, so I have made some quick experiments where AI (Google AI) helped accurately and spot on, really impressive I think in those cases; I…
N
Build complete latest-debian should point to 5.0.10 agian
N
Fix: Pull request node-red/node-red-docker Remove `latest-debian` from 4.1.x build tags (#556) v4.1.x ← hardillb-patch-9 hardillb opened 09:25PM - 17 Nov 26 UTC +1 -1 - [x] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-b…reaking change which adds functionality) ## Proposed changes The `latest-debain` tag got overwritten by the 4.1.x build, this totally removes that tag from the 4.1.x build ## Checklist - [ ] I have read the [contribution…
N
I know what the problem is, the 4.1.18 containers were built after the 5.0.10 ones and it looks like there is a bug in the tagging that is still adding the latest-debian tag to the 4.1.x builds. You must have updated the first 2 machines inbetween the two builds I will respin the 5.0.10 build which will fix this and then look for the bit to delete from the 4.1.x container build script. Give it an hour and do the pull again
N
ThingsTinkerer: If the ovens are hacked, that would be a problem for the oven company who maintains their cloud service. I think that your customers, landlords, insurers and more might just disagree. Depending on where the ovens are situated, there could be risk to life, surrounding buildings and more. ThingsTinkerer: The damage is limited, by turning it down, people would come to work to a cold office (ovens are secondary heating for the building). Ah, I was thinking a bakery. The worse case…
N
If the ovens are hacked, that would be a problem for the oven company who maintains their cloud service. For us, best we could do is shut it down by removing or replacing the access token. The damage is limited, by turning it down, people would come to work to a cold office (ovens are secondary heating for the building). If heated up, I don't know all ovens are a potential fire hazard regardless, but I think they're capped at max 30 Celsius.
N
No, that was not it, unfortunately. I hoped it whas that easy.
N
Thanks for answering, Colin! I really didn't think about that, since they are all Trixie, from the same basic image (I install and update and add the Docker stuff before branching them out for the different uses, one in my house, one in my cabin and one in my boat). But I see that the other two are updated in the beginning of november, while the problematic one was updated in mid september. The versions are a bit different from uname -a, first the problematic one: 6.18.50+rpt-rpi-2712 #1 SMP…
N
I don't know whether it might be a factor, but are they all running the same os version? cat /etc/os-release [Edit] Also are they all up to date? sudo apt update && sudo apt full-upgrade
N
This is weird. I have three Pi 5 running Node-RED in Docker, identical setups with the Docker files moved from the SD card to an SSD. Two of them has identical hardware connected to Node-RED as well (RFXtrx). And identical Docker Compose files, here's the relevant parts of the Docker file (the build stuff is running perfectly, building with version 5 on two of the Pi's and has been working for a few years). node-red: build: dockerfile_inline: | FROM nodered/node-red:latest-debian USER root RUN…
N
ThingsTinkerer: the ovens are controlled via a cloud service I do hope you have taken note of the recent Europe-wide fridge hacks? Many vendors who squeezed either cloud or local network controls into things have still not properly dealt with security. ThingsTinkerer: The main hassle with it is the oven producer doesn't set a flag for the source of the temperature change, so it got a bit complicated by storing latest automated commands in context and only changing temp immediately after reading…
N
Node-RED 5.0.10 and 4.1.18 released News Node-RED 5.0.1 and 4.1.18 are now available. Most notably, these releases include fixes for the latest Safari browser and a number of security-related updates.
N
I generally set the trigger period to about 1% of the cycle time so you get a 1% accuracy in the times.
N
It is now working - outputing a 0, 9 times in a row and then a 1, 3 times in row.
N
This is ridiculous. What version of node-red and nodejs are you using? What is node-red running on. What version of the timeprop node is it?
N
It is on the radar (and in progress) & will land in the coming days.
N
I think we need someone else to install it and see what happens with them
N
Just outputs a 0 every 5 secs - I always press the inject
N
Try with 0.25 again, did you click the inject node again after deploying the timeprop node?
N
If i send in a 1 - it outs a 1 every 5 secs [edit] sending in 0.5 - just goes back to outputting a zero every 5 secs
N
cymplecy: it just starts running even if I don't - very strange It starts running immediately, assuming an initial input of zero. When you send in a message it should change to the required duty cycle. Is it now working? If not, what happens if you feed in 1? I am sure there is nothing wrong with the node, I see I first released it 10 years ago tomorrow.
N
Yes but interestingly - it just starts running even if I don't - very strange