I'm using Domoticz on a Raspberry Pi to read the status of GPIO-ports that are connected to my alarm system and be able to switch it on/of.

Domoticz acts as a hub to forward this information to HomeAssistant that does logic with it (to which I am migrating to)

Yes, this is exactly what the use is for retained messages.

From the link I have referred to:
Retained messages help newly-subscribed clients get a status update immediately after they subscribe to a topic. The retained message eliminates the wait for the publishing clients to send the next update ...

Hi,

I'm using the MQTT Client gateway to have Domoticz publish the status of sensors and switches on MQTT so that other software can use this.

This works fine, except that if the other tool restarts, it is not until and update is send from Domoticz about a sensor before it is informed of the last ...

Sure, just read the information with the MQTT Client Gateway at the "Publish Topic" setting.

If you set this at "Index" it will publish on Domotiz/out/idx

Can you see the device as /dev/ttyUSB0 or /dev/ttyACM0?

I'm definitely no Unix expert, but I think that most of these devices are placeholders.
In my case the "real" devices are different from the other devices because all devices are belonging tot the "tty" group, but the actual devices are ...

My point was that there shouldn’t be a need to use mknod. If you plug in a USB stick a device is created, there is noneed to do that manually. If you can’t list the device, not even by it’s /dev/tty* then something else is wrong.

Doing the ls -lh /dev/ttyUSB-ZStick-5G
ls: cannot access '/dev/ttyUSB-ZStick-5G': No such file or directory
SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SYMLINK+="ttyUSB-ZStick-5G"


Hi, you should not have to use mknod: if the device is recognised its there if not it ...

Hi,

I can't see anything strange, look Ok from here.

You can check why you can't see a running Domoticz, by checking the Domoticz-log.

You can check the log by going into the Portainer web interface (default at http://docker-host:9000/#/containers) and then in the "Containers" menu, select the ...

hi, i recognise your struggling, so here is a small guide:

On the ProxMox host:

I first used the Domoticz guide create " Persistent USB Devices" . It is optional, but it makes sure that the ID of your USB does not change after a restart or when plugging in other USB-devices as well.

After that ...

Hi,

In order not to have all this installation hustle, I would advice you to look at using Docker.

You can install Docker inside a LXC and get all the benefits of managing the machine with ProxMox, but without having to actually install Domoticz or other "Docker-ised" apps. So the only thing you ...

Thanks,

So if I can get the one above for 95€ or this one for 115€ Intel NUC Kit D34010WYK
Intel Core i3 4010U 1.7GHz, 4GB Ram, 120GB M.2 SSD

Which would be the best option? Old processors made some sense to me, now days it doesn't.

As said, both will have plenty CPU-power for Domoticz only ...

It is better to actually partition/format and use the whole SSD, because now you are continuously using the 8 Gb for all writes, while it would be better to spread this over the whole disks. This would decrease the amount of writes per surface 30 times!

Found a small bug, the notification returned an empty message today.

So line 194:
dz.notify(longGarbageName(overallEarliestType) .. ' will be collected today')

needs to be changed to:
dz.notify(longGarbageName(garbage[sortedKeys[1]][2]) .. ' will be collected today')

Or this, if you would ...

I will already change the regex to include ophaaldagenNext as well, like this:
json = "{"..triggerObject.data:match('(\"ophaaldagen\":{.*),\"mededelingen\":').."}"


This will probably work for you but is not needed for addresses where the initial conversion already worked. There is also a ...

I don't think that this line will work at the end of the year:
json = "{"..triggerObject.data:match('(\"ophaaldagen\":{.*),\"ophaaldagenNext\":').."}"

.. because towards the end of December the "ophaaldagenNext" table will be filled with the collection dates for January and the "ophaaldagen ...

Thanks waaren!

I couldn't stand that I was not able to get this working nicely so did some more testing and found that the crippled Json is in a part of the result that is not relevant. So I used the regex as posted earlier to only select the proper "ophaaldagen" Json object from the result.

Now ...

Hi Jos,
Thanks for the tip, I actually got the idea from your script ;-)

My version is a try to improve that even a bit further by not only filtering everything out of the reply after the "ophaaldagen" object, but also everything before. If I test this regex in an online regex editor with the ...

I tried to reduce the result set by adding these lines which should reduce the result to only the "ophaaldagen" object, but that seem not to do anything, still getting the error that there are too many lines.

triggerObject.data = triggerObject.data:match('.*(\"ophaaldagen\".*),.*\"ophaaldagenNext ...

Don’t you get this error?

That script actually works! Well sort off, it complains with this error, although the devices are updated:

Error: dzVents: Error: (3.0.9) collectGarbage: Error parsing json to LUA table: /opt/domoticz/scripts/dzVents/../lua/JSON.lua:1234: /opt/domoticz/scripts/dzVents/../lua/JSON.lua:1016: Lua ...