All good - much appreciated.

Sorry - my bad. Device that's working does not have a password. I'll have another go.

Boom - all working

Yes I have - on all of them. I seem to recall, when setting up the first one, that openLuup recognised a button press. Perhaps that's how it worked. These sensors wake up on an hourly basis, but when you wake them up manually they are awake for a minute or so (it seems).

Should have looked first ! Red highlights a win here; am seeing this ... (is there a proper way of copying and pasting?)

2021-06-12 11:10:01.904 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=492370363&Timeout=60&MinimumDelay=1500&_=1623492371898 HTTP/1.1 tcp{client}: 0x1e96db0
2021-06-12 11:10:19.108 openLuup.io.server:: MQTT:1883 connection from 192.168.1.156 tcp{client}: 0x1d97790
2021-06-12 11:10:19.152 openLuup.mqtt:: shellyht-E01A8B SUBSCRIBE to shellies/command tcp{client}: 0x1d97790
2021-06-12 11:10:19.153 openLuup.mqtt:: shellyht-E01A8B SUBSCRIBE to shellies/shellyht-E01A8B/command tcp{client}: 0x1d97790
2021-06-12 11:10:19.156 luup.shelly:83: New Shelly announced: shellyht-E01A8B
2021-06-12 11:10:19.279 openLuup.context_switch:: ERROR: [dev #83] ./openLuup/client.lua:96: missing realm or nonce in received WWW-Authenticate header
2021-06-12 11:10:19.280 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/announce : ./openLuup/client.lua:96: missing realm or nonce in received WWW-Authenticate header
2021-06-12 11:10:19.393 openLuup.server:: request completed (1891 bytes, 1 chunks, 17488 ms) tcp{client}: 0x1e96db0

Updated openLuup to v. 21.6.8 yesterday. I notice the z-way bridge has lost connection. and requires login. When I go to device/actions there is no way to enter credentials - only a login button.

The first Shelly I tried worked with the bridge created and device created in the Shellies room. The next ones also appear in openLuup/Servers/Received Connections list but don't appear as devices. Have I missed a step?

OMG. Genius. Many thanks indeed! Note to self - for Shelly .. Internet & Security/Advanced - Developer Settings/Enable MQTT

Will I need to set ports or do anything in Lua Startup still?

Hi guys - just received some Shelly H & Ts. Is there any documentation on how to connect these to mqtt (in novice speak )? Have read the thread but am getting slightly confused - do I need just the openluup mqtt server or another plugin also?

Did you ever get a certificate on to your controller? Would love to get Let's Encrypt on but I wonder if they are making it difficult so people go for their cloud solution.

Not using the button - don't really know what it does.

Thanks, only difference is Brand; I have Horstman (Secure), all versions and command classes are the same. I get the same error using openLuup interface too. Think this is the part where setpoint is accepted. Do you use the button for anything?

[2021-03-22 09:05:40.517] [D] [zway] SETDATA devices.42.data.lastReceived = 0 (0x00000000)
[2021-03-22 09:05:40.517] [I] [zway] Node 42:0 CC Wakeup: Wakeup notification
[2021-03-22 09:05:40.517] [D] [zway] SETDATA devices.42.instances.0.commandClasses.132.data.lastWakeup = 1616403940 (0x60585de4)
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.isAwake = True
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.lastSendInternal = **********
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.lastNonceGet = 47091702 (0x02ce8ff6)
[2021-03-22 09:05:40.518] [D] [zway] Running wakeup handler for node 42
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.instances.0.commandClasses.132.data.lastSleep = 1616403940 (0x60585de4)
[2021-03-22 09:05:40.518] [I] [zway] Node 42:0 CC Wakeup: Send node to sleep
[2021-03-22 09:05:40.518] [I] [zway] Adding job: Wakeup Sleep
[2021-03-22 09:05:40.518] [D] [zway] SENDING (cb 0xfc): ( 01 0D 00 13 2A 06 43 01 01 22 00 6E 05 FC 3B )
[2021-03-22 09:05:40.525] [D] [zway] RECEIVED ACK
[2021-03-22 09:05:40.527] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2021-03-22 09:05:40.528] [D] [zway] SENT ACK
[2021-03-22 09:05:40.528] [D] [zway] Delivered to Z-Wave stack
[2021-03-22 09:05:40.548] [D] [zway] RECEIVED: ( 01 18 00 13 FC 00 00 02 00 B0 7F 7F 7F 7F 01 01 03 00 00 00 00 02 01 00 00 BA )
[2021-03-22 09:05:40.548] [D] [zway] SENT ACK
[2021-03-22 09:05:40.548] [I] [zway] Job 0x13 (ThermostatSetPoint Set): Delivered
[2021-03-22 09:05:40.549] [D] [zway] SendData Response with callback 0xfc received: received by recipient
[2021-03-22 09:05:40.549] [D] [zway] SETDATA devices.42.data.lastSendInternal = **********
[2021-03-22 09:05:40.549] [D] [zway] SETDATA devices.42.data.lastSend = 47092706 (0x02ce93e2)
[2021-03-22 09:05:40.549] [D] [zway] Job 0x13 (ThermostatSetPoint Set): success
[2021-03-22 09:05:40.549] [I] [zway] Removing job: ThermostatSetPoint Set

Thanks - yes from zway basic interface.

Seems to be working fine except I get an error notification via email 'Error during perform command execution: Error: Invalid argument' every time setpoint is changed from controller. Also does anyone know if the 'Button' child is useful?

[2021-03-22 09:00:03.113] [I] [core] --- ZWayVDev_zway_42-0-67-1 performCommand processing: {"0":"exact","1":{"level":"11"}}
[2021-03-22 09:00:03.113] [D] [zway] SETDATA devices.42.instances.0.commandClasses.67.data.1.setVal = 11.000000
[2021-03-22 09:00:03.114] [I] [zway] Adding job: ThermostatSetPoint Set
[2021-03-22 09:00:03.114] [I] [zway] Adding job: ThermostatSetPoint Get
[2021-03-22 09:00:03.114] [I] [zway] Node 42:0 CC ThermostatMode: Thermostat Mode 1 is not supported by device (modemask 0x0)
[2021-03-22 09:00:03.117] [I] [core] Notification: error (module): Error during perform command execution: Error: Invalid argument
[2021-03-22 09:00:03.125] [I] [core] Error: Invalid argument
at Error (native)
at t_vDev.(anonymous function).self.controller.devices.create.handler (automation/modules/ZWave/index.js:5540:62)
at .extend.performCommand (automation/classes/VirtualDevice.js:365:25)
at ZAutomationAPIWebRequest..extend.performVDevCommandFunc (automation/ZAutomationAPIProvider.js:442:51)
at ZAutomationAPIWebRequest.handlerFunc (automation/ZAutomationAPIProvider.js:3976:30)
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:250:35)
at automation/WebserverRequestRouter.js:32:29
at WebServer.document_root (automation/Webserver.js:40:31)
[2021-03-22 09:00:03.130] [I] [core] HK: updated ZWayVDev_zway_42-0-67-1
[2021-03-22 09:00:03.137] [D] [zway] RECEIVED: ( 01 18 00 13 F0 00 00 05 01 C4 7F 7F 7F 7F 00 00 03 2E 00 00 00 03 01 00 00 EB )

+1 for zway

May well be different machines, differing firmwares. Frustrating nevertheless. Here's a stab at displaying variables.

Thanks - will have to try tomorrow - can't risk sending vera in to a tiz with guests staying.

Can i set them to (0,0) as the (5,1) misbehaves?

Sorry I was conflating issues. I have (a) two thermostats on separate veras that have different jsons and (b) one of those thermostats is shown above has the same json as another thermostat (on zway) but different functionality. Kinda got that muddled.

Seems odd that it's two different jsons for the same thermostat on separate veras. Perhaps the issue is inherently an altui one anyway. When I use the up down arrows for temp setpoint it starts from the cooling setting ie in this case 0 so its a lot of clicking to get to 20.

The same model thermostat paired to zway displays and behaves correctly with no cooling temps.

But they have the same json?