In the beta version, there is now an Ocotoprint hardware. I can see the Octoprint hardware made it into 2021.1 but I can't see any documentation about it, is anyone using it? It has options for settings in\out topics but that doesn't actually appear to flow to anything as I can see in the MQTT logs ...

Thanks for sharing, I also needed to install node-red-contrib-splitter. I have tested it yet, but I will have a play. I also might dust off my old solution, it was a variation of one in this thread (https://www.domoticz.com/forum/viewtopic.php?f=69&t=13607&start=20#p150149). The limitation I didn't ...

Confirming it is working as expected with 4.9758.

On the hardware what should the poll interval be? I had it as 0 before and all working, tried a value to see if it fixed (before update), back to 0 now. Just wondering what it does with this hardware?

Wob

Sent from my SM-G935F using Tapatalk

waaren wrote:This is solved in recent beta's

Thanks for the info, I was hoping to stick with stable, but I'll update today.

Sent from my SM-G935F using Tapatalk

Hi, Since the beta V3.9672 the status of the Hue bulbs (as a switch) isn't coming back in domoticz. I installed a new hue bridge on the hardware page and disabled the previous one. Scenes and groups are imported, also the motion sensor, but the bulbs are not imported. Who sees the same? And what to ...

@waaren A bit delayed, but I just wanted to say thanks, tweaked the formula and the timing to suit a couple of rooms and it has been working great.

theo69 wrote:Hi does anybody update to 1.4.1_155.0143, is it working with Domoticz?

Yes, a few weeks ago and so far no issues

Sent from my SM-G935F using Tapatalk

That looks seriously awesome, thanks so much for taking the time. I'm very interested to have a look at your test code.

Your stuff always look so neat and compact. I've not got around to learning all the shorthand.

Wob

Sent from my SM-G935F using Tapatalk

Hi, Not even sure where to start on this one, so hoping some better scripters can help. Have have a number of motion activated lights, and currently I just have to manually work out levels based on time periods, what I would like to do is have a formula work out the level based on how many minutes ...

Thanks. This fixed it. Btw. I don't have js/main.custom so I guess it isn't needed to change there. Now that I think about it I think those are my backup files when I made some changes to a couple of switches and removed the .0 from my thermostat :) what about the vendor folder, any idea on what ...

A fix for the above, The Levelnames are now being base64 encoded. I modified js/main.js and js/main.custom (I'm not sure if both are needed), I also noticed the same files under vendor/js/ can anyone comment on if these are used or not? Change var names = device['LevelNames'].split('|'); To var ...

EdwinK wrote: ↑Wednesday 23 May 2018 17:32 Not sure if this is Dashticz or Domoticz

I am seeing the same thing, looking at the json for the affected switches and Levelnames and Levelactions are all garbage, my guess is it is linked to this commit.

https://github.com/domoticz/domoticz/co ... 04db3d9dd0

waaren wrote: ↑Friday 18 May 2018 12:46 @Wob76,

thx for sharing!

No problem, happy to hear any suggestions on improvements etc

Still early days, but so far so good. Since this is a little off topic I started a new thread, my scripts are included.

viewtopic.php?f=59&t=23492

Should have noted.
Domoticz Version: 3.8932
dzVents Version: 2.4.1

My second script was a Door\Window monitor for when the house is empty, if something opens\closes when nobody is home it sends a notification. Again I have had this script running for some time, but quite often when I get home I have opened the back door before my phone has connected to the wifi (my ...

Since someone showed some interest in my solution to delaying notifications I thought I would post my scripts, or at least relevant snippets. I have only just implemented these, so I may yet find some bugs, but preliminary testing is positive. I wanted to delay messages, and have them not send if a ...

The advantage of the switch in this case is it I can create it to be momentary, with a configurable time, saves me using any dzVents queues. I had previously used variables for this kind of thing, but I use Dashitz and wanted to used the states of these variables to shade buttons depending on state ...

OK, so I have added a 'if (device.lastUpdate.minutesAgo >= 5) then" (device being my door\windows) check around my notification send, just before that I am switching on a dummy delay switch, this switch is set to turn off after a 300 second delay (5 min) and that device is included in my trigger ...

Or use a timer in where you check if the lastUpdate of the switch is older than 5 minutes and then send the notification. The issue with that approach is I need the script to run at time intervals, at the moment it is called by changes in the door/window contacts, and AC switches. So called much ...