Hey,

As far as I can see there's currently no support for Thermostat on MQTT. Would be cool to implement this hopefully in such way that it supposerts Evohome - https://www.domoticz.com/wiki/Evohome#T ... d_HGI80.29

you sir saved my day, thanks

just create a custom.js file on /domoticz/www/styles/your_theme and paste jQuery(window).load(function() { setTimeout(function () { $("#devices tbody tr").each(function() { var html = $(this).children()[2].innerHTML; var className = $(this)[0].className; var res = html.match(/(\s[0-9]{3}\s[\(][0-9]x ...

thank you @jvdz - this is the single best add to Domoticz since I can remember :D As a suggestion, add a "link" on the device ID to filter the devices' table. This is how I'm doing it now (added to my themes custom.js) $("#devices tbody tr").each(function() { var html = $(this).children()[2 ...

Cool.

That's actually another question I have, not sure why the "replacement" option isn't available for Z-Wave devices...

apparently it's not...or it's not a priority

+1 for this

it's the *one* thing that pisses me off with Domoticz...it's OK if you have half a dozen devices, a mess when you have 50!

I'm wondering if theres something preventing this from being implemented of if I can help in any way...

Are there any plans to continue improving MQTT supported commands such as setcolbrightnessvalue?

I'm either missing the point or have explained myself incorrect. the HArdwareID you mention is not a device node ID. So say you can have an Aeon Z-Stick (HardwareID 2) and multiple a Fibaro Dimmer (nodeID 10). There's no way on the UI or the database to know what devices (DevicesStatus) have been ...

I've scavenged the DB and couldn't find anything relevant

that's interesting, so it sounds like there's a way to "link" Hardware (as in Z-Wave device) with a Domo device somehow..
I can't understand why we can't see this in the device list so that we can easily see which devices have been created by a "Z-Wave device"

don't think you can, you'll need to use http instead

can't see how that's a problem, just replace 192.168.1.2 with your Domoticz IP

nvm, I've figured it out - guess Wiki needs updating!

The JSON API seems a bit incomplete when it comes to Room and Floor Plans Unable to list *all* (including hidden) rooms Would have expected /json.htm?type=plans&order=name or /json.htm?type=plans&order=name&used=false to retrieve them but it doesn’t Unable to list Floor Plans (Plans -> Floorplan) I n ...

@SchattenMann There is one reason I can think of why the devices are not deleted when a node is excluded; if you delete a sensor your saved data will be lost. Would be better to ask when you delete a node if you want to delete the associated devices and a option to backup your sensor data say for ...

yeah I have the same problem, after a few Excluded Z-Wave devices I end up with dozens of "orphan" devices to be removed but not idea how to identify them all

This method gizmocuz describes is not full proof. If I filter "Razz 13" (my zwave hardware is called: Razzbery 2.0 and the node 0x13) than it returns 25 devices. I second that. I'm surprised there wasn't any foreign key between the two tables, I would expect when a device (DeviceStatus) is created ...

I'm looking at the DB and it seems there's no relation between DeviceStatus and ZWaveNodes table...I would have expected a relational table or a NodeID field on DeviceStatus but guess I was wrong...

How does domo know that device X belongs to Z-Wave Node Y then? Clearly I'm missing the point here...

Thanks gizmocuz, That does kinda help :-) I would say it's worth adding "Node ID" and "Hardware (device) Name" column on the device list table. Sure not all devices will have it filled in but the same thing happens with Battery and Range columns if that makes sense. With these columns device ...